forge-brainstorming

Full-lifecycle development with persistent teammates — discovery, design, planning, TDD execution, deep review, and PR creation in one unified flow

Persistent system designer teammate for brainstorming sessions. Designs multiple implementation approaches with trade-offs, produces actionable blueprints with file maps, component designs, data flows, and build sequences. Uses opus model for deeper architectural reasoning on complex trade-off analysis. Persists across design iterations for refinement based on user feedback. <example> Context: Scout completed exploration, user answered clarifying questions assistant: "Sending architect the exploration findings and user requirements to design approaches" </example> <example> Context: User wants to refine the chosen architecture approach user: "Can you make approach B work with the existing event bus instead?" assistant: "Sending architect the refinement request with the constraint" </example>

Persistent implementation lead teammate for brainstorming sessions. Executes TDD tasks from the implementation plan one at a time: writes failing tests, implements minimal solutions, verifies, commits, and self-reviews. Maintains context across tasks — remembers patterns from previous tasks to improve consistency. <example> Context: Plan approved, worktree set up, ready to implement assistant: "Sending builder Task 1 with full description and architectural context" </example> <example> Context: Reviewer found spec compliance issues in builder's work assistant: "Sending builder the reviewer's findings to fix before re-review" </example>

Persistent PR and integration specialist teammate for brainstorming sessions. Handles the final phase: verification, branch finishing (4 options), PR creation, and automated PR review with confidence-based scoring. Coordinates the handoff from implementation to merged code. <example> Context: Deep review passed, ready for PR assistant: "Spawning closer to handle verification, PR creation, and automated review" </example> <example> Context: User wants to skip PR and just merge user: "Just merge it directly" assistant: "Sending closer the merge instruction instead of PR flow" </example>

Persistent quality gatekeeper teammate for brainstorming sessions. Operates in three modes: (1) Spec validation — checks design documents for completeness and consistency. (2) Per-task review during execution — spec compliance then code quality, with the "Do Not Trust the Report" protocol. (3) Deep review after all tasks — applies 5 specialized lenses (tests, errors, types, comments, simplification) to the full implementation. <example> Context: Builder completed a task, needs spec + quality review assistant: "Sending reviewer the task spec and builder's report for two-stage review" </example> <example> Context: All tasks complete, need deep specialized review assistant: "Switching reviewer to deep mode for 5-lens quality analysis" </example> <example> Context: Spec document needs validation before planning assistant: "Sending reviewer the spec document for completeness and consistency check" </example>

Persistent codebase explorer teammate for brainstorming sessions. Performs multi-pass analysis that accumulates understanding: similar features, architecture mapping, and integration point identification. Unlike ephemeral code-explorer agents, scout retains context across passes and reports via team coordination. <example> Context: Brainstorming session starts, codebase needs exploration user: "/brainstorming add real-time notifications" assistant: "Spawning scout to explore the codebase for notification patterns and architecture" </example> <example> Context: Scout completed first pass, needs deeper analysis assistant: "Sending scout a follow-up to trace the event system integration points" </example>

Full-lifecycle teammate orchestration for complex features. Use when the user invokes /brainstorming or asks for "end-to-end development", "full lifecycle", "discovery to PR", "teammate-driven development", or "brainstorming with agents". Covers discovery, design, planning, TDD execution, deep review, and PR creation with persistent named teammates. DO NOT use for simple tasks, single-file changes, bug fixes, or straightforward features where the implementation path is clear.