task-startlisted
Install: claude install-skill real-case/marvin-toolkit
# Spec Create
Co-create a spec with the user through structured dialogue. The spec is the contract between
human intent (Phase 1) and AI execution (Phase 2) — it must be specific enough to implement
**headless**, with no access to this dialogue.
## Core principles
- **A spec that can't be tested is a wish.** Every acceptance criterion has an `oracle` proof.
- **Understand before formalizing.** Surface ambiguity early through domain-specific questions, not templates.
- **The spec IS the plan.** "Chosen Approach" + the `spec-contract` block replace a separate implementation plan — they contain enough for an autonomous agent to execute and bound exactly which files it may touch.
- **The spec is a validated contract, not prose.** Before dispatch it passes a mechanical gate (the `spec` tool), not just a self-read checklist.
## Input
`$ARGUMENTS` — one of:
- Free-form text description of the task
- Tracker reference (`PROJ-123`, `#42`, URL)
- File path to an existing description
If no arguments, ask the user what they want to build or fix.
---
## Step 0: Routing
Before intake, decide whether this request belongs here at all. Gather evidence from exactly four
cheap sources — no more:
1. **The request text** — `$ARGUMENTS`, or the user's answer if it was empty.
2. `git status --short` — is the change already written?
3. `git log --oneline -3` — what just happened on this branch?
4. **The spec directories listed in step 1.3** — read the frontmatter `slug` and `status` of