dev-workflow
Skill379 starsChanged 28 days agoMITView on GitHub
Use for ANY development request on Flocon (new feature, bug fix, refactor, docs or test change), even when the user names no skill. Routes the work to the right model and subagents.
32 other projects use a version of this.
Adopted by
Most recently taken up by
- AsiaOstrich/EngramGraphtheir own version, first seen Nov 8, 2026
- pandazki/pneuma-skillstheir own version, first seen Nov 6, 2026
- bmsuisse/skillstheir own version, first seen Nov 6, 2026
- Youngju-Heo/claude-skilltheir own version, first seen Nov 1, 2026
- dzianisv/skillstheir own version, first seen Nov 1, 2026
- AsiaOstrich/universal-dev-standardstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use retrospective, brainstorm and 6 more.
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.
MicrosoftSkillretrospective
Review how work went and improve the next round. USE WHEN asked for a retro, delays, or process lessons. DO NOT USE for code review or transcript replay.
Also in 3 projects that use this
nicolasestremSkillbrainstorm
Structured idea generation and solution exploration with systematic analysis.
Also in 4 projects that use this
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 4 projects that use this
HashiCorpSkillchangelog
Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.
Also in 3 projects that use this
VercelSkilldeploy
Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".
Also in 3 projects that use this
GoogleSkillimprove-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Also in 3 projects that use this
Other versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 32
- ag2ai/faststream★ 5.4ksame name
- xstongxue/best-skills★ 2.9ksame name
- AltimateAI/vscode-dbt-power-user★ 586same name
- SmartThingsCommunity/SmartThingsEdgeDrivers★ 349same name
- pandazki/pneuma-skills★ 161same name
- AsiaOstrich/universal-dev-standards★ 84same name
- clarity-digital-development/tworkflow★ 47same name
- addxai/enterprise-harness-engineering★ 44same name
- muyen/vibe-to-prod★ 34same name
- AsiaOstrich/EngramGraph★ 4same name
22 more not listed
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 repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- create-pull-requestSkill
- flocon-mock-modeSkill
- git-setupSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Run the git-setup skill (it runs in the Haiku git-ops agent) to name the branch, passing the feature name.
- Very specific: line 28
Commit with git-setup, and open a PR only when asked, with create-pull-request, passing the checks run and their results.
“Common” is measured: kept by at least 6 in 10 of the 23 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
Dev workflow
Classify the request, then follow the matching path. Do not ask the user which one.
1. Setup
Run the git-setup skill (it runs in the Haiku git-ops agent) to name the branch, passing the feature name.
2. Route by nature
| Request | Path |
| Lookup, "where is X", reading code | Explore (haiku), nothing else |
| CI failed on a PR | ci-investigator (haiku) for the error, then fix the cause (Sonnet) |
| Docs-only change | docs-sync (haiku) or code directly |
| Needs thinking: design, unclear bug, trade-off | Plan mode (Opus), planner for the approach |
| Adds a plugin, changes the protocol or the layering between modules | planner, then architect on the plan before coding |
| Clear change, plan already decided (even across several files) | Code directly (Sonnet), or implementer |
3. Verify and deliver
test-runner(haiku) on the touched module (.claude/rules/build-verification.md).docs-sync(haiku) when the change touches the protocol, an MCP tool, the public SDK API or adds a feature (.claude/rules/docs-protocol-sync.md).reviewer(sonnet) once on the finished diff. Fix what it reports, or say why it isn't a problem.- Commit with
git-setup, and open a PR only when asked, withcreate-pull-request, passing the checks run and their results. Both run in the Haikugit-opsagent. Then bind the PR with the ccd_pr tools.
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.