โ† Back to Devchain
๐Ÿš€
Quick Start Guide
1
Discuss & Create Master Plan
User Brainstormer

Start a conversation with the Brainstormer agent. Describe your requirements, features, or changes. The Brainstormer creates a Master Plan with phases, epics, and sub-epics.
2
Technical Validation
Brainstormer SubBSM

The Brainstormer sends the draft plan to SubBSM for technical validation against the codebase. This loop continues (up to 10 rounds) until the plan is solid.
3
Review & Approve Master Plan
User

Review the final Master Plan. Check phases, epics, acceptance criteria, and scope. Approve to proceed or request changes.
4
Epic Decomposition
Brainstormer

After approval, the Brainstormer creates the epic hierarchy:
  • Phase Epics (Draft) โ€” high-level deliverables
  • Sub-Epics (New) โ€” individual tasks with acceptance criteria
  • Backlog Epic (Backlog) โ€” out-of-scope items
5
Prepare Epics for Execution
User

On the Board, move all Phase Epics you want to complete together to "New" status. Leave epics in "Draft" for future sprints.
6
Trigger Execution
User Epic Manager

Assign the first Phase Epic to the Epic Manager. This triggers the automated execution loop.
7
Automated Execution Loop
System Epic Manager Coder

The system runs autonomously:
  • Coder picks tasks, implements, tests, submits for review
  • Epic Manager reviews โ†’ Approve (Done) / Revise (back to Coder)
  • Repeat until all sub-epics in the Phase are Done
8
Code Review
Epic Manager Code Reviewer

When all epics complete, the Code Reviewer analyzes git diffs, checks architectural standards, and generates findings.
9
Remediation & Iteration
Code Reviewer Brainstormer

The Code Reviewer sends findings to Brainstormer, who creates remediation epics. The cycle repeats as needed.
1
Planning
USER
Requirements Provider
โ†“
requirements
Brainstormer
Architect / Planner
draft plan
โ†’
SubBSM
Technical Validator
โ†
technical feedback
โ†ป Technical Validation Loop (up to 10 rounds)
โ†“
final plan
USER
Approve / Reject
โ†“
approved

Created Epic Hierarchy

Phase Epic Draft
Sub-Epic 1 (Task:1) New
Sub-Epic 2 (Task:2) New
Sub-Epic 3 (Task:3) New
BACKLOG Epic Backlog
2
Execution Loop

โšก User Trigger (Manual Step)

  1. Move all epics to be completed together โ†’ "New" status
  2. Assign the first Phase Epic โ†’ Epic Manager
โ†“
triggers automation
Epic Manager
Reviewer / Controller
assigns task
โ†’
Coder
Task Executor
Coder Actions:
  1. Pick task (lowest # tag)
  2. Set "In Progress"
  3. Read requirements
  4. Implement & test
  5. Document work
  6. Set "Review"
โ†“
submits for review
Review Decision
APPROVE
โ†’ Done
โ†’ Assign next task
REVISE
โ†’ Back to Coder
with feedback
BLOCKED
โ†’ Blocked status
BACKLOG
New items
discovered
โ†ป Repeat until all sub-epics in phase are Done
โ†“
Phase Complete
Phase Epic โ†’ "Review" ยท Pick next Phase from "New" pool
3
Code Review (After All "New" Epics Complete)
Epic Manager
Requests review
all phases done
โ†’
Code Reviewer
Autonomous Reviewer
Code Reviewer Actions:
  1. Find all epics in "Review"
  2. Analyze git diffs
  3. Check architectural standards
  4. Generate findings report
โ†“
sends findings
Brainstormer
Creates remediation epics
โ„น
Agent Summary
Agent Role Inputs Outputs
Brainstormer Architect / Planner User requirements, Review findings Phase Epics, Sub-Epics, Backlog
SubBSM Technical Validator Draft plans Technical validation feedback
Epic Manager Reviewer / Controller Sub-epics in Review Approve/Revise decisions, Assignments
Coder Task Executor Assigned sub-epics Implemented code + documentation
Code Reviewer Autonomous Reviewer Completed phases Architectural findings โ†’ new epics
User
Brainstormer
SubBSM
Epic Manager
Coder
Code Reviewer