build-dod
01Skill Claude CodeCodex
Use when converting a spec, requirements document, or goal statement into a Definition of Done with acceptance criteria and integration test scenarios.
Skill Claude CodeCodex
Use when converting a spec, requirements document, or goal statement into a Definition of Done with acceptance criteria and integration test scenarios.
Skill Claude Code
Use when authoring or repairing Kilroy Attractor DOT graphs from requirements, with template-first topology, routing guardrails, and validator-clean output.
Skill Claude CodeCodex
Use when authoring or repairing Kilroy run config YAML/JSON files, including DOT-to-provider backend alignment and runtime policy defaults.
Skill Codex needs its repo
To diagnose active, stuck, or failed Kilroy Attractor runs, inspect run artifacts (manifest.json, live.json, checkpoint.json, final.json, progress.ndjson), resolve run IDs/log roots, identify model/provider routing, and isolate failure causes. Includes CXDB operations for launching/probing CXDB, opening the CXDB UI…
Skill Claude CodeCodex needs its repo
Use when preparing a Kilroy release — writing release notes, tagging, and publishing via goreleaser on GitHub.
Skill Claude CodeCodex
Use when bootstrapping a new project repository for Kilroy Attractor from a clean directory using existing spec, DoD, graph, and run config artifacts.
Skill Claude CodeCodex
Operate Kilroy Attractor pipelines end-to-end: ingest English requirements into DOT graphs, validate graph semantics, run and resume pipelines with run config files, configure provider backends (cli/api), and debug runs from logsroot artifacts and checkpoints.
Skill Claude CodeCodex
Create polished interactive flowchart visualizations for complex codebases, workflows, data flows, prompt pipelines, and system/process maps using Cytoscape.js, Chroma.js, and Prism.js. Invoke only when the user explicitly asks for "flowchart" by name or asks to build an interactive flowchart visualization.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: