Claude Code governance for active project specs and reports
Find the current specification, summarize the objective in three bullets, check dependencies, and ask before proceeding. File a report of the result and modified files after completion.
中文Install in Claude Code
Open the repository in Claude Code. The exercise reads a CSV reporting specification and uses the standard library. Specs requiring external libraries need a configured Context7 connection.
- Review `.claude/skills/governance/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.claude/skills/governance/` in your project and save the reviewed file as `.claude/skills/governance/SKILL.md`.
- Start Claude Code from that project's root, then select `/governance` in the slash menu.
Example task
Under {directory: '.project_governance/specs/', feature: 'label-export'}, current report-labels.md asks for a single source column label. The archive contains an older file with the same name.What to check
Select {file: 'report-labels.md', includeArchive: false}. Summarize the objective, absence of external libraries, and absence of a mech_core dependency, then wait for confirmation.
Original SKILL.md on GitHub · Updated
Frequently asked question
Where are completed changes reported?
Use the repository reports directory and its date-and-feature naming convention. Record pass or fail, changed files, and verified external dependencies.