Agent skills for planning, building, reviewing, auditing, maintaining, and shipping software — one collection for Claude Code, Codex, OpenCode, and pi.
Produces a deep 11-section behavioral specification for a single module (typically 1–6 files, up to 1500 lines). Used by the code-to-spec pipeline on critical modules flagged by the scout, and as the primary agent for Small-tier bundles. Output is detailed enough that another engineer can reimplement the same…
Independent auditor for behavioral specs. Reads source files directly and evaluates how well a spec captures them — finds misses, errors, overreach, placeholders. Runs per-module and globally. Produces severity-grouped findings for the audit.md file.
Maps cross-module contracts — events, public exports, imports, integration points — across all modules in a bundle. Reconciles fire/listen sites, flags asymmetries, and produces the contract document used by the synthesizer. Use this agent after module analyzers complete, once per code-to-spec run.
Produces a medium-depth behavioral summary of a single module — purpose, public surface, state bindings, events, lifecycle, and key decisions. Use this agent once per module in the code-to-spec pipeline for Medium and Large tier bundles.
Surveys a source-code bundle (one directory up to an entire repo) and produces an architecture overview, module inventory, and a shortlist of critical modules for deep-dive analysis. Use this agent as the first pass of the code-to-spec pipeline on Medium or Large bundles.
Merges scout, per-module, contract-resolver, and deep-analyzer outputs into the final spec directory. Writes README.md, architecture.md, modules.md, contracts.md, and modules/ .md files. No source analysis — aggregation only. Use this agent at the end of the code-to-spec pipeline for Medium and Large tier bundles.