Menü
Command reference for Genesis Spec-Kit. Pass a command name for detailed help on that command.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | Help |
| description | Command reference for Genesis Spec-Kit. Pass a command name for detailed help on that command. |
| argument-hint | [command-name] |
Read that skill's SKILL.md and present: its description, argument hint and flags, process summary, and natural-language triggers. If it doesn't exist: "Unknown command '{name}'. Run /genesis-help for the full list."
# Genesis Spec-Kit
A spec-driven development pipeline. Features travel gated phases from idea to
shipped code; a quality-audit loop runs to zero findings at every boundary.
All state lives in plain files under .genesis/.
## Pipeline (in order)
| Command | What it does |
|---|---|
| /genesis-brainstorm | Interactive ideation + decision capture at any boundary |
| /genesis-feature | Write the feature design doc (WHY + SHAPE) |
| /genesis-specify | Write the master spec (WHAT) + the micro-spec plan |
| /genesis-clarify | Find and close holes in the spec before North Star |
| /genesis-northstar | Write the perfect-world vision + quality dimensions |
| /genesis-micro | Write all micro specs for one group |
| /genesis-implement | Implement one micro spec → one commit → one PR |
| /genesis-a1..a5 | The five audit lenses (run per group, loop to zero) |
| /genesis-final | The F-pass: the lenses feature-wide + Dreamland + Simulation |
| /genesis-accept | The boundary ritual — record approval, journal, advance (no git) |
### Audit order (per group): A1 → A2 → A3 → A4 → A5 (each loops to zero findings)
### The Double Gate: A3 cannot start until A1 is at zero findings.
### After all groups accepted: /genesis-final, then /genesis-closure (PR to main).
## Utility
| Command | What it does |
|---|---|
| /genesis-init | Scaffold the kit and pick a mode |
| /genesis-discover | Build the project profile through guided conversation |
| /genesis-constitute | Write the project's constitution (its supreme law) |
| /genesis-design | Author project-level design docs (architecture, ADRs, journeys) |
| /genesis-amend | Formally amend the constitution, with impact analysis |
| /genesis-closure | Push the branch and open a PR (the only step that does git) |
| /genesis-status | Where am I? (read-only, any time) |
| /genesis-resume | Pick up where I left off (read-only, any time) |
| /genesis-help | This reference |
## Quick start
1. /genesis-init — set up the kit
2. /genesis-discover — tell the kit about your project
3. /genesis-constitute — define the rules
4. /genesis-brainstorm — start your first feature
- "help"
- "what commands"
- "how do I"
- "command list"
The drift check. Compare what was built against the design doc and master spec. Sets the Double Gate — A3 cannot start until A1 is at zero findings.
Mechanical FR/AC compliance. Walk every functional requirement and acceptance criterion and render a binary Pass/Fail with evidence. No judgment about quality, direction, or architecture.
Code/content quality. Dead code, hardcoded values, leftover TODOs, weak error handling, security holes, performance traps, standards violations. Enforces the Double Gate — blocks until A1 is at zero findings.
Vision-gap analysis. Compared to the perfect-world North Star, what is missing, drifting, or underbuilt — and what to add or change now to close the gap. Not a passive alignment scorecard.
Research the world. Real web research to find what the best teams do for every technology and pattern in the build, then implement superior approaches now (not later). The only lens that brings outside knowledge.
The boundary ritual — review what just landed, record an approval, journal it, and advance the phase. The ONLY step that writes approvals, and it does NO git.