Create detailed implementation plans for software features following the Epoch monorepo structure

1. Prepare the content of the Feature PRD file and specify the epic name and the feature name. 2. Ask the agent to apply the skill, attaching the document content. Example user request: "This is the feature requirements document for importing recipes from a URL within the Recipe Library epic. Create a detailed implementation plan following the monorepo structure." 3. The agent prepares a plan containing: the goal, the requirements, the layered architecture diagram, the entity-relationship diagram, the API design, the frontend component structure, and security and performance considerations. 4. The plan is saved at the path /docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md. 5. Review the plan and the Mermaid diagrams, then adjust the proposed technologies if your project does not use the assumed stack.

The skill needs a Feature PRD provided by the user, and write permission to the docs folder in the repository. It does not require external accounts or tools, as it is text-based guidance only. Limitations: - It assumes a monorepo structure (apps, services, and packages). - It assumes a specific technology stack: tRPC, Stack Auth, shadcn/ui, Zustand, React Query, and Docker. - The component structure example is specific to a recipe library, so it must be adapted to your feature. - It does not produce executable code. - It requires human review for plan accuracy. - Rendering Mermaid diagrams requires a tool that supports this format.