feature-delivery
Skill1 starsChanged 3 months agoNo licenceView on GitHub
Enterprise-Implementierungs-Disziplin für JEDE nicht-triviale Code-Änderung auf JEDEM Projekt. Diesen Skill verwenden BEVOR und WÄHREND Code geschrieben wird — wann immer ein Feature, ein Fix, ein Refactor oder eine Verhaltensänderung umgesetzt wird, besonders bei State-/Rollen-/Payment-/ Auth-/Async-/SSR-/Cross-Layer-Änderungen. Der Skill zwingt den Agent ZUERST den vollständigen Blast-Radius zu kartieren (alle Aufrufer, Konsumenten, Reverse-Pfade, duplizierte Configs, generierte Artefakte), den Zustandsraum zu modellieren (State-Table, Invarianten, Falsy-Fälle, Contracts) und erst DANN — vollständig und symmetrisch — zu implementieren. Ziel: 1 Prompt → vollständig & korrekt eingebautes Feature, ohne vergessene Stellen, ohne Folgekommit-Ketten. Orchestriert /feature-testing (Test-Beweis), /verify (Real-Runtime-Beweis) und /security-review (Diff-Security). Führt bei jedem Aufruf einmal täglich einen Threat-Intel-Refresh aus (neueste CVEs/Angriffe → Exposure-Check gegen unseren Code) und härtet auf Enterprise-Security-Niveau inkl. Paywall-/Abuse-Schutz (VPN/IP/Geo, Coupon-Abuse). Ergänzt /performance-boost. Denkt wie IT-Architekt + Security-Engineer. Läuft als autonome LOOP-ENGINE (Loop Engineering): jeder Aufruf gibt dem Lauf EIN Ziel und er promptet sich selbst — findet die Arbeit, erledigt sie, prüft sie mit unabhängigen Subagenten (Writer ≠ Reviewer), merkt den Fortschritt in einem durablen Checkpoint und macht weiter bis die DoD wirklich erfüllt ist. Nutzt die fünf Loop-Bausteine (Automation/Worktrees/Skills/Connectors/Subagents) risiko-proportional statt Hand-Holding.
- Reads credentials
- Commits and pushes
8 other projects use a version of this.
Adopted by
Most recently taken up by
- MarioJames/skill-foundrytheir own version, first seen Nov 8, 2026
- pdugan20/skillstheir own version, first seen Nov 1, 2026
- florian101010/awesome-agentic-AI-coding-templatetheir own version, first seen Nov 1, 2026
- Eliahhango/nullbyte-securitytheir own version, first seen Nov 1, 2026
- microsoft/testfxtheir own version, first seen Oct 13, 2026
- ack-solutions/claude-code-ai-skillstheir own version, first seen Oct 11, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- microsoft/testfx★ 1.1ksame name
- DodoraApp/DodoStream★ 243same name
- LanternOps/breeze★ 169same name
- Eliahhango/nullbyte-security★ 4same name
- florian101010/awesome-agentic-AI-coding-template★ 4same name
- ack-solutions/claude-code-ai-skills★ 1same name
- MarioJames/skill-foundry★ 1same name
- pdugan20/skills★ 1same 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 repository7 other files it gives its agents.
- apple-designSkill
- architectureSkill
- emil-design-engSkill
- feature-testingSkill
- frontend-designSkill
- gameboy-gateSkill
- performance-boostSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
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 measured: kept by at least 6 in 10 of the 7 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.
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.