setup-workflow
Skill1 starsChanged 9 months agoMITView on GitHub
Set up the autonomous post-task workflow for a project. Injects the standard development pipeline into CLAUDE.md and installs all required skills and agents (docs-consolidator, ci-cd-pipeline, smoke-test, bug-bash-update, code-reviewer, debugger). Use at the start of a new project. Triggers on "setup workflow", "init workflow", "add workflow", or "set up project workflow".
5 other projects use a version of this.
Adopted by
Most recently taken up by
- karrot0195/harness-agent-skillstheir own version, first seen Nov 8, 2026
- prefapp/skillstheir own version, first seen Oct 4, 2026
- linhnt89/skillstheir own version, first seen Jul 22, 2026
- BanKnight/claude-templatetheir own version, first seen May 23, 2026
- dcolclazier/skillstheir own version, first seen May 18, 2026
Used with
Projects with it also use tdd.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- dcolclazier/skills★ 1same name
- karrot0195/harness-agent-skills★ 1same name
- prefapp/skills★ 1same name
- BanKnight/claude-template★ 0same name
- linhnt89/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- bug-bash-updateSkill
- ci-cd-pipelineSkill
- claudemd-auditorSkill
- docs-consolidatorSkill
- ralphSkill
- refactor-auditSkill
- reflectSkill
- skill-reviewerSkill
- smoke-testSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 10 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Skills: Check that SKILL.md exists at the live path.
- Very specific: line 30
Agents: Check that the agent .md file exists at the live path.
- Distinctive: line 34
If all dependencies are present, proceed to Phase 2.
- Distinctive: line 36
If any are missing, report which ones and stop:
- Distinctive: line 45
Search for the project's CLAUDE.md file:
- Distinctive: line 46
Check for CLAUDE.md in the project root
- Very specific: line 48
Check if root CLAUDE.md is a symlink to docs/CLAUDE.md
- Distinctive: line 50
If found, note the path. If not found, note that a new one will be created.
- Very specific: line 56
Check if a ## Workflow section already exists
- Very specific: line 61
Read references/workflow-template.md — this is the canonical workflow content.
- Very specific: line 67
If a
## Quality Standardssection already exists: Do not inject a duplicate. - Distinctive: line 69
If no CLAUDE.md exists: Create a new CLAUDE.md in the project root with this structure:
- Distinctive: line 95
Read the updated CLAUDE.md
- Distinctive: line 102
Never modify any section of CLAUDE.md outside the Workflow section (unless creating a new file)
- Distinctive: line 104
If auto-detecting commands for a new CLAUDE.md, prefer reading the project's config files over guessing
- Distinctive: line 105
If a dependency is missing, tell the user to install it rather than attempting to create it
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 this additional file:
~/.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 a ## Quality Standards section already exists: Do not inject a duplicate. Only inject the Quality Standards section (from the template) when creating a new CLAUDE.md or when no such section exists.
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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

