breakdown-feature-implementation

Generate Markdown implementation plans with architecture diagrams and API specs.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill breakdown-feature-implementation-brunoamsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breakdown-feature-implementation
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/breakdown-feature-implementation
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill breakdown-feature-implementation-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many feature requests lack the technical detail, architecture, and implementation steps engineers need to deliver robust, production-quality functionality. This Skill translates a Feature PRD into a comprehensive, actionable implementation plan that reduces ambiguous decisions, accelerates onboarding, and aligns cross-functional teams on architecture, data models, APIs, and deployment. The result is a single Markdown artifact ready to be checked into the repository under the prescribed Epoch monorepo path.

Core Features & Use Cases

  • End-to-end Implementation Plans: Generates goal statements, detailed requirements, component-level tasks, and a prioritized implementation checklist tailored to frontend, backend, and shared packages.
  • Technical Artifacts: Produces Mermaid system architecture diagrams, ERD schemas, API endpoint specs with TypeScript types, database migration strategies, and deployment recommendations.
  • Use Case: Turn a Product PRD for "user profiles with avatars and privacy settings" into a repo-ready implementation-plan that outlines tRPC endpoints, service classes, DB schema, frontend components, and CI containerization steps.

Quick Start

Create a complete implementation plan for the "feature-name" in the "epic-name" epic using the provided Feature PRD and Epoch monorepo context, and save it to the prescribed implementation-plan.md path.

Frequently Asked Questions about breakdown-feature-implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a technical implementation plan from a Feature PRD for a monorepo?

To generate an implementation plan from a Feature PRD, you need a tool that translates product requirements into actionable technical steps. This Skill processes your PRD and Epoch monorepo context to produce a repo-ready Markdown plan with architecture diagrams, database schemas, and API specs.

What is the best way to create Mermaid architecture diagrams and ERD schemas for new software features?

Creating Mermaid architecture diagrams and ERD schemas requires mapping out system components and data models. This Skill automatically generates these technical artifacts from your feature requirements, embedding them directly into a comprehensive Markdown implementation plan.

How to define TypeScript API specifications and database migration strategies for a SaaS feature?

Defining TypeScript API specifications and database migration strategies involves detailing endpoint contracts and schema changes. This Skill produces these technical specifications within the implementation plan, ensuring frontend and backend coordination across your monorepo's apps and services.

Does this implementation plan generator work with specific monorepo structures like the Epoch architecture?

Yes, this implementation plan generator is specifically designed for SaaS monorepos following the Epoch structure. It maps out frontend, backend, and shared packages coordination, and prescribes explicit repository file paths for saving the generated Markdown plan.

Can I include deployment and scaling strategies in my feature implementation plans?

Yes, you can include deployment and scaling strategies in your feature implementation plans. This Skill generates comprehensive plans that encompass CI containerization steps, deployment recommendations, and a prioritized implementation checklist tailored to your software architecture.

What should a production-ready feature implementation plan include to align cross-functional engineering teams?

A production-ready implementation plan should include goal statements, detailed requirements, component-level tasks, ERD schemas, API TypeScript types, and deployment strategies. This Skill generates these artifacts to reduce ambiguous decisions and align cross-functional teams on architecture.