القائمة
Use when bootstrapping a new project repository for Kilroy Attractor from a clean directory using existing spec, DoD, graph, and run config artifacts.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | starting-a-project |
| description | Use when bootstrapping a new project repository for Kilroy Attractor from a clean directory using existing spec, DoD, graph, and run config artifacts. |
Use this skill to prepare a clean repo for kilroy attractor validate/run. This skill does not create requirements artifacts; it only wires and verifies them.
*.md), DoD (*.md), graph (*.dot), run config (*.yaml or *.json)skills -> <kilroy-repo>/skills.claude/skills/<name> -> ../../skills/<name>.agents/skills/<name> -> ../../.claude/skills/<name>demo/): spec, DoD, graph, run config, and any graph-referenced companion files.repo.path to the absolute target repo path.modeldb path or scripts/start-cxdb.sh) still resolve on this machine.kilroy attractor validate --graph <graph.dot>skills, .claude/skills, .agents/skills).repo.path in run config points at the new repo.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 logs_root artifacts and checkpoints.
Use when authoring or repairing Kilroy Attractor DOT graphs from requirements, with template-first topology, routing guardrails, and validator-clean output.
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, and querying run context turns. This skill is useful when investigating run status, debugging retries/failures, explaining model usage, or inspecting CXDB-backed event history.
Use when converting a spec, requirements document, or goal statement into a Definition of Done with acceptance criteria and integration test scenarios
Use when authoring or repairing Kilroy run config YAML/JSON files, including DOT-to-provider backend alignment and runtime policy defaults.
Use when preparing a Kilroy release — writing release notes, tagging, and publishing via goreleaser on GitHub.