breakdown-feature-implementation

Provide the Feature PRD content as context and invoke this prompt. It outputs a structured Markdown plan covering goals, requirements, system architecture, database schema, API design, and frontend component hierarchy, saved to the docs/ways-of-work/plan directory.

A thorough plan includes a system architecture diagram, database schema with ERD, API endpoint specifications with request/response types, frontend component hierarchy, security considerations, and deployment strategy. This Skill generates all of these sections using Mermaid diagrams.

Yes, the prompt is designed around a monorepo structure with apps/, services/, and packages/ directories. It references technologies common in such setups including tRPC, shadcn/ui, Zustand, and React Query.

No, the prompt explicitly instructs not to write code in the output except pseudocode for technical situations. The focus is on architecture diagrams, type definitions, and design specifications rather than implementation code.

The generated plan quality depends on the completeness of the input PRD. It produces a planning document only and does not validate feasibility against the actual codebase, so engineers must still review and adjust the plan before implementation.