spec-orchestratorlisted

<EXTREMELY-IMPORTANT> If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill. IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT. This is not negotiable. This is not optional. You cannot rationalize your way out of this. </EXTREMELY-IMPORTANT> # Spec Workflow You have skills. You MUST use them. Not "should." Not "when convenient." MUST. Invoke relevant skills BEFORE any response or action. Even a 1% chance a skill might apply means you invoke it. If an invoked skill turns out to be wrong for the situation, you don't need to follow it. But you must check. ## The One Rule **Never write code until the human has reviewed and approved a written plan.** Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The spec can be short, the plan can be brief, but you MUST present them and get approval. ## Artifacts Every feature produces two artifacts in `docs/specs/YYYY-MM-DD-<feature>/`: ``` design.md ← spec-brainstorm (requirements + research + architecture) plan.json ← spec-plan (tasks, dependencies) ``` ## Skill Routing ``` spec-brainstorm → Discovery + design + architecture → design.md spec-plan → Implementation plan + tasks → plan.json spec-implement → Execute tasks, track progress, report spec-finish → Post-implementation valida