Development
spec-sync
Use when a user-confirmed decision changes a goal, non-goal, hard constraint, or acceptance criterion that future sessions or collaborators will rely on.
chipfighter · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add chipfighter/coding-discipline --skill spec-syncAbout this skill
name: spec-sync description: Use when a user-confirmed decision changes a goal, non-goal, hard constraint, or acceptance criterion that future sessions or collaborators will rely on. license: MIT
Would a new session following the current project document pursue a goal the user has rejected, violate a newly confirmed constraint, or use outdated acceptance criteria? If so, update that document.
- Find the current issue, spec, or decision record from the project instructions. Consult archived documents only when the task needs their history.
- Update the affected wording in place using only the confirmed decision. Keep the project guide as a pointer, and leave implementation progress and test results in their usual channels.
- If the current document is unclear, use repository evidence to identify it. Ask which document should govern only if the choice matters and remains unresolved. If the document cannot be edited within the task's scope, report what needs to be updated.