Implementation Approaches

​

Quick Comparison

​

One-Shot Implementation

​

How It Works

1. Open product-plan/prompts/one-shot-prompt.md
2. Add any additional notes (tech stack preferences, constraints)
3. Copy/paste the prompt into your coding agent
4. Answer the agent’s clarifying questions about:
   • Tech stack and existing codebase conventions
   • Authentication and user management
   • Product requirements
   • Anything else needed before implementing
5. Agent creates a comprehensive implementation plan
6. Agent implements all milestones (shell + all sections)
7. Review and test the complete product

​

What the Prompt Does

• References product-overview.md for full context
• References instructions/one-shot-instructions.md (all milestones combined)
• Guides agent to review all design files before starting
• Prompts for clarifying questions about tech stack and requirements
• Asks if you have any additional notes
• Encourages the agent to create a plan before implementing

# One-Shot Implementation Prompt

I need you to implement a complete web application based on 
detailed UI designs and product specifications I'm providing.

## Instructions

Please carefully read and analyze the following files:

1. **@product-plan/product-overview.md** — Product summary
2. **@product-plan/instructions/one-shot-instructions.md** — 
   Complete implementation instructions for all milestones

After reading these, also review:
- **@product-plan/design-system/** — Tokens
- **@product-plan/data-shapes/** — UI data contracts
- **@product-plan/shell/** — Application shell components
- **@product-plan/sections/** — All section components and test specs

## Before You Begin

Review all the provided files, then ask me clarifying questions about:

1. **My tech stack** — Framework, language, tools, conventions
2. **Authentication & users** — Sign up, log in, permissions
3. **Product requirements** — Anything that needs clarification
4. **Anything else** — Whatever you need to know

Lastly, ask me if I have any additional notes.

Once I answer, create a comprehensive implementation plan before coding.

​

When to Use One-Shot

​

Advantages

• Fast — See the full product in one session
• Cohesive — Agent has full context and can optimize across sections
• Less overhead — No need to manage multiple sessions

​

Challenges

• Large context — Requires agent to handle all instructions at once
• Higher risk — If something goes wrong, more work to redo
• Less control — Harder to course-correct mid-implementation

​

Incremental Implementation

​

How It Works

1. Shell (instructions/incremental/01-shell.md)
   • Design tokens and application shell
   • Foundation for all sections
2. Section 1 (instructions/incremental/02-[section-id].md)
   • First feature section
   • Uses the shell and tokens
3. Section 2 (instructions/incremental/03-[section-id].md)
   • Second feature section
   • Builds on existing work
4. Continue for all remaining sections

​

For Each Milestone

1. Open product-plan/prompts/section-prompt.md
2. Fill in the section variables at the top:
   SECTION_NAME = [Human-readable name]
   SECTION_ID = [Folder name in sections/]
   NN = [Milestone number: 01 for shell, 02+ for sections]
   
3. Add any section-specific notes
4. Copy/paste the prompt into your coding agent
5. Answer clarifying questions
6. Agent implements the milestone
7. Review and test before moving to the next milestone

# Section Implementation Prompt

## Define Section Variables

- **SECTION_NAME** = [e.g., "Invoices" or "Project Dashboard"]
- **SECTION_ID** = [e.g., "invoices" or "project-dashboard"]
- **NN** = [e.g., "02" or "03" — sections start at 02]

---

I need you to implement the **SECTION_NAME** section of my application.

## Instructions

Please carefully read and analyze the following files:

1. **@product-plan/product-overview.md** — Product context
2. **@product-plan/instructions/incremental/NN-SECTION_ID.md** — 
   Specific instructions for this section

Also review the section assets:
- **@product-plan/sections/SECTION_ID/README.md** — Feature overview
- **@product-plan/sections/SECTION_ID/tests.md** — Test specs
- **@product-plan/sections/SECTION_ID/components/** — React components
- **@product-plan/sections/SECTION_ID/types.ts** — TypeScript interfaces
- **@product-plan/sections/SECTION_ID/sample-data.json** — Test data

## Before You Begin

Review all files, then ask me clarifying questions about:

1. **Integration** — How this connects to existing features
2. **Product requirements** — Anything that needs clarification
3. **Anything else** — Whatever you need to know

Lastly, ask me if I have any additional notes.

Once I answer, proceed with implementation.

​

When to Use Incremental

​

Advantages

• Controlled — Review and test after each milestone
• Lower risk — Easier to catch and fix issues early
• Flexible — Can adjust approach based on learnings
• Better for learning — Understand each piece before moving on

​

Challenges

• More sessions — Requires multiple implementation sessions
• Session management — Need to track progress across milestones
• Context switching — Agent doesn’t see full picture until later

​

Choosing Your Approach

​

Project Complexity

• 2-3 sections: Either approach works
• 4-6 sections: Incremental recommended
• 7+ sections: Incremental strongly recommended

​

Team Size

• Solo developer: Either approach works
• Small team (2-3): Incremental for better coordination
• Larger team: Incremental with milestone assignments

​

Requirements Clarity

• Very clear requirements: One-shot can work
• Some ambiguity: Incremental lets you clarify as you go
• Exploratory: Incremental to learn and adjust

​

Time Constraints

• Need full product fast: One-shot
• Prefer steady progress: Incremental
• Long-term project: Incremental

​

Agent Experience

• Experienced with AI agents: One-shot feasible
• Learning AI-assisted development: Incremental safer
• First time with this agent: Incremental to calibrate

​

Hybrid Approach

1. Start with incremental — Build shell + first section to validate
2. Switch to one-shot — Complete remaining sections in one session

1. Group related sections — Implement 2-3 sections per session
2. Review between groups — Test and adjust before next group

​

Example: Incremental Workflow

​

Tips for Success

​

Next Steps