feature-integrator
Skill1 starsChanged 35 days agoNo licenceView on GitHub
Add or change a single feature on a project that already has a `.product/` foundation. Make sure to use this whenever the user asks to "add a feature", "also support X", "change how Y works", "can we make it do Z", "can we also add <thing> to my app", "integrate <service>", or requests any capability that isn't simply the next planned roadmap slice — even when it sounds like a small addition, because the conflict/backward-compatibility check below is most valuable exactly when a change looks harmless. Trigger on concrete build-it phrasings just as much as the word "feature": "wire up email notifications", "hook up Stripe", "build in exports", "implement <capability>", "make it also send …" all count — any new behavior added to an existing product is this skill's job, not a one-off you do inline. BEFORE writing any code it checks the request against ARCHITECTURE and ROADMAP for conflicts, breaking changes, and backward-compatibility risk, and reports what it finds; only then does it implement, preserving backward compatibility unless the user explicitly says otherwise, and updates ROADMAP + STATE. Use phase-executor instead to build the next already-planned slice in order, debugger if something is broken rather than missing, and refactor-steward if the goal is cleanup with no behavior change.
- Commits and pushes
In this repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- board-reconcileSkill
- change-scoperSkill
- codebase-cartographerSkill
- commit-conventionsSkill
- debuggerSkill
- dynamo-bootstrapSkill
- dynamo-bootstrapSkill
- dynamo-designSkill
- dynamo-designSkill
- dynamo-probeSkill
- dynamo-probeSkill
- dynamo-rebuildSkill
- dynamo-rebuildSkill
- dynamo-repairSkill
- dynamo-repairSkill
- dynamo-reworkSkill
- dynamo-submissionSkill
- dynamo-submissionSkill
- dynamo-verifySkill
- dynamo-verifySkill
- feature-grafterSkill
- grillingSkill
- intake-triageSkill
- phase-executorSkill
- pr-descriptionSkill
- product-architectSkill
- product-guideSkill
- product-state-initSkill
- quality-gateSkill
- refactor-stewardSkill
- regression-guardSkill
- root-cause-investigatorSkill
- safety-net-builderSkill
- surgical-fixerSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
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.