breakdown-feature-implementation

Name: breakdown-feature-implementation
Availability: InStock
Author: shysssthanhtri

Generate end-to-end implementation plans for features in an Epoch monorepo.

Updated Mar 19, 2026

Search Tags:#mermaid #frontend-backend #saas #architecture-diagrams #implementation-plan #feature-planning #epoch-monorepo

Ready to run

npx skills add https://github.com/shysssthanhtri/AI-tools --skill breakdown-feature-implementation-shysssthanhtri

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: breakdown-feature-implementation
Source: https://github.com/shysssthanhtri/AI-tools/tree/main/skills/breakdown-feature-implementation
Command: npx skills add https://github.com/shysssthanhtri/AI-tools --skill breakdown-feature-implementation-shysssthanhtri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams quickly produce end-to-end implementation plans for new features, ensuring alignment with architecture, timelines, and PRD requirements.

Core Features & Use Cases

Generate step-by-step implementation plans that map to an Epoch monorepo structure.
Include front-end and back-end components, data flow, and deployment considerations.
Use cases include feature PRD to implementation plan conversion, architecture diagram generation, and risk/edge-case coverage.

Quick Start

Describe and document a full end-to-end implementation plan for a given feature in an Epoch-style monorepo.

Frequently Asked Questions about breakdown-feature-implementation

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

FAQPage Schema

How do I create an end-to-end implementation plan for a feature in a monorepo?▼

To create an end-to-end implementation plan for a feature in a monorepo, define front-end, back-end, data, and deployment considerations. Map architecture, data models, and API design to the PRD requirements for actionable guidance.

How do I convert a feature PRD into a step-by-step implementation plan?▼

Converting a feature PRD into an implementation plan involves detailing architecture, data models, API design, and security validations. This translates PRD requirements into actionable steps covering front-end and back-end components within a monorepo structure.

What should a scalable feature implementation plan include for SaaS architecture?▼

A scalable feature implementation plan for SaaS architecture should include front-end and back-end components, data flow, API design, security validations, and deployment considerations. It ensures alignment with timelines and architecture diagrams.

Does this implementation plan generation support Epoch monorepo structures?▼

Yes, implementation plan generation supports Epoch monorepo structures by mapping step-by-step front-end and back-end tasks directly to that architecture. It produces clear guidance suitable for a PRD-to-implementation workflow.

Can I generate architecture diagrams for my feature planning workflow?▼

Yes, you can generate architecture diagrams during feature planning. The plan details data flow and system architecture using Mermaid, providing visual guidance alongside the step-by-step implementation tasks.

What is the best way to cover edge cases when planning a large-scale feature?▼

The best way to cover edge cases when planning a large-scale feature is to document risk and edge-case coverage alongside data models and security validations. This ensures the end-to-end plan anticipates potential deployment and architectural issues.