startcycle-graph

🚀 BDB Autonomous Development Cycle (/startcycle-graph)

Step 0 — bootstrap the contract into this project, before calling Workflow. Every agent the dispatcher spawns is told to read/write production_artifacts/state.json "per .agents/state.schema.json" — a path resolved against the CURRENT PROJECT, not globally. If this project has never run /startcycle-graph before, that file (and .agents/graph.md) won't be here yet, and every agent will freelance the state shape instead of conforming to the schema (observed for real: a run's state.json was missing run_id/max_iterations/gate/findings/approvals and had several fields the schema doesn't define at all). Fix it first:

mkdir -p .agents
[ -f .agents/graph.md ] || cp "$HOME/.agents/graph.md" .agents/graph.md
[ -f .agents/state.schema.json ] || cp "$HOME/.agents/state.schema.json" .agents/state.schema.json

If $HOME/.agents/graph.md or $HOME/.agents/state.schema.json doesn't exist either, stop and tell the user: this machine has no canonical copy of the graph contract to bootstrap from, and /startcycle-graph will produce a non-conforming state.json until one is installed. Don't silently proceed. (.claude/agents/*.md, the seven agent persona files, do NOT need this treatment — Claude Code resolves subagents from the user-level ~/.claude/agents/ fine without a project-local copy.)

Action — do this, and nothing else: call the Workflow tool with scriptPath pointing at this repo's dispatcher script — resolve $HOME yourself (e.g. echo $HOME or your own environment info) rather than hardcoding a username, giving $HOME/.claude/workflows/startcycle-dispatch.mjs — and args set to the goal text that follows ARGUMENTS: below this file's content. Pass the goal through verbatim. If there is no ARGUMENTS: text, pass no args (or args: undefined) — the workflow itself asks for a goal in that case rather than guessing one.

Use scriptPath, not name: "startcycle-dispatch" — by-name lookup for a custom (non-built-in) workflow script has been observed to fail with Workflow "startcycle-dispatch" not found. Available: deep-research, even when the script exists at the expected path and is correctly named inside its own meta.name. scriptPath pointing directly at the file works reliably; name apparently requires a separate registration step (the /workflows monitor's s save action looked like a candidate, but that's an interactive step a slash command can't trigger on its own, so don't rely on it).

Then wait for the Workflow tool call to finish and report its result (including phase, any reason, and — at ready_to_ship — the instruction to reply GO) back to the user. Do not summarize or reinterpret it; relay it.

Do NOT decompose the task, write anything under production_artifacts/, or implement any part of the goal yourself in response to this skill. This file exists only to route the /startcycle-graph slash command to the real dispatcher — a Dynamic Workflow script (.claude/workflows/startcycle-dispatch.mjs) that holds the actual node/edge graph, spawns the seven agents, and drives the repair loop. If you catch yourself about to write a plan file or code directly because of this skill, stop — that means the Workflow tool call was skipped, which is exactly the failure this file was rewritten to close (see SESSION-HANDOVER-v3.13.md in the source repo for the incident: an earlier version of this file embedded the full pipeline description in prose, and the model followed it "in spirit" inline instead of invoking the script — silently skipping the whole graph, with no state.json, no subagents, no Reviewer, and no quality gate ever running).