project-bootstrap-full

Files (1)

• SKILL.md

SKILL.md (first lines)

# Project Bootstrap Full

A comprehensive project bootstrapping skill that creates a complete engineering foundation with SOLID architecture, TDD protocols, comprehensive documentation suite, data logic wireframes, and project scaffold. Works for both **greenfield** (new) and **brownfield** (existing) projects. Based on the proven patterns from `amph-v2` and `amph-v2-greenfield`.

## Core Philosophy

This skill follows a strict **Question-First** approach:

1. **Understand completely** before creating anything
2. **Ask intelligent questions** to uncover hidden requirements  
3. **Create proportional documentation** based on project risk
4. **Build one vertical slice** before expanding horizontally
5. **Maintain source-of-truth** files that evolve with the project
6. **Enforce SOLID principles** through architecture, not just code review

## Workflow

### Phase 0: Project Type Detection

**Critical First Step:** Determine if this is a **greenfield** (new) or **brownfield** (existing) project.

#### Greenfield Detection
- New repository or empty directory
- No existing codebase
- Starting from scratch
- **Action:** Proceed to Phase 1 with full greenfield workflow

#### Brownfield Detection
- Existing codebase with history
- Established patterns and conventions
- Multiple contributors or long development history
- **Action:** Proceed to Phase 1 with brownfield assessment first

---

### Phase 1: Intelligent Discovery

Before creating any files, ask questions to understand:

#### Project Identity & Purpose
- **Project name**: What should the project be called?
- **One-sentence summary**: What outcome does this project create?
- **Primary users**: Who will use this system?
- **Problem statement**: What specific problem does this solve?
- **Success criteria**: How will you measure if this project succeeded?
- **Non-goals**: What is explicitly NOT in scope?

#### Technical Foundation
- **Tech stack**: What languages, frameworks, databases, and tools?
- **Deployment target**: Where will this run? (cloud, on-premise, mobile, desktop)
- **Data sensitivity**: What kind of data will it handle?
- **Scalability needs**: Expected user/load growth?
- **Budget/hosting**: Cost constraints or preferred providers?

#### Architecture & Design
- **System boundaries**: What are the main components/modules?
- **Integration points**: What external systems will it connect to?
- **UI requirements**: Web, mobile, CLI, or API-only?
- **Real-time needs**: Does it need live updates, notifications, or streaming?
- **Architecture preference**: Monolith, microservices, or modular monolith?

#### Development & Operations
- **Team size**: Solo developer or team?
- **Development timeline**: Urgent prototype or long-term production system?
- **Testing strategy**: Unit, integration, E2E, or all?
- **CI/CD pipeline**: What build/test/deploy tools?
- **Monitoring needs**: Logging, metrics, alerting requirements?
- **Existing systems**: Legacy code or greenfield project?

#### Business & Domain
- **Business rules**: What are the core business rules?
- **Pricing model**: If applicable, what's the pricing structure?
- **Payment processing**: What payment gateways are needed?
- **Email/notification requirements**: Transactional, marketing, etc.?
- **Compliance/regulatory**: GDPR, HIPAA, SOC2, PCI?

#### Brownfield-Specific Questions (If Existing Project)
- **Project history**: How old is the codebase? Major milestones?
- **Code quality**: Current test coverage? Technical debt level?
- **Architecture patterns**: Existing patterns to preserve?
- **Team knowledge**: Who knows what parts of the system?
- **Business criticality**: What's the cost of downtime?
- **User base**: How many active users? Impact of changes?
- **Integration dependencies**: External systems that can't be changed?
- **Compliance constraints**: Regulatory requirements that must be maintained?

### Phase 2: Profile & Layout Selection

Based on answers, recommend:

- **Profile**: `prototype`, `standard`, or `production`
- **Layout**: `generic`, `web-app`, `api-service`, `library`, or `monorepo`
- **Architecture**: Traditional, SOLID-layered, or microservices
- **Testing strategy**: Proportional to risk and team capability
- **Mode**: `greenfield` or `brownfield` (determined in Phase 0)

### Phase 2.5: Brownfield Assessment (If Existing Project)

Before scaffolding, perform a comprehensive codebase assessment:

#### Codebase Analysis
- **Directory structure**: Map existing folder layout
- **Package.json / requirements.txt**: Catalog all dependencies
- **Configuration files**: Identify existing configs (.eslintrc, tsconfig, etc.)
- **Test setup**: What testing framework exists? Coverage baseline?
- **CI/CD pipeline**: Existing automation and deployment
- **Documentation**: What docs already exist?

#### Code Quality Audit
- **Test coverage**: Run coverage, document baseline
- **Linting**: Run linter, count warnings/errors
- **Type safety**: TypeScript strictness level
- **Dependencies**: Outdated packages, security vulnerabilities
- **Technical debt**: Known pain points from team

#### Architecture Mapping
- **Entry points**: Where does the app start?
- **Data flow**: How does data move through the system?
- **Integration points**: External APIs, databases, services

From projectamazonph/agent-skill-framework, MIT.

More from projectamazonph/agent-skill-framework