flow-spec

# STOP - SKILL ALREADY LOADED **DO NOT call Skill() again. DO NOT load any more skills. Execute directly.** --- ## EXECUTION CONTRACT (MANDATORY - CANNOT SKIP) This skill uses **ENFORCED execution mode**. You MUST follow this exact 8-step sequence. --- ### STEP 1: Clarifying Questions (MANDATORY) **Ask via AskUserQuestion BEFORE any other action.** You MUST gather these inputs from the user — spec quality depends on knowing actors, constraints, and complexity upfront; without these the research query is too broad and the spec will have gaps: ``` AskUserQuestion with these questions: 1. **What to specify**: Project or feature name + brief description - "What system/feature should I specify?" 2. **Actors**: Who interacts with this system? - Options: End Users, Developers, Admins, External Services, Other 3. **Key constraints**: What matters most? - Options: Performance, Security, Compatibility, Scale - (multiSelect: true) 4. **Complexity class**: How complex is this? - Clear (well-understood, straightforward) - Complicated (multiple parts, but knowable) - Complex (emergent behavior, unknowns) ``` If user provided a description inline with the command (e.g., `/octo:spec user authentication system`), use that as the project description but STILL ask remaining questions (actors, constraints, complexity). If user says "skip" for any question, note assumptions and proceed. **DO NOT PROCEED TO STEP 2 until questions answered.** --- ### STEP 2: D...