implementation-cycle
Skill0 starsChanged 22 days agoNo licenceView on GitHub
Defines the full workflow for implementing a batch of features from an existing overarching plan file: propose a batch and get it quickly confirmed, implement each feature against its spec with targeted tests and an independent review loop (building independent features in parallel, dependent ones in sequence), then get the result signed off on an as-built floor walk before pushing one PR. Use this whenever the user says \"start implementation cycle,\" \"implement this feature,\" \"implement the next batch,\" \"start the implementation loop,\" or points to a plan file and asks for features from it to be built. Requires a plan file path to begin. Make sure to trigger this any time the user is asking Claude Code to build out features from a broader plan/roadmap document, even if they don't use the exact phrase \"implementation cycle.\"
In this repository6 other files it gives its agents.
- architecture-mapSkill
- coding-agentSkill
- feature-plannerSkill
- floor-walkSkill
- risk-inspectorSkill
- visual-planSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 8 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.