breakdown-feature-implementation
Detailed feature implementation plan generator following Epoch monorepo
by githubFree
Description
breakdown-feature-implementation is an agent skill from the github/awesome-copilot collection, a prompt for writing a detailed implementation plan for a feature, based on a feature requirements document. It follows the folder conventions of the Epoch monorepo, which lays out front-end and back-end repositories in a set structure, and it saves the plan as a markdown file under the epic's planning folder. The agent acts as an experienced software engineer. The plan covers the system architecture, the database schema and the API design, and it includes Mermaid diagrams for the system architecture, the entity relationships and the components. The prompt says not to write code in the plan except pseudocode for technical situations, so the plan describes what to build and how the parts fit, without being an implementation. The plan is useful for engineers who need agreement on a design before they start, and for splitting a feature across several people. The plan should be reviewed against the real codebase, because a plan written from a requirements document can miss existing code that already does part of the job. The skill is installed with the skills CLI from the github/awesome-copilot repository. Its skills.sh page showed about 9.2K installs and passing results from three security audits at the time of the scan.…
Highlights
- Feature implementation plans in Markdown
- System architecture, database schema and API design
- Mermaid diagrams for architecture and entities
- Epoch monorepo folder conventions
- No code except pseudocode
- Installs with the skills CLI
Ratings & Reviews
No ratings yet
Be the first to rate breakdown-feature-implementation.
People also visit
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures
python-design-patterns
Fundamental design principles for writing maintainable, testable Python code
python-project-structure
Python project organization, module architecture, and public API design
acquire-codebase-knowledge
The user explicitly asks to map, document, or onboard into an existing codebase
breakdown-feature-implementation FAQ
What does the plan include?
System architecture, database schema, API design, and Mermaid diagrams for architecture, entity relationships and components.
Does it follow a folder structure?
Yes, the Epoch monorepo structure for front-end and back-end repositories.
Does it write code?
No, apart from pseudocode for technical situations, so the plan describes the build rather than implementing it.
Should I check it against the codebase?
Yes. A plan written from a requirements document can miss existing code that already does part of the job.
How do I install it?
Run npx skills add https://github.com/github/awesome-copilot --skill breakdown-feature-implementation.
What security audits does it have?
skills.sh lists three audits: Gen Agent Trust Hub Pass, Socket Pass and Snyk Pass.
What are the best breakdown-feature-implementation alternatives?
Popular alternatives to breakdown-feature-implementation include cqrs-implementation, event-store-design and parallel-feature-development. See all breakdown-feature-implementation alternatives