spec-guidelisted

Create role-based instructions for a feature delivered by a spec, split into developer, admin, and user guidance, then verify every numbered step through its real delivery vehicle. Use after or near spec completion when someone asks how to configure, operate, or use the feature and needs browser, API/MCP, Telegram, email, CLI, webhook, worker, or design evidence rather than untested prose.
austinmao/feature-fix-swarm · ★ 3 · AI & Automation · score 69

Install: claude install-skill austinmao/feature-fix-swarm

# /spec-guide [NNN] [--no-live] [--output PATH] ## Host dispatch contract - Codex: invoke skills as `$skill`; use Codex collaboration roles and GPT-5.6 model tiers. - Claude: invoke skills as `/skill`; use Claude Agent/Skill tools and Claude model aliases. - A bare `/skill` in this shared source denotes the Claude form; Codex dispatches the same named skill as `$skill`. - Resolve `volume` to Codex Luna low / Claude Haiku, `execution` to Codex Terra medium / Claude Sonnet, and `judgment` to Codex Sol high / Claude Opus. (`frontier` — Codex Sol xhigh / Claude Fable — is the planning-only tier, not used by this verification fan-out.) Produce instructions that have survived the same journey the reader will take. Do not treat a unit test, screenshot, or prior completion claim as a substitute for exercising the documented surface. This is an operating guide for the shipped feature, not a retelling of its implementation or release history. Include a build, migration, promotion, cutover, or rollback step only when a developer or administrator must still perform it to configure, use, recover, or retire the feature today. Otherwise cite it as background at most. A role with no current operating surface gets a source-backed `N/A`; do not fill the section with historical delivery tasks. ## Step 1 — Resolve and collect Resolve the spec from the argument, otherwise from the branch numeric prefix. Fail closed if zero or multiple `specs/<NNN>-*` directories match. ```bash bash "$(dirn