← ClaudeAtlas

setuplisted

Prepare a project to run this workflow — either wire the commands into the doc layer it already has (adopt), or build that layer from the real codebase (init). Use right after install.sh, or when the other commands report that references/ is missing.
ledtorch/coding-agent-workflow · ★ 0 · Data & Documents · score 70
Install: claude install-skill ledtorch/coding-agent-workflow
# Setup Make a project ready for the other commands. **Writes only inside `references/`**, plus one proposed edit to a `references/SKILL.md` the project already owns. Never touches source, config, or history. **Use when:** `install.sh` has just linked the commands into a project; a command reported that `references/` was missing; the project's reference docs have drifted so far they mislead more than they help. **NOT for:** installing the commands (that is `install.sh`, and it needs no agent), or writing a plan for actual work (`/plan`). ## The mode is already chosen The user picked when they ran the installer. **Detect it — never re-ask.** | | **adopt** — `install.sh` | **init** — `install.sh --init` | |---|---|---| | The project | already has its own `references/SKILL.md` | has no doc layer yet | | Your job | wire the commands into the docs that exist | write the layer from the real codebase | | `SKILL.md` | **theirs.** You propose an edit; they approve it | yours to write | | Failure mode | their router doesn't route to what the commands read | a scaffold of plausible guesses nobody corrected | Both end in the same place: the three contract paths resolve, and the index routes to them. ### The three contract paths Hardcoded in the other commands' blocking Step 0. Whatever the index says about them, they have to exist: | Path | Read by | |---|---| | `references/SKILL.md` | `/build` `/inspect` `/plan` `/team` | | `references/development/conventions.md` | `/build` `/h