up-2-cataloging-requirements
Turns a vision, workshop transcripts, notes or an interview into a requirements catalog (docs/requirements.md) with functional requirements as role and need (FR), measurable non-functional requirements (NFR) with a verification method, and constraints (C) under stable identifiers, and returns a conflict ledger of contradictions, duplicates and open decisions for the human review gate. Runs an elicitation interview when there is no workshop material. Use when the user asks to gather, write, extract, classify or update requirements, user stories, NFRs or constraints for a spec-driven or use-case-driven project, adds, defers or drops a requirement in the catalog, or hands over meeting notes to consolidate. Not for the detailed behavior of one feature (that is a use case specification) and not for brainstorming a design.
Pinned to revision a5e959f4838b, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/up-2-cataloging-requirements/SKILL.md
- skills/up-2-cataloging-requirements/references/conventions.md
- skills/up-2-cataloging-requirements/references/elicitation-questions.md
- skills/up-2-cataloging-requirements/references/row-quality.md
- skills/up-2-cataloging-requirements/scripts/check_requirements.py
- skills/up-2-cataloging-requirements/scripts/spec_model.py
- skills/up-2-cataloging-requirements/templates/conflict-ledger.md
- skills/up-2-cataloging-requirements/templates/requirements.md
Every link opens the file at its source, pinned to the revision this page describes.