flow-spec

1> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.
2> Cross-reference commands use installed skill names in Codex rather than `/octo:*` slash commands.
3> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.
4> For host tool equivalents, see `skills/blocks/codex-host-adapter.md`.
5 
6 
7# STOP - SKILL ALREADY LOADED
8 
9**DO NOT call Skill() again. DO NOT load any more skills. Execute directly.**
10 
11 
12## EXECUTION CONTRACT (MANDATORY - CANNOT SKIP)
13 
14This skill uses **ENFORCED execution mode**. You MUST follow this exact 8-step sequence.
15 
16 
17### STEP 1: Clarifying Questions (MANDATORY)
18 
19**Ask via AskUserQuestion BEFORE any other action.**
20 
21You 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:
22 
23```
24AskUserQuestion with these questions:
25 
261. **What to specify**: Project or feature name + brief description
27   - "What system/feature should I specify?"
28 
292. **Actors**: Who interacts with this system?
30   - Options: End Users, Developers, Admins, External Services, Other
31 
323. **Key constraints**: What matters most?
33   - Options: Performance, Security, Compatibility, Scale
34   - (multiSelect: true)
35 
364. **Complexity class**: How complex is this?
37   - Clear (well-understood, straightforward)
38…