breakdown-feature-implementation

Solid

Prompt for creating detailed feature implementation plans, following Epoch monorepo structure.

AI & Automation 34,158 stars 4179 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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, workf...

Details

Author
github
Repository
github/awesome-copilot
Created
11 months ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category