agentleFS
omarismailbomarismailb/product-wiki/.agents/skills/compile-change/SKILL.md

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.

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
  1. Distinctive:

    Use the lightest safe path.

    line 9
  2. Very specific:

    If the template is missing, do not invent a plan shape from memory.

    line 14
  3. Distinctive:

    Stop only if the canonical contract cannot be restored.

    line 17
  4. Very specific:

    Read references/blast-radius-rubric.md before choosing the path.

    line 21
  5. Distinctive:

    Use a light path when the change is tiny, mechanical, and has no product or architecture impact.

    line 23
  6. Distinctive:

    Use the full path when the change affects behaviour, user journeys, data, security, architecture, dependencies, or multiple modules.

    line 25
  7. Very specific:

    update checks/manifest.json so every acceptance criterion in the approved change has a command that will run against code

    line 46
  8. Very specific:

    use templates/compiler-plan-template.md when the change is medium or high risk

    line 54
  9. Distinctive:

    add the smallest failing check for the next acceptance criterion

    line 57
  10. Distinctive:

    run it and confirm it fails for the expected reason

    line 58
  11. Distinctive:

    run it again and confirm it passes

    line 60
  12. Very specific:

    Add or update PW: anchors at important routes, services, workflows, domain modules, and tests.

    line 62
  13. Very specific:

    Use anchors as signposts, not comments on every line.

    line 63
  14. Very specific:

    Every active capability and rule unit must carry at least one PW: anchor in code, or wiki-anchor-lint fails.

    line 64
  15. Very specific:

    Run checks, including node scripts/checks-lint.mjs --run, node scripts/wiki-anchor-lint.mjs --write-report, node scripts/ratchet-lint.mjs, …

    line 65
  16. Very specific:

    update or review the local source map in .product-wiki/source-map.json

    line 70
  17. Very specific:

    keep each unit's ## What it does for you in plain product language.

    line 72

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Apply or confirm the approved wiki change.
  2. Locate the blast radius:
    • wiki/overview.md
    • wiki units
    • existing PW: wiki anchors from code search
    • code paths
    • tests
    • dependencies
    • design system files
  3. Decide reuse or refactor:
    • reuse existing capability where possible
    • raise a refactor proposal before adding fragile branches
  4. 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.json so 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.md for the command and shell-quoting gotchas
  5. Plan the edit:
    • files
    • interfaces
    • data paths
    • risk points
    • PW: anchors to add or update at important implementation boundaries
    • use templates/compiler-plan-template.md when the change is medium or high risk
    • save the compiler plan under docs/compiler-plans/, never in intake/proposals/ (proposal-lint treats every file there as a proposal and will fail it)
  6. 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
  7. Implement the smallest coherent code change.
  8. Add or update PW: anchors at important routes, services, workflows, domain modules, and tests. Use anchors as signposts, not comments on every line. Every active capability and rule unit must carry at least one PW: anchor in code, or wiki-anchor-lint fails.
  9. 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.
  10. Reconcile the wiki:
  • review wiki/overview.md if 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 you in 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.md before introducing UI, or keep the change UI-free
  1. Mark the proposal implemented only after the manifest coverage and code checks pass.
  2. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.