--- name: make-change description: Skill to make changes in the current project context. Use it whenever the functionality or behavior of the project needs to be modified. --- # Make Change Skill ## Process - Read relevant context with `get-context` unless `workflow` has already done so. Search context and documentation for applicable constraints and guardrails. - Before implementation, update the relevant specification with the requested intent and acceptance needs. Use applicable `context-*` skills and `document-context`; do not put implementation details in context. Resolve blocking gaps first. - A change is context-neutral only when it preserves all documented expectations and adds no intent or acceptance need (for example, formatting, refactoring, or a dependency update without behavior change). When unsure, treat it as non-neutral. State any context-neutral rationale in the summary. - Capture broader recurring conventions when they matter. Implement only documented changes or context-neutral work, and follow any approval policy in `context/README.md`. - Review user-facing documentation for every change. Update it when behavior, setup, configuration, interfaces, workflows, or troubleshooting changes; otherwise state why no update applies. - Run relevant quality checks and report results, skipped checks, and limitations. A context validator does not verify implementation behavior.