← Back to Shared Artifacts
/executeplan
Bridge Planning to Execution via GitLab Board
Executive Summary
The /executeplan command bridges the gap between planning and execution.
It takes your /createsolution and /createplan artifacts
and generates a fully populated GitLab project board with trackable cards.
Once set up, the entire project can be executed through board-driven workflow - humans move cards
to "ready", AI executes tasks, and progress is tracked visually. No CLI needed after initial setup.
📋
Creates GitLab Project
Sets up repo with Kanban board and labels
📝
Generates Cards
INFO, TASK, PHASE, and DECISION cards
🔗
Links Dependencies
Connects blocked cards to blockers
⚙
Enables Board-Driven
Human/AI collaboration via card status
From Planning Artifacts to Actionable Board
→
/executeplan
Parse artifacts
Create project
Generate cards
→
Output (Execution)
GitLab Board
Trackable Cards
Board-Driven Workflow
flowchart LR
subgraph Input
A[Solution File]
B[Plan File]
end
subgraph "Setup Phase"
C[Resolve Name]
D[Check/Create Project]
E[Verify Labels]
end
subgraph "Card Generation"
F[INFO Cards]
G[First Phase Tasks]
H[PHASE Cards]
I[DECISION Cards]
end
subgraph Output
J[GitLab Board]
end
A & B --> C --> D --> E
E --> F & G & H & I
F & G & H & I --> J
style A fill:#ffd700,color:#1a1a2e
style B fill:#60a5fa,color:#1a1a2e
style J fill:#22c55e,color:#1a1a2e
1
Resolve
Project name & group
→
2
Check Source
Verify folder exists
→
3
Create Project
GitLab repo + board
→
4
Parse
Extract from artifacts
→
5
Generate
Create all cards
→
6
Link
Connect dependencies
→
INFO Cards
Reference cards for solution and plan overviews. Not actionable - just documentation.
INFO: Solution - clawdbot
INFO: Plan - clawdbot
TASK Cards (First Phase)
Immediately workable tasks with acceptance criteria. Created for Phase 0/1 only.
T0.1: Inventory existing services
T0.2: Validate runner networking
PHASE Cards
Meta-cards for remaining phases. When moved to "ready", AI spawns task cards.
PHASE 2: Pipeline Setup
PHASE 3: Integration Testing
DECISION Cards
Cards requiring human decision. Check an option, move to "ready" to record choice.
DECISION: D1 Database selection
DECISION: D2 Auth method
sequenceDiagram
participant U as User
participant E as /executeplan
participant G as GitLab
participant F as Files
U->>E: /executeplan {descriptor}
E->>F: Read solution file
E->>F: Read plan file
Note over E,G: Project Setup
E->>G: Check/create project
E->>G: Verify labels exist
Note over E,G: Card Generation
E->>G: Create INFO: Solution
E->>G: Create INFO: Plan
loop First Phase Tasks
E->>G: Create TASK card with criteria
end
loop Remaining Phases
E->>G: Create PHASE meta-card
end
loop Grey Areas
E->>G: Create DECISION card
end
Note over E,G: Linking
E->>G: Link DECISIONs to blocked PHASEs
E->>U: Report: Board URL + card summary
Board-Driven Execution After Setup
Backlog
DECISION: D1
PHASE 2
PHASE 3
Ready
T0.1: Inventory
T0.2: Validate
In Progress
T0.3: Configure
After /executeplan Completes
- Human: Review DECISION cards, check option, move to "ready"
- Human: Move first phase task cards to "ready" to prioritize
- AI: Run
/gitlab-board {descriptor} all to execute ready tasks
- AI: Completes tasks, moves to "review" or "done"
- Human: Review completed work, close cards or provide feedback
- Human: When phase complete, drag next PHASE card to "ready"
- AI: Creates task cards for that phase automatically
- Repeat: Continue until project complete
Prerequisites
- At least one planning artifact must exist:
ainotes/shared/createsolution/{name}.final.md (from /createsolution)ainotes/shared/createplan/{name}.plan.final.md (from /createplan)
- Source folder must exist:
$HOME/projects/{name}/
- glab CLI configured at:
/home/administrator/projects/devscripts/glab
- Supported groups:
administrators (ID: 10), developers (ID: 13)
How to Invoke
/executeplan {descriptor}
Examples:
/executeplan clawdbot (auto-detect group)
/executeplan administrators/cicd (explicit group)