Skills github awesome-copilot Epic breakdown workflow
breakdown-feature-implementation
- Use it when:
- A feature's PRD is written and you want the technical design worked out before anyone codes.
- It does:
- Sets out the goal and requirements, a layered system diagram, database schema with indexes, API endpoints with TypeScript types, a component tree and state flow.
- You get:
- implementation-plan.md in /docs/ways-of-work/plan/{epic-name}/{feature-name}/, with no code beyond pseudocode.
- Assumes:
- A monorepo of apps, services and packages, with tRPC, Stack Auth, shadcn/ui, Zustand or React Query, and Docker.
- Unlike create-implementation-plan:
- That one, from the same repo, writes atomic task tables for an agent to execute; this one designs the architecture, data model, API and UI.
Skill 4 of 6 in the Epic breakdown workflow bundle, after breakdown-feature-prd and before breakdown-plan.
Plans for a set stack: tRPC, Stack Auth, shadcn/ui, Zustand or React Query and Docker, in a monorepo of apps, services and packages.
TL;DR
You give it the content of a feature PRD, and it writes the plan engineers build from, acting as a veteran engineer at a large SaaS company. The plan states the feature's goal in three to five sentences and its detailed requirements, then the technical considerations. A Mermaid system diagram shows the frontend, API, business logic, data and infrastructure layers as subgraphs with labelled data flows, followed by the technology choice for each layer, integration points, Docker deployment and scaling. The database section has a Mermaid entity-relationship diagram with field types and constraints, indexes, foreign keys and a migration strategy. The API section specifies endpoints, request and response formats as TypeScript types, authentication with Stack Auth, error handling, rate limiting and caching. The frontend section lays out a component hierarchy built on shadcn/ui, with a recipe library page as its example, plus a state flow diagram and Zustand or React Query for state, and a last section covers security and performance. The folder layout follows what it calls Epoch's monorepo structure, so expect to swap parts of the stack for yours.
Summarizes the skill at 797337f.
npx skills add https://github.com/github/awesome-copilot --skill breakdown-feature-implementation skills.sh pageSource on GitHubAll skills from github/awesome-copilot
- Total Downloads
- 9,200 on skills.sh, Nov 9, 2026
- Repo stars
- 40,943 github/awesome-copilot
- First seen
- Feb 25, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 17 |
| Sep 28 | 19 |
| Oct 5 | 20 |
| Oct 12 | 10 |
| Oct 19 | 2 |
| Oct 26 | 5 |
| Nov 2 | 5 |
| Nov 9 | 1 |
| Category |
Make the agent question you and write the plan down before it writes code. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A one-shot action you invoke by name, such as turning the conversation into a PRD. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates. |
| Topics | |
| Stack |
SKILL.md
From github/awesome-copilot at 797337f. Checked daily, last changed Nov 6, 2026.
Frontmatter
name: breakdown-feature-implementation
description: 'Prompt for creating detailed feature implementation plans, following Epoch monorepo structure.'Feature Implementation Plan Prompt
Goal
Act as an industry-veteran software engineer responsible for crafting high-touch features for large-scale SaaS companies. Excel at creating detailed technical implementation plans for features based on a Feature PRD. Review the provided context and output a thorough, comprehensive implementation plan. Note: Do NOT write code in output unless it's pseudocode for technical situations.
Output Format
The output should be a complete implementation plan in Markdown format, saved to /docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md.
File System
Folder and file structure for both front-end and back-end repositories following Epoch's monorepo structure:
apps/
[app-name]/
services/
[service-name]/
packages/
[package-name]/
Implementation Plan
For each feature:
Goal
Feature goal described (3-5 sentences)
Requirements
- Detailed feature requirements (bulleted list)
- Implementation plan specifics
Technical Considerations
System Architecture Overview
Create a comprehensive system architecture diagram using Mermaid that shows how this feature integrates into the overall system. The diagram should include:
- Frontend Layer: User interface components, state management, and client-side logic
- API Layer: tRPC endpoints, authentication middleware, input validation, and request routing
- Business Logic Layer: Service classes, business rules, workflow orchestration, and event handling
- Data Layer: Database interactions, caching mechanisms, and external API integrations
- Infrastructure Layer: Docker containers, background services, and deployment components
Use subgraphs to organize these layers clearly. Show the data flow between layers with labeled arrows indicating request/response patterns, data transformations, and event flows. Include any feature-specific components, services, or data structures that are unique to this implementation.
- Technology Stack Selection: Document choice rationale for each layer
- Integration Points: Define clear boundaries and communication protocols
- Deployment Architecture: Docker containerization strategy
- Scalability Considerations: Horizontal and vertical scaling approaches
Database Schema Design
Create an entity-relationship diagram using Mermaid showing the feature's data model:
- Table Specifications: Detailed field definitions with types and constraints
- Indexing Strategy: Performance-critical indexes and their rationale
- Foreign Key Relationships: Data integrity and referential constraints
- Database Migration Strategy: Version control and deployment approach
API Design
- Endpoints with full specifications
- Request/response formats with TypeScript types
- Authentication and authorization with Stack Auth
- Error handling strategies and status codes
- Rate limiting and caching strategies
Frontend Architecture
Component Hierarchy Documentation
The component structure will leverage the shadcn/ui library for a consistent and accessible foundation.
Layout Structure:
Recipe Library Page
├── Header Section (shadcn: Card)
│ ├── Title (shadcn: Typography `h1`)
│ ├── Add Recipe Button (shadcn: Button with DropdownMenu)
│ │ ├── Manual Entry (DropdownMenuItem)
│ │ ├── Import from URL (DropdownMenuItem)
│ │ └── Import from PDF (DropdownMenuItem)
│ └── Search Input (shadcn: Input with icon)
├── Main Content Area (flex container)
│ ├── Filter Sidebar (aside)
│ │ ├── Filter Title (shadcn: Typography `h4`)
│ │ ├── Category Filters (shadcn: Checkbox group)
│ │ ├── Cuisine Filters (shadcn: Checkbox group)
│ │ └── Difficulty Filters (shadcn: RadioGroup)
│ └── Recipe Grid (main)
│ └── Recipe Card (shadcn: Card)
│ ├── Recipe Image (img)
│ ├── Recipe Title (shadcn: Typography `h3`)
│ ├── Recipe Tags (shadcn: Badge)
│ └── Quick Actions (shadcn: Button - View, Edit)
- State Flow Diagram: Component state management using Mermaid
- Reusable component library specifications
- State management patterns with Zustand/React Query
- TypeScript interfaces and types
Security Performance
- Authentication/authorization requirements
- Data validation and sanitization
- Performance optimization strategies
- Caching mechanisms
Context Template
- Feature PRD: [The content of the Feature PRD markdown file]