Skip to main content
The Project Planner breaks down user requests into actionable tasks, plans file structure, and creates dependency graphs for systematic execution.

​
Overview

The Project Planner is a strategic planning agent that analyzes user requests, identifies required components, and creates detailed execution plans with task dependencies. It’s essential for starting new projects or planning major features. Use Project Planner when:
  • Starting new projects from scratch
  • Planning major feature additions
  • Need task breakdown with dependencies
  • Require file structure planning
  • Want agent assignment recommendations

​
Key Capabilities

Request Analysis

Parses user requests to understand domain, features, constraints, and risk areas

Task Breakdown

Creates detailed tasks with INPUT→OUTPUT→VERIFY criteria for each step

Dependency Mapping

Generates task dependency graphs showing what must be done first

Agent Assignment

Recommends which specialist agent should handle each task

​
Skills Used

​
4-Phase Workflow

The Project Planner follows a structured BMAD-inspired workflow:
PhaseNameFocusOutputCode Allowed?
1ANALYSISResearch, brainstorm, exploreDecisions❌ NO
2PLANNINGCreate plan{task-slug}.md❌ NO
3SOLUTIONINGArchitecture, designDesign docs❌ NO
4IMPLEMENTATIONCode per planWorking code✅ YES
XVERIFICATIONTest & validateVerified project✅ Scripts
During planning phase, agents MUST NOT write any code files! Only the plan markdown file.

​
Planning Process

​
Step 1: Request Analysis

Parse the request to understand:
  • Domain: What type of project? (ecommerce, auth, realtime, cms)
  • Features: Explicit + Implied requirements
  • Constraints: Tech stack, timeline, scale, budget
  • Risk Areas: Complex integrations, security, performance

​
Step 2: Project Type Detection

Critical: Correctly identifying project type determines which agents to use!
TriggerProject TypePrimary AgentDO NOT USE
”mobile app”, “iOS”, “Android”, “React Native”MOBILEmobile-developer❌ frontend-specialist
”website”, “web app”, “Next.js”WEBfrontend-specialist❌ mobile-developer
”API”, “backend”, “server”BACKENDbackend-specialist-

​
Step 3: Component Identification

Components by Project Type:
ComponentWEB AgentMOBILE Agent
Database/Schemadatabase-architectmobile-developer
API/Backendbackend-specialistmobile-developer
Authsecurity-auditormobile-developer
UI/Stylingfrontend-specialistmobile-developer
Teststest-engineermobile-developer
Deploydevops-engineermobile-developer
mobile-developer is full-stack for mobile projects and handles all layers.

​
Step 4: Task Format

Each task must include:
  • task_id - Unique identifier
  • name - Clear task name
  • agent - Recommended specialist
  • skills - Required skills
  • priority - P0, P1, P2, P3
  • dependencies - Blocking tasks
  • INPUT→OUTPUT→VERIFY - Clear success criteria

​
Step 5: Plan File Creation

Plan files use dynamic naming based on the task, NOT a fixed name like “PLAN.md”.
Naming Convention:
User RequestPlan File Name
”e-commerce site with cart”ecommerce-cart.md
”add dark mode feature”dark-mode.md
”mobile fitness app”fitness-app.md
Required Plan Structure:
SectionMust Include
OverviewWhat & why
Project TypeWEB/MOBILE/BACKEND (explicit)
Success CriteriaMeasurable outcomes
Tech StackTechnologies with rationale
File StructureDirectory layout
Task BreakdownAll tasks with Agent + Skill
Phase XFinal verification checklist

​
Implementation Priority Order

PriorityPhaseAgentsWhen to Use
P0Foundationdatabase-architect → security-auditorIf project needs DB
P1Corebackend-specialistIf project has backend
P2UI/UXfrontend-specialist OR mobile-developerWeb OR Mobile (not both!)
P3Polishtest-engineer, performance-optimizerBased on needs

​
Phase X: Verification

Every plan must include a Phase X verification checklist with mandatory script execution.
# Single command - runs all checks in priority order:
python .agent/scripts/verify_all.py . --url http://localhost:3000

# Priority Order:
# P0: Security Scan (vulnerabilities, secrets)
# P1: Color Contrast (WCAG AA accessibility)
# P1.5: UX Audit (Psychology laws, Fitts, Hick, Trust)
# P2: Touch Target (mobile accessibility)
# P3: Lighthouse Audit (performance, SEO)
# P4: Playwright Tests (E2E)

​
Or Run Individually

# P0: Security Scan
python .agent/skills/vulnerability-scanner/scripts/security_scan.py .

# P1: UX Audit
python .agent/skills/frontend-design/scripts/ux_audit.py .

# P3: Lighthouse (requires running server)
python .agent/skills/performance-profiling/scripts/lighthouse_audit.py http://localhost:3000

​
Example Use Cases

​
Use Case 1: New E-commerce Project

User: "Build an e-commerce site with cart and checkout"

[Project Planner analyzes]

→ Domain: E-commerce
→ Project Type: WEB
→ Features: Product catalog, cart, checkout, payments
→ Components: Database, Backend API, Frontend, Auth, Payments

[Creates plan file: ecommerce-site.md]

Plan includes:
- 25 tasks across 4 phases
- Agent assignments: database-architect, backend-specialist, 
  frontend-specialist, security-auditor, test-engineer
- Dependencies: Schema → API → UI
- Verification checklist

​
Use Case 2: Mobile Fitness App

User: "Mobile fitness tracking app for iOS and Android"

[Project Planner analyzes]

→ Domain: Mobile Health & Fitness
→ Project Type: MOBILE
→ Features: Workout tracking, progress charts, offline sync
→ Agent: mobile-developer (full-stack for mobile)

[Creates plan file: fitness-app.md]

Plan includes:
- React Native + Expo setup
- Offline-first architecture
- Push notifications
- All handled by mobile-developer

​
Best Practices

Task Size

Each task should take 2-10 minutes with one clear outcome

Dependencies

Only mark explicit blockers - avoid hidden dependencies

Verify-First

Define success criteria before coding begins

Context

Explain WHY not just WHAT for better agent decisions

​
Automatic Selection Triggers

Project Planner is automatically selected when:
  • User says “build”, “create”, “start new project”
  • Major feature planning is needed
  • No existing plan file is found
  • User explicitly asks for a plan or roadmap

Orchestrator

Executes the plan with multiple agents

Product Manager

Defines requirements and user stories

Build docs developers (and LLMs) love

Get started for freeTalk to us