speckit-auto-runlisted
Install: claude install-skill opsmill/infrahub-mcp
## User Input
```text
$ARGUMENTS
```
You **MUST** consider the user input before proceeding (if not empty).
## Outline
You are running the **full speckit pipeline** end-to-end. The user's input (above) is the feature description that will seed the specification phase.
Execute every phase below **in order**, making all decisions autonomously. Do not stop to ask the user for input between phases — if a phase requires choices (e.g., clarification questions in specify, research decisions in plan), use your best judgment and proceed. The user expects a hands-off, one-shot execution.
After **each phase**, invoke the `speckit-checkpoint-commit` skill to commit the artifacts produced by that phase before moving on.
> Each phase below is executed by invoking the named skill (e.g. via the agent's Skill tool). Skills are agent-agnostic, so this workflow runs identically across any harness that supports skill discovery — not only those exposing speckit slash commands.
### Phase 1 — Specify
Invoke the `speckit-specify` skill with the user's feature description (`$ARGUMENTS`).
- Complete the full specify workflow: generate a short name, create the spec directory, write `spec.md`, run quality checks.
- If clarification questions arise, answer them yourself based on context and best judgment — do **not** pause for user input.
- Commit the spec artifacts.
### Phase 2 — Plan
Invoke the `speckit-plan` skill.
- Complete the full plan workflow: research unknowns, generate `plan.md`,