compile-change
Skill8 starsChanged 5 months agoMITView on GitHub
Use when an approved product wiki change needs implementation, checks, verification evidence, or reconciliation with code.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- apply-wiki-changeSkill
- generate-checksSkill
- import-codebaseSkill
- propose-changeSkill
- reconcile-wikiSkill
- review-architectureSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 7 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use the lightest safe path.
- Very specific: line 14
If the template is missing, do not invent a plan shape from memory.
- Distinctive: line 17
Stop only if the canonical contract cannot be restored.
- Very specific: line 21
Read references/blast-radius-rubric.md before choosing the path.
- Distinctive: line 23
Use a light path when the change is tiny, mechanical, and has no product or architecture impact.
- Distinctive: line 25
Use the full path when the change affects behaviour, user journeys, data, security, architecture, dependencies, or multiple modules.
- Very specific: line 46
update checks/manifest.json so every acceptance criterion in the approved change has a command that will run against code
- Very specific: line 54
use templates/compiler-plan-template.md when the change is medium or high risk
- Distinctive: line 57
add the smallest failing check for the next acceptance criterion
- Distinctive: line 58
run it and confirm it fails for the expected reason
- Distinctive: line 60
run it again and confirm it passes
- Very specific: line 62
Add or update PW: anchors at important routes, services, workflows, domain modules, and tests.
- Very specific: line 63
Use anchors as signposts, not comments on every line.
- Very specific: line 64
Every active capability and rule unit must carry at least one PW: anchor in code, or wiki-anchor-lint fails.
- Very specific: line 65
Run checks, including node scripts/checks-lint.mjs --run, node scripts/wiki-anchor-lint.mjs --write-report, node scripts/ratchet-lint.mjs, …
- Very specific: line 70
update or review the local source map in .product-wiki/source-map.json
- Very specific: line 72
keep each unit's ## What it does for you in plain product language.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Compile Change
Your job is to compile an approved product wiki change into code and executable checks. Use the lightest safe path.
Template contract
For medium or high-risk changes, load templates/compiler-plan-template.md before implementation.
If the template is missing, do not invent a plan shape from memory.
First run node scripts/repair-contracts.mjs --write, then re-run node scripts/template-lint.mjs.
Continue if repair succeeds.
Stop only if the canonical contract cannot be restored.
Choose path by blast radius
Read references/blast-radius-rubric.md before choosing the path.
Use a light path when the change is tiny, mechanical, and has no product or architecture impact.
Use the full path when the change affects behaviour, user journeys, data, security, architecture, dependencies, or multiple modules.
Full path
- Apply or confirm the approved wiki change.
- Locate the blast radius:
wiki/overview.md- wiki units
- existing
PW:wiki anchors from code search - code paths
- tests
- dependencies
- design system files
- Decide reuse or refactor:
- reuse existing capability where possible
- raise a refactor proposal before adding fragile branches
- Define executable checks before application code:
- acceptance criteria to tests
- for each acceptance criterion, apply the edge-case triggers in
.agents/skills/generate-checks/references/check-patterns.md(boundary, cardinality, round-trip, time and calendar, ordering, presence, identity; plus state and scale when introduced) and add a check for every trigger it matches, not only the happy path - rules to regression checks
- journeys to integration or E2E checks where appropriate
- update
checks/manifest.jsonso every acceptance criterion in the approved change has a command that will run against code - register a runnable command that names a real test file for each acceptance criterion; see
references/blast-radius-rubric.mdfor the command and shell-quoting gotchas
- Plan the edit:
- files
- interfaces
- data paths
- risk points
PW:anchors to add or update at important implementation boundaries- use
templates/compiler-plan-template.mdwhen the change is medium or high risk - save the compiler plan under
docs/compiler-plans/, never inintake/proposals/(proposal-lint treats every file there as a proposal and will fail it)
- For behaviour changes, use a red-green loop:
- add the smallest failing check for the next acceptance criterion
- run it and confirm it fails for the expected reason
- implement the smallest code change
- run it again and confirm it passes
- Implement the smallest coherent code change.
- Add or update
PW:anchors at important routes, services, workflows, domain modules, and tests. Use anchors as signposts, not comments on every line. Every activecapabilityandruleunit must carry at least onePW:anchor in code, orwiki-anchor-lintfails. - Run checks, including
node scripts/checks-lint.mjs --run,node scripts/wiki-anchor-lint.mjs --write-report,node scripts/ratchet-lint.mjs, and the product repo's normal test command. - Reconcile the wiki:
- review
wiki/overview.mdif implementation changes the whole-product map - update traceability
- update dependency links
- update or review the local source map in
.product-wiki/source-map.json - record decisions or assumptions discovered during implementation
- keep each unit's
## What it does for youin plain product language; move any implementation detail you add during compile under## How it works, never into the product prose - design system, important: adding any UI file turns on the design-system lint cascade; see
references/blast-radius-rubric.mdbefore introducing UI, or keep the change UI-free
- Mark the proposal
implementedonly after the manifest coverage and code checks pass. - Run
node scripts/product-wiki-check.mjs.
Production questions
For production changes, ask:
- Does this cross a trust boundary?
- Does this affect permissions, secrets, auth, or user data?
- Does this require migration or backward compatibility?
- Will we know if it fails in production?
- Is rollback obvious?
Output
Return:
- Proposal compiled.
- Checks added or run.
- Code paths changed.
PW:anchors added or updated.- Verification evidence.
- Wiki reconciliation notes.
Related skills
generate-checks: when acceptance criteria do not yet have executable checks.review-architecture: when reuse, data ownership, module boundaries, or refactor pressure are material.reconcile-wiki: after implementation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

