Menu
Use when a SPEC.md exists or is needed and the user wants gaps found through an interview before implementation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user says they are stepping away and the agent should continue without interactive approvals
Use when running e2e tests, debugging test failures, or fixing flaky tests. Covers failure taxonomy, fix rules, and workflow. Never changes source code logic or API without spec backing.
Use when auditing how well the shared agent instructions (AGENTS.md, skills) hold up in real sessions — sampling transcripts via recall, scoring them against the gap rubric, and turning findings into ratified amendments
Use when preparing clean, logical git commits from an existing working tree
Use when syncing a feature branch onto the latest origin base branch via git rebase.
Fetch latest from origin, prune remote-tracking refs, delete stale local branches and worktrees, and fast-forward important branches. Use when tidying up a worktree-based repo layout.
| name | spec-interview |
| description | Use when a SPEC.md exists or is needed and the user wants gaps found through an interview before implementation |
Use this workflow to turn an incomplete SPEC.md into an implementation-ready
contract.
spec-best-practices.SPEC.md; if none is provided, search likely colocated paths.REQ-* requirementsPrefer questions about data models, invariants, edge cases, security, operability, compatibility, and scope boundaries. Avoid questions that can be answered by reading the repo, or already answered in the surface's Decisions or the doctrine.