up-7-implementing-use-cases
Implements or synchronizes exactly one approved use case in code, in any stack: checks the Status gate, reads only the use case, its linked requirement rows, the entity model and the guideline file, shows an element-to-code plan with the list of decisions the specification leaves open, then generates a new slice or applies only the behavioral difference between the previous and the current specification, marks rule-enforcing code with the rule identifier, audits the diff for out-of-scope changes and handles schema changes as a guarded sub-procedure. Use when the user says implement, build, generate, sync or synchronize UC-XXX, asks to bring code in line with a changed use case, or asks for a database migration or schema change after the entity model changed. Not for work that names no use case and not for deciding whether a report is a bug or a change.
Pinned to revision aecf4e91025c, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/up-7-implementing-use-cases/SKILL.md
- skills/up-7-implementing-use-cases/references/conventions.md
- skills/up-7-implementing-use-cases/references/element-to-code.md
- skills/up-7-implementing-use-cases/references/invention-list.md
- skills/up-7-implementing-use-cases/references/schema-changes.md
- skills/up-7-implementing-use-cases/references/synchronization.md
- skills/up-7-implementing-use-cases/scripts/finish_change.py
- skills/up-7-implementing-use-cases/scripts/guard_check.py
- skills/up-7-implementing-use-cases/scripts/scope_audit.py
- skills/up-7-implementing-use-cases/scripts/spec_model.py
- skills/up-7-implementing-use-cases/scripts/uc_change_list.py
- skills/up-7-implementing-use-cases/scripts/unrecorded_changes.py
- skills/up-7-implementing-use-cases/templates/implementation-plan.md
Every link opens the file at its source, pinned to the revision this page describes.