Setup Workflow
Install the autonomous post-task development pipeline into a project's CLAUDE.md. All dependency skills and agents must be installed before running this skill.
Dependencies
This workflow requires 6 tools:
| Dependency | Type | Live path |
|---|---|---|
| docs-consolidator | Skill | ~/.claude/skills/docs-consolidator/SKILL.md |
| ci-cd-pipeline | Skill | ~/.claude/skills/ci-cd-pipeline/SKILL.md |
| smoke-test | Skill | ~/.claude/skills/smoke-test/SKILL.md |
| bug-bash-update | Skill | ~/.claude/skills/bug-bash-update/SKILL.md |
| code-reviewer | Agent | ~/.claude/agents/code-reviewer.md |
| debugger | Agent | ~/.claude/agents/debugger.md |
Workflow
Phase 1: Check dependencies
For each dependency in the table above, check if the live file exists:
- •Skills: Check that
SKILL.mdexists at the live path. - •Agents: Check that the agent
.mdfile exists at the live path. - •ci-cd-pipeline references: Also check these additional files:
- •
~/.claude/skills/ci-cd-pipeline/references/actions-catalog.md - •
~/.claude/skills/ci-cd-pipeline/references/deploy-prerequisites.md
- •
If all dependencies are present, proceed to Phase 2.
If any are missing, report which ones and stop:
Missing dependencies: - [dependency name]: expected at [path] Install the missing skills/agents before running setup-workflow.
Phase 2: Detect CLAUDE.md
Search for the project's CLAUDE.md file:
- •Check for
CLAUDE.mdin the project root - •Check for
docs/CLAUDE.md - •Check if root
CLAUDE.mdis a symlink todocs/CLAUDE.md
If found, note the path. If not found, note that a new one will be created.
Phase 3: Read current state
If CLAUDE.md exists:
- •Read it fully
- •Check if a
## Workflowsection already exists - •Note the line range of the existing Workflow section (from
## Workflowto the next##heading or end of file)
Phase 4: Inject workflow
Read references/workflow-template.md — this is the canonical workflow content.
If a Workflow section exists: Replace it (from ## Workflow up to but not including the next --- or ## heading) with the content of workflow-template.md.
If CLAUDE.md exists but has no Workflow section: Insert the workflow content after the first heading block (title + any introductory text before the first ---).
If no CLAUDE.md exists: Create a new CLAUDE.md in the project root with this structure:
# CLAUDE.md ## Project — Development Guide This file provides context for Claude Code sessions working on this project. --- [workflow-template.md content here] --- ## Commands [Auto-detect from pyproject.toml / package.json / Makefile / Cargo.toml and list the project's lint, format, typecheck, and test commands] --- ## Mistakes to Avoid *Claude: After any correction, add a rule here. Be specific.*
Phase 5: Verify
- •Read the updated CLAUDE.md
- •Confirm the Workflow section contains the full pipeline
- •Confirm no other sections were accidentally modified
- •Report a summary of all changes made
Guidelines
- •Never modify any section of CLAUDE.md outside the Workflow section (unless creating a new file)
- •The workflow template in
references/workflow-template.mdis the single source of truth - •If auto-detecting commands for a new CLAUDE.md, prefer reading the project's config files over guessing
- •If a dependency is missing, tell the user to install it rather than attempting to create it