Let's set up your new project. Tell me about what you're building.

I'm looking for:
- **The core idea** — What problem does this solve?
- **Target users** — Who is this for?
- **Scope** — MVP, production-ready, or quick prototype?

Don't worry about technical details yet — just tell me about the product.

Based on what you've described, this sounds like a [scope_type] project.

**[If MVP]:**
I'll optimise for getting to a working product quickly:
- Lite design documentation
- Pragmatic architecture choices
- Essential features only

**[If Production]:**
I'll set up for long-term maintainability:
- Comprehensive documentation
- Scalable architecture patterns
- Full security considerations

**[If Prototype]:**
I'll focus on speed above all:
- Minimal documentation
- Fastest path to demo
- Technical debt accepted

Does this match your expectations, or should we adjust?

Now let's choose your technology stack. I'll suggest defaults based on 
your preferences, but you can override any choice.

**Frontend:**
→ Recommended: Next.js 14 with App Router
  - Great for SEO, fast initial loads, React ecosystem
  - Alternative: Plain React (simpler, if you don't need SSR)
  - Alternative: Vue/Nuxt (if you prefer Vue syntax)

**Backend:**
→ Recommended: Python with FastAPI
  - Excellent for rapid development, great typing support
  - Alternative: Node.js/Express (if JS everywhere matters)
  - Alternative: Python/Django (if you need batteries-included)

**Database:**
→ Recommended: PostgreSQL
  - Rock solid, great tooling, handles most use cases
  - Alternative: MongoDB (if truly document-oriented data)
  - Alternative: SQLite (for simpler projects, no server needed)

**Deployment:**
→ Recommended: Vercel (frontend) + Railway (backend)
  - Easy setup, good free tiers, scales well
  - Alternative: AWS (more control, more complexity)
  - Alternative: Fly.io (good for global distribution)

What would you like to use? You can say:
- "Use defaults" — I'll proceed with recommendations
- "Change [X] to [Y]" — I'll adjust specific choices
- "Tell me more about [X]" — I'll explain trade-offs

A few security questions to set the baseline:

1. **User data**: Will you store personal information (names, emails, etc.)?
   → Affects: Data protection requirements, encryption needs

2. **Authentication**: Do users need to log in?
   → Affects: Auth system complexity, session management

3. **Payments**: Will you handle money or financial data?
   → Affects: PCI compliance, security scrutiny level

4. **Compliance**: Any specific requirements (GDPR, HIPAA, SOC2)?
   → Affects: Documentation depth, audit trails

Here's what I'm going to set up:

╔══════════════════════════════════════════════════════════════╗
║  PROJECT: [project-name]                                     ║
╠══════════════════════════════════════════════════════════════╣
║                                                              ║
║  Scope: [MVP/Production/Prototype]                           ║
║  Design System: [Lite/Full]                                  ║
║                                                              ║
║  Stack:                                                      ║
║  ├─ Frontend:   [choice] + [styling] + [state]              ║
║  ├─ Backend:    [language] + [framework]                    ║
║  ├─ Database:   [db] + [orm]                                ║
║  └─ Deployment: [platform]                                  ║
║                                                              ║
║  Security Baseline:                                          ║
║  ├─ Auth: [method]                                          ║
║  ├─ PII: [yes/no]                                           ║
║  └─ Compliance: [requirements]                              ║
║                                                              ║
╚══════════════════════════════════════════════════════════════╝

I'll create:
- Project configuration file
- Documentation folder structure  
- Pipeline status tracking
- Decision log

Ready to proceed? (yes / make changes)

./project-documentation/
├── _meta/
│   ├── project-config.yaml      # Generated from selections
│   ├── pipeline-status.md       # Initialised with Phase 0 complete
│   └── decision-log.md          # Initial decisions recorded
│
├── 00-bootstrap/
│   └── project-bootstrap.md     # This phase's output
│
├── 01-requirements/
│   └── .gitkeep
│
├── 02-design/
│   └── .gitkeep
│
├── 03-architecture/
│   ├── api-contracts/
│   │   └── .gitkeep
│   └── data-models/
│       └── .gitkeep
│
├── 04-implementation/
│   ├── backend/
│   │   └── .gitkeep
│   ├── frontend/
│   │   └── .gitkeep
│   └── shared/
│       └── .gitkeep
│
├── 05-testing/
│   ├── test-specs/
│   │   └── .gitkeep
│   └── test-results/
│       └── .gitkeep
│
├── 06-deployment/
│   └── runbooks/
│       └── .gitkeep
│
└── 07-security/
    └── audit-reports/
        └── .gitkeep

---
project: [project-slug]
last_updated: "[timestamp]"
---

# Pipeline Status

## Current Phase
- **Active**: Phase 1 — Product Manager
- **Started**: [timestamp]
- **Blockers**: None

## Phase Completion Status

| Phase | Status | Version | Approved | Notes |
|-------|--------|---------|----------|-------|
| 0 - Bootstrap | ✅ Complete | 1.0.0 | — | |
| 1 - Product Manager | 🔄 Ready | — | — | |
| 2a - UX/UI | ⏳ Waiting | — | — | |
| 2b - Architect | ⏳ Waiting | — | — | |
| Gate #1 | ⏳ Waiting | — | — | |
| 3a - Backend | ⏳ Waiting | — | — | |
| 3b - Frontend | ⏳ Waiting | — | — | |
| 3c - QA Specs | ⏳ Waiting | — | — | |
| 4 - QA | ⏳ Waiting | — | — | |
| 5 - DevOps | ⏳ Waiting | — | — | |
| 6 - Security | ⏳ Waiting | — | — | |
| Gate #2 | ⏳ Waiting | — | — | |

## Recent Activity

- **[timestamp]** — Project bootstrapped

## Next Actions

1. Run Product Manager agent to define requirements

---
project: [project-slug]
---

# Decision Log

This document records key decisions made during development with rationale.

## DEC-001: Technology Stack Selection

**Date**: [timestamp]  
**Phase**: 0 - Bootstrap  
**Decision**: Use [stack summary]  

**Context**: 
[Brief project context]

**Options Considered**:
1. [Option A] — [Pros/cons]
2. [Option B] — [Pros/cons]

**Decision**: 
Chose [selected option] because [rationale].

**Consequences**:
- [Expected outcomes]
- [Trade-offs accepted]

---

## DEC-002: Project Scope

**Date**: [timestamp]  
**Phase**: 0 - Bootstrap  
**Decision**: [MVP/Production/Prototype] scope with [Lite/Full] design system

**Rationale**:
[Why this scope was chosen]

**Implications**:
- Documentation depth: [level]
- Quality bar: [expectations]
- Speed vs. thoroughness: [balance]

---
document_type: bootstrap
version: "1.0.0"
status: approved
created_by: bootstrap
created_at: "[timestamp]"
last_updated: "[timestamp]"
project: "[project-slug]"

phase: 0
depends_on: []
blocks:
  - "01-requirements/product-requirements.md"

requires_human_approval: false
approval_status: not_required

stack:
  frontend: [selection]
  backend: [selection]
  database: [selection]
  deployment: [selection]

security_considerations:
  - id: "SEC-001"
    category: infrastructure
    consideration: "Development environment security"
    status: identified
    mitigation: "Use environment variables for secrets, never commit .env files"
    owner: devops_engineer
  - id: "SEC-002"
    category: dependencies
    consideration: "Dependency vulnerability management"
    status: identified
    mitigation: "Enable Dependabot/Snyk, review before merging updates"
    owner: devops_engineer
---

# Project Bootstrap: [Project Name]

## Project Overview

**Name**: [Project Name]  
**Slug**: [project-slug]  
**Description**: [One-line description]  
**Created**: [timestamp]

## Scope Definition

**Type**: [MVP | Production | Prototype]  
**Design System**: [Lite | Full]  
**Estimated Features**: [count]

### Scope Implications

| Aspect | Approach |
|--------|----------|
| Documentation depth | [Minimal | Moderate | Comprehensive] |
| Code quality bar | [Functional | Solid | Production-grade] |
| Testing coverage | [Critical paths | Good coverage | Comprehensive] |
| Security scrutiny | [Basic | Standard | Rigorous] |

## Technology Stack

### Frontend
- **Framework**: [e.g., Next.js 14]
- **Styling**: [e.g., Tailwind CSS]
- **State Management**: [e.g., Zustand]
- **Rationale**: [Why this choice]

### Backend
- **Language**: [e.g., Python 3.11]
- **Framework**: [e.g., FastAPI]
- **Rationale**: [Why this choice]

### Database
- **Primary**: [e.g., PostgreSQL]
- **ORM**: [e.g., Prisma]
- **Cache**: [e.g., Redis]
- **Rationale**: [Why this choice]

### Deployment
- **Platform**: [e.g., Vercel + Railway]
- **CI/CD**: [e.g., GitHub Actions]
- **Containerised**: [Yes | No]
- **Rationale**: [Why this choice]

## Security Baseline

### Data Classification
- **Contains PII**: [Yes | No]
- **Contains Financial Data**: [Yes | No]
- **Contains Health Data**: [Yes | No]

### Authentication
- **Method**: [JWT | Session | OAuth | None]
- **MFA Required**: [Yes | No]

### Compliance Requirements
- **GDPR**: [Yes | No]
- **CCPA**: [Yes | No]
- **SOC2**: [Yes | No]
- **Other**: [List]

## Project Conventions

### Naming
- Files: [kebab-case]
- Components: [PascalCase]
- Functions: [camelCase]
- Variables: [camelCase]

### Code Style
- Max line length: [100]
- Indentation: [2 spaces]
- Quotes: [double]

## Directory Structure

## Next Steps

The project is now bootstrapped. Proceed to **Phase 1: Product Manager** to define:
- Detailed requirements
- User personas
- Feature prioritisation
- Success metrics

---

*Generated by Bootstrap Agent v1.0.0*

✅ Project "[project-name]" bootstrapped successfully!

Created:
- Project configuration in ./project-documentation/_meta/
- Folder structure for all pipeline phases
- Initial decision log with stack rationale

**Next Step**: Product Manager (Phase 1)

The Product Manager agent will:
- Define detailed requirements from your project idea
- Create user personas
- Write user stories with acceptance criteria
- Prioritise features for your [scope] approach

Ready to continue with requirements? Say "next" or "phase 1" to proceed.