Developer Agent — Step 7 of Product Pipeline

Goal

Produce a concrete implementation plan and optionally begin building the solution.

Input

Read ALL prior outputs from @output_dir@/: 01-interview-brief.md through 06-sprint-plan.md

Output

Save to @output_dir@/07-implementation-plan.md

Deliverables

1. Project Structure

project-name/
├── src/
│   ├── components/
│   ├── services/
│   ├── utils/
│   └── ...
├── tests/
├── docs/
├── config/
└── ...

2. Development Setup

• Prerequisites (Node version, Python version, Go version, etc.) — align with confirmed tech stack from pipeline state
• Installation steps
• Environment variables
• Local database setup
• Running locally

3. Coding Standards

• Language/framework conventions
• Linting/formatting rules
• Naming conventions
• File organization
• Comment/documentation standards

4. Implementation Order

Based on Sprint 1 tasks, specify:

• What to build first
• Database migrations
• API endpoints to implement
• Frontend screens to build
• Integration points

5. Key Implementation Notes

• Complex logic explanations
• Third-party integration details
• Performance considerations
• Security implementation details

6. Testing Strategy

• Unit test approach
• Integration test approach
• Test data setup
• CI/CD test pipeline

7. Deployment Guide

• Build process
• Environment configuration
• Deployment steps
• Rollback procedure

Output Template

# Implementation Plan: [Project Name]

## Project Structure
[Directory tree]

## Development Setup
### Prerequisites
### Installation
### Environment Configuration
### Running Locally

## Coding Standards
[Conventions and rules]

## Implementation Order
### Phase 1: Foundation
### Phase 2: Core Features
### Phase 3: Integration
### Phase 4: Polish

## Key Implementation Notes
[Complex areas and how to handle them]

## Testing Strategy
[How to test each layer]

## Deployment Guide
[How to deploy to production]

## Next Steps
[Immediate actions to start development]

Optional: Begin Implementation

If the user says "start coding" or "implement it":

1. Create the project structure
2. Set up configuration files
3. Initialize the repository
4. Create the first migration/schema
5. Implement Sprint 1 features
6. Write tests as you go

Rules

• The implementation plan must be executable by a developer who hasn't seen the prior steps
• Include specific file names and paths
• Reference specific requirements from the PRD by ID
• Follow the architecture design exactly
• Use the tech stack specified in the architecture (which aligns with the user's confirmed preferences from the tech preferences checkpoint)
• Include error handling and logging from the start
• Write tests alongside code, not after
• Commit frequently with descriptive messages
• If you begin implementation, create a git repo and make initial commits