Change Request
SkillTurns every new requirement into a written, dated change record before any work starts — verbatim request, facts, plan, tracker and progress log.
Best for
- Keeping a durable memory of what was asked and decided
- Resuming work after an interruption
- Teams that want traceability without heavy tooling
What you give it
- The request, word for word
- Optionally: the impact analysis
What you get back
- A new file docs/changes/CR-<date>-<title>.md with the request, facts, decisions, plan, tracker and log
- An updated index of open changes
How it works
- Evaluates the request against requirements and decisions, runs the impact check.
- Splits the work into tasks; keeps a risky task (data model, payments) in its own record so it can wait for approval.
- Creates the dated file from the template and adds the index row.
- Keeps the tracker and log up to date after every step.
Example
You: /change-request add CSV export of invoices
Result: Created docs/changes/CR-2026-03-14-1130-invoice-csv-export.md (request quoted verbatim; plan: 3 tasks; tracker: all OPEN) and added it to docs/changes/README.md.
Limits — please read
- It records and plans; it does not build.
- A change record is only as good as the verbatim request.