Project Planning Workflow

Generate detailed architectural blueprints and implementation roadmaps without writing code.

Overview

Goal: Create comprehensive technical plans before implementation. Agents Used: Planner, Scout. Command: /plan

Workflow

1. Analysis

/plan "refactor the payment system to support subscription tiers"

What happens:

• Planner activates.
• Scout analyzes the current payment implementation to understand constraints.
• Planner breaks down the requirement into user stories and technical tasks.

2. Strategy & Output

The agent generates a structured plan file (e.g., PLAN.md) containing:

• Context Analysis: Current state vs. target state.
• Requirements: Functional and non-functional requirements.
• Implementation Strategy: Phased approach (Phase 1, Phase 2, etc.).
• Technical Decisions: Architecture patterns, database changes, API design.
• Risk Assessment: Potential challenges and mitigation strategies.

3. Review & Iterate

Review the generated plan. If changes are needed, you can refine it:

/plan "update the plan to include Stripe as the provider"

Example Output Structure

# Implementation Plan: Subscription System
 
## Context
Refactor existing one-time payment system to support recurring billing.
 
## Phases
 
### Phase 1: Database Schema
- Create `subscriptions` table.
- Update `users` table with stripe_customer_id.
 
### Phase 2: Stripe Integration
- Implement webhook handlers for `invoice.payment_succeeded`.
- Create subscription management API service.
 
### Phase 3: UI Updates
- Create Pricing page.
- Add "Manage Subscription" portal.

When to Use

• New Features: Before starting any complex feature (/build).
• Refactoring: When changing core systems.
• Migrations: Planning database or framework migrations.
• Documentation: To create technical specs for team alignment.