setup-new-feature
Skill9 starsChanged 3 months agoMITView on GitHub
Scaffold a new feature across layers
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- gologo13/agent-skillsedited, first seen Feb 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- gologo13/agent-skills★ 078% same
Wrote their own version · 0
None found.
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 repository43 other files it gives its agents.
- accessibility-auditSkill
- add-documentationSkill
- add-error-handlingSkill
- address-github-pr-commentsSkill
- agent-risk-reviewSkill
- agent-work-receiptSkill
- automation-roi-auditSkill
- blind-spot-passSkill
- code-reviewSkill
- commit-changes-mainSkill
- commit-same-branchSkill
- commitSkill
- create-pr-mainSkill
- debug-issueSkill
- decision-auditSkill
- define-agent-goalSkill
- design-agent-loopSkill
- fix-compile-errorsSkill
- fix-git-issuesSkill
- gauntlet-loopSkill
- generate-api-docsSkill
- generate-pr-descriptionSkill
- git-sync-workspaceSkill
- instruction-ablationSkill
- light-review-existing-diffsSkill
- lint-fixSkill
- lint-suiteSkill
- merge-open-prsSkill
- optimize-performanceSkill
- pathfinderSkill
- prompt-eval-debugSkill
- refactor-codeSkill
- requirement-to-implementationSkill
- run-all-tests-and-fixSkill
- scoped-auditSkill
- security-auditSkill
- seo-auditSkill
- structure-promptSkill
- tddSkill
- thermo-nuclear-code-quality-reviewSkill
- update-memory-bankSkill
- update-readmeSkill
- write-unit-testsSkill
The file
Files
Overview
Systematically set up a new feature from initial planning through to implementation structure.
Steps
- Define requirements
- Clarify feature scope and goals
- Identify user stories and acceptance criteria
- Plan technical approach
- Create feature branch
- Branch from main/develop
- Set up local development environment
- Configure any new dependencies
- Plan architecture
- Design data models and APIs
- Plan UI components and flow
- Consider testing strategy
Setup New Feature Checklist
- Requirements documented
- User stories written
- Technical approach planned
- Feature branch created
- Development environment ready
Guardrails
- Scaffold only what the feature needs now; do not over-engineer or add speculative layers.
- Match the existing project structure, naming, and conventions instead of inventing a new layout.
- Plan requirements and architecture before writing code; do not commit, push, or merge without an explicit request.
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.