← Back to Create Plan
/createplan
AI Board Review Workflow for Implementation Planning
Executive Summary
The /createplan command transforms a solution design (from /createsolution or a custom ask)
into a detailed implementation plan with agent assignments. It identifies which specialized
agents (PM, Architect, Security, Developer, QA) should handle each task and which tasks can run in parallel.
The result is an actionable project plan that enables efficient multi-agent execution, with clear dependencies,
parallel execution groups, and stakeholder-ready timeline visualizations.
📋
Generates Tasks
Breaks down solution into actionable implementation tasks
👥
Assigns Agents
Maps each task to PM, Architect, Security, Dev, or QA
⚡
Parallelizes Work
Identifies tasks that can run simultaneously
flowchart LR
subgraph Input
A[Solution or Ask]
end
subgraph "Step 1-3: Plan Generation"
B[Resolve Name]
C[Claude Plan]
D[Gemini Plan]
E[Codex Plan]
end
subgraph "Step 4-6: Synthesis"
F[Merge Plans]
G[Peer Review]
H[Final Plan]
end
subgraph Output
I[Executive Site]
end
A --> B --> C
B --> D & E
C & D & E --> F --> G --> H --> I
style A fill:#ffd700,color:#1a1a2e
style I fill:#4ade80,color:#1a1a2e
style C fill:#d97757,color:#fff
style D fill:#4285f4,color:#fff
style E fill:#10b981,color:#fff
1
Resolve Name
From solution or user
→
2
Clarify
Format plan ask
→
→
4
Synthesize
Merge best elements
→
5
Peer Review
Gemini + Codex feedback
→
6
Finalize
Incorporate feedback
5 Specialized Agents for Task Execution
💼
PM
Orchestration
Coordination
🏗
Architect
System Design
Tech Decisions
🔒
Security
Auth, Network
Hardening
💻
Developer
Implementation
Deployment
Parallel Execution Groups
Tasks are grouped by dependencies. Same group letter = can run simultaneously.
Sequential:
Architecture Design
→
Security Review
Group A:
User Service [Dev-1]
Product Service [Dev-2]
Test Specs [QA]
Group B:
CI Pipeline [QA]
Security Audit [Security]
sequenceDiagram
participant U as User
participant C as Claude
participant G as Gemini
participant X as Codex
participant F as Files
U->>C: /createplan {solution or ask}
C->>F: Read solution file (if exists)
C->>U: Confirm project name
Note over C,X: Step 3: Parallel Plan Generation
par Claude Plan
C->>F: {name}.plan.claude.md
and Gemini Plan
C->>G: Generate plan
G->>F: {name}.plan.gemini.md
and Codex Plan
C->>X: Generate plan
X->>F: {name}.plan.codex.md
end
Note over C,F: Step 4: Synthesis
C->>F: {name}.plan.draft.md
Note over G,X: Step 5: Peer Review (Parallel)
par Gemini Review
C->>G: Review draft
G->>F: {name}.plan.gemini-review.md
and Codex Review
C->>X: Review draft
X->>F: {name}.plan.codex-review.md
end
Note over C,F: Step 6: Final Plan
C->>F: {name}.plan.final.md
C->>F: HTML site deployed
C->>U: URL to presentation
Final Plan Structure
2
Objectives & Success Criteria
Generated Artifacts
{name}.plan.ask.md
Clarified plan ask
{name}.plan.claude.md
Claude's plan
{name}.plan.gemini.md
Gemini's plan
{name}.plan.codex.md
Codex's plan
{name}.plan.draft.md
Synthesized draft
{name}.plan.final.md
Final plan
When to Use /createplan
- After running /createsolution to create an implementation roadmap
- Need to break down a complex project into actionable tasks
- Want clear agent assignments for multi-agent execution
- Need to identify parallel work opportunities
- Preparing for /executeplan to create GitLab board cards
How to Invoke
/createplan {solution file or plan ask}
Example: /createplan clawdbot (uses existing solution file)