up-0-navigating-spec-driven-work
Reads the state of a spec-driven repository (vision, requirements catalog, entity model, use case diagram, use case specifications with their Status, journey test cases, code and tests) and names the single next step and the skill that performs it, following the artifact chain from vision to tests. Also classifies work that is not a change: new behavior before any use case is approved, recovery of an existing system, throwaway, and picks the rigor profile (throwaway, solo, team). Use when the user asks where the project stands, what comes next, which step follows the entity model or an approved use case, whether to go ahead with a step now, whether a piece of work needs use cases or specifications at all, how to start spec-driven development or use-case-driven work on an idea or an existing codebase, to clean the specs, or names spec-driven development without naming an artifact. For a fix, change or feature, use up-1-triaging-change-requests. Routes only; writes no artifact.
Pinned to revision a5e959f4838b, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/up-0-navigating-spec-driven-work/SKILL.md
- skills/up-0-navigating-spec-driven-work/references/conventions.md
- skills/up-0-navigating-spec-driven-work/references/decision-table.md
- skills/up-0-navigating-spec-driven-work/scripts/spec_data.py
- skills/up-0-navigating-spec-driven-work/scripts/spec_model.py
- skills/up-0-navigating-spec-driven-work/scripts/use_case_map.py
- skills/up-0-navigating-spec-driven-work/scripts/workflow_state.py
Every link opens the file at its source, pinned to the revision this page describes.