The implement recipe closes the confirmed findings of a final audit report in the audited repository. It works one theme at a time, on one branch per theme. It respects each finding the owner skipped, and it records existing debt instead of mass-fixing it. It never merges. It pushes and opens a pull request only when the owner opted in (ADR 0003). A state file in the target lets a run stop after any theme and resume later. The report comes from the audit recipe.
- Have a final, owner-confirmed audit report for the repository.
- Open Claude Code at the root of this repository.
- Say: "Start implementing the fixes on
<repo-path>based on<audit-json-path>". - Answer the triage questions, one theme at a time. Say the same sentence again to resume; the state file tells the agent where it stopped.
The skill is SKILL.md (agentic-readiness-implement). Another agent with shell access can run it from
prompts/kickoff.md. Full walkthrough:
Implement an audit report.
To install the skill in another project, build the bundles with python3 dev/build_skills.py and copy
dev/dist/skills/agentic-readiness-implement/ beside agentic-readiness-audit/, from the same build. The implement
skill runs the audit skill's engine.
| Path | Contents |
|---|---|
SKILL.md |
The recipe: hard rules, Stages 0 to 5, themes |
prompts/ |
The kickoff prompt, also used to resume |
playbooks/ |
Thirteen playbooks, one per class of finding, and their anatomy |
state.md |
The per-repository state contract: files, statuses, skip, preferences |
tools/ |
The implement tools and their tests |
docs/architecture/adrs/ |
This recipe's decisions |
Each tool is standard-library Python: python3 implement/tools/<tool>.py <arguments>. The tools import the shared
helpers from audit/tools/.
| Tool | Does |
|---|---|
progress.py |
Creates, shows and renders the state; the only tool that writes inside the target (ADR 0002) |
check_drift.py |
Tells which findings the repository has moved under since the audit |
compare_reports.py |
Compares two audit reports of the same repository |
The full synopsis of each tool is in the Tools CLI reference.
Start at the root router, docs/README.md. What the recipe may and never does to a repository is
in Trust and safety. A real run, before and after this
recipe, is in the worked example.