devflow
Skill22 starsChanged 7 months agoMITView on GitHub
Use when working in a DevFlow project with .devflow/ directory and gate-based step-by-step workflows
- Installs packages
6 other projects use a version of this.
Adopted by
Most recently taken up by
- docutray/devflow-skilltheir own version, first seen Nov 1, 2026
- wotjr1649/devflowtheir own version, first seen Oct 15, 2026
- ambient-code/platformtheir own version, first seen Oct 8, 2026
- slpy22/claude-skillstheir own version, first seen Oct 8, 2026
- AppleCG/devflowtheir own version, first seen Jul 8, 2026
- Santazuki/devflowtheir own version, first seen Jun 2, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- ambient-code/platform★ 131same name
- AppleCG/devflow★ 8same name
- Santazuki/devflow★ 4same name
- docutray/devflow-skill★ 2same name
- wotjr1649/devflow★ 1same name
- slpy22/claude-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 repository17 other files it gives its agents.
- code-analysisSkill
- code-generatorSkill
- contributingSkill
- daily-logSkill
- git-workflowSkill
- hexo-blog-updateSkill
- kimicode-vision-bridgeSkill
- knowledge-base-cacheSkill
- layered-first-principles-teachingSkill
- msvc-buildSkill
- mvp-designSkill
- paper-first-principlesSkill
- requirement-clarificationSkill
- research-to-practiceSkill
- taskmaster-skillSkill
- ue5-umgSkill
- unity-mcpSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
If devflow is not found, install first:
- Distinctive: line 80
When gates fail, the workflow may route based on failure count:
“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
DevFlow
CLI-driven progressive disclosure workflow. Advance one verified step at a time.
Overview
DevFlow enforces a disciplined development process where each step must be completed and verified before advancing. It uses TOML workflow definitions, gate-based verification, and a devflow done checkpoint system.
When to Use
- Project has
.devflow/workflows/*.tomlfiles - You see
devflowcommands in project docs - Task requires writing requirements, design docs, or code in stages
- You need gate-based verification (tests must pass before advancing)
When NOT to use: Project has no .devflow/ directory — this is a standard project, use normal development.
Quick Start
devflow --help # Verify CLI is installedIf devflow is not found, install first:
pip install agent-devflow # From PyPIThen start the workflow:
devflow list-workflows # See available workflows
devflow select-workflow MODE-A # Pick one
devflow current # Read current stepCore Loop (ALWAYS follow this)
1. devflow current -> Read what to do
2. Execute the step -> Write code, create docs, run tests
3. devflow done -> Check gates -> advance or retry
4. Repeat until "Workflow complete!"Core rule: Only advance through devflow done. Never skip steps. Never create files for future steps.
Commands
| Command | Purpose |
devflow current | Show current step instruction |
devflow done | Check gates and advance |
devflow back | Go back one step |
devflow approve ITEM | Mark item as user-approved |
devflow set KEY VALUE | Set state variable |
devflow list-workflows | List available workflows |
devflow select-workflow ID | Select and start a workflow |
devflow run | Start autonomous Ralph Loop |
Gate Types
Gates block advancement until satisfied:
file_exists:path— File must existfile_contains:path:content— File must contain textcommand_success:{test_command}— Command exits 0user_approved:ITEM— Requiresdevflow approve ITEMstate_set:var— State variable must be set
Fail Routes
When gates fail, the workflow may route based on failure count:
fails 1-2 -> retry or fallback step
fails 3+ -> escalate to humanFail count persists across visits (resets only when gates pass).
Built-in Workflows
| Workflow | Steps |
| MODE-A (Feature) | req-create -> req-approve -> brainstorm -> write-plan -> implement-sdd -> code-review -> test-run -> verify -> finish |
| MODE-B (Debug) | debug-root-cause -> debug-pattern -> debug-hypothesis -> debug-fix -> debug-question -> debug-verify -> debug-finish -> (auto -> MODE-A:write-plan) |
Cross-workflow references use WORKFLOW-ID:STEP-ID format.
5 Iron Laws
| # | Law | Severity |
| 1 | Read using-superpowers skill first | Rigid |
| 2 | TDD: Test before code | Rigid |
| 3 | Verify before claim | Rigid |
| 4 | Root cause before fix | Strong |
| 5 | Debug -> Repeat full cycle | Strong |
Common Mistakes
| Mistake | Fix |
Writing code before devflow current | Stop. Run devflow current first |
| Creating files for future steps | Only create what the current step asks for |
Skipping devflow done | All advancement must go through devflow done |
| Ignoring gate failures | Fix the issue, then devflow done again |
Project Context
Language: {{ project.language }} Stack: {{ project.stack }} Version: {{ project.version }}
Constraints
{% if constraints.zero_warnings %}- ZERO warnings — All builds must have zero warnings{% endif %} {% if constraints.zero_mocks %}- ZERO mocks — Use real instances only in tests{% endif %} {% if constraints.nullable %}- Nullable enabled — Use nullable reference types{% endif %}
Project Structure
{{ project.name }}/
├── .devflow/ # DevFlow configuration
│ ├── workflows/ # Workflow definitions (TOML)
│ ├── prompts/ # Reusable prompt files
│ ├── config.toml # Project config
│ └── state.toml # Current state (gitignored)
├── {{ paths.src }}/ # Source code
├── {{ paths.tests }}/ # Tests
├── {{ paths.docs }}/ # Documentation
│ ├── requirements/ # REQ files
│ ├── features/ # FEAT files
│ ├── superpowers/specs/ # Design docs
│ ├── superpowers/plans/ # Implementation plans
│ ├── evidence/ # Verification evidence
│ ├── debug/ # Debug analysis
│ └── completion/ # Workflow completion summaries
└── SKILL.md # This fileCommands Reference
# Build
{{ commands.build }}
# Test
{{ commands.test }}
{{ commands.test_unit }}
{{ commands.test_integration }}
# Lint
{{ commands.lint }}Generated by DevFlow v2.0
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.

