What problem does it solve? It standardizes how a main agent authors planning documents in the rad-orc workflow, ensuring Requirements, Master Plans, and amendments follow a parser-enforced structure that downstream orchestration can explode into executable phases and tasks. ## Core Features & Use Cases - Mode-based routing: Three self-contained workflows — requirements, master-plan, and amendment — selected by the caller and followed inline by the main agent, never delegated to subagents. - Contract-rich task authoring: An authoring standard that pins interfaces, external surfaces, and seams into each task so coding agents execute without opening other documents. - Parser-safe output contracts: Templates and heading discipline (## P{NN}:, ### P{NN}-T{MM}:) with retry guidance for structured parse errors, capped at 3 attempts. - Use Case: After a /rad-brainstorm session reaches consensus, the main agent authors a Requirements document, then later receives the spawn_master_plan action and produces a Master Plan whose tasks a coding agent executes directly. ## Quick Start Declare a mode such as requirements, master-plan, or amendment and follow the corresponding workflow reference to author the planning document.
