Guide · Agent skill
How to use the Feature Implementation Planner agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Feature Implementation Planner is an agent skill, published as breakdown-feature-implementation, that turns a feature product requirements document (PRD) into a structured technical implementation plan. It is aimed at engineers and tech leads on teams using a monorepo layout similar to Epoch's. After this guide you will know what the skill does, how to install it, how to ask for a plan, and what to check before you trust the output.
Feature Implementation Plannergithub/awesome-copilot · MIT Download the skill Quick start
- 1Download the ZIP. Get the skill ZIP from this page. It contains SKILL.md.
- 2Unzip into a skills folder. Place the breakdown-feature-implementation folder in ~/.claude/skills/ for personal use or in a project's .claude/skills/ folder.
- 3Or upload in the Claude apps. Open Settings → Capabilities → Skills and upload the skill.
- 4Paste your Feature PRD. Start a request that describes the feature and includes the full PRD content.
- 5Review the plan. Check folder layout, data model, API and auth against your real system before building.
What an agent skill is and what this one makes the agent do
An agent skill is a folder containing instructions that an AI agent loads when a request matches the skill. This one is a single file, SKILL.md, which is a text prompt. It contains no scripts and does not run code or fetch anything itself.
Once installed, the agent answers feature-planning requests by acting like a senior engineer. It produces a Markdown plan covering goals, requirements, a folder layout of apps, services and packages, architecture and database diagrams in Mermaid, API design, frontend component structure built on shadcn/ui, and security and performance notes.
- Goal and requirements drawn from the PRD
- Folder layout using apps/, services/ and packages/
- System architecture and database diagrams in Mermaid
- API design with TypeScript types and Stack Auth authentication
- Frontend component hierarchy on shadcn/ui, with Zustand or React Query state notes
- Security and performance notes
Install the skill from the ZIP or the Claude apps
Download the ZIP for this skill from this page. Unzip it so that SKILL.md sits in a breakdown-feature-implementation folder. For a personal install, place that folder in ~/.claude/skills/. For a single project, place it in the project's .claude/skills/ folder.
If you use the Claude apps instead, upload the skill under Settings → Capabilities → Skills.
- Personal install: ~/.claude/skills/breakdown-feature-implementation/
- Project install: .claude/skills/breakdown-feature-implementation/ inside your repository
- Claude apps: Settings → Capabilities → Skills, then upload
Trigger the skill with a natural request
You do not need a special command. Describe the task in plain language and include the PRD content, since the template's context section expects the Feature PRD. Mention that you want an implementation plan so the agent matches the skill.
The output is meant to be saved to /docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md. Replace the placeholders with your own epic and feature names when you ask.
- "Using the feature implementation planning skill, write an implementation plan for this PRD: [paste PRD]"
- "Create a technical implementation plan for the notifications feature from the PRD below, following our monorepo layout."
- "Draft the implementation plan for this PRD and save it under docs/ways-of-work/plan/ with the epic and feature names I give you."
What to check in the output
The output is generated text. It can contain wrong assumptions about your system, so engineers should review it before anyone builds from it. Check the folder layout against your real repository, the data model against your existing schema, and the API against your auth rules.
Expect to adapt sections if your stack differs. The template assumes Epoch's monorepo conventions and named libraries such as Stack Auth, tRPC, Zustand, React Query and shadcn/ui.
- Compare the folder layout with your repository
- Confirm the database tables and foreign keys against your schema
- Verify auth and rate-limit assumptions
- Remove or rewrite sections that do not fit your stack
Safety notes: scripts and network
The skill requires nothing to be installed beyond the file itself. It runs no scripts and uses no network access, according to its published assessment. Because it is only a prompt, it does not change your files on its own; any saving of the plan depends on what the agent you are using does with your request.
Treat the PRD you paste as the only input. Do not paste secrets or credentials into the request.
- Runs scripts: no
- Uses network: no
- Requires: nothing listed
Tips for better plans
The plan is only as good as the PRD. Give clear goals, user flows and data needs. Ask for one feature at a time, because the template is written per feature. If the result leans on libraries you do not use, say so in the request and ask for those sections to be rewritten.
- Write a complete PRD before you ask for the plan
- Plan one feature per request
- Ask the agent to note assumptions it made
- Ask for pseudocode rather than code, since the template asks for no code beyond pseudocode
What people use it for
- Drafting a first-pass implementation plan for a new feature in an Epoch-style monorepo
- Producing a consistent plan template across several features for a tech lead
- Getting a Mermaid architecture diagram and entity-relationship diagram as starting points for a design review
- Outlining a frontend component tree on shadcn/ui before a sprint starts
Frequently asked questions
How do I install the breakdown-feature-implementation skill?
Download the ZIP from this page and unzip it so SKILL.md sits in a breakdown-feature-implementation folder. Put that folder in ~/.claude/skills/ for personal use or in a project's .claude/skills/ folder. You can also upload it in the Claude apps under Settings → Capabilities → Skills.
Is the Feature Implementation Planner skill free?
The skill is published under the MIT licence. This page does not list any price for it, so check the licence text in the repository for the terms.
What does the skill need to run?
The skill lists no requirements. It is a single SKILL.md text prompt that runs no scripts and uses no network access.
Can I use this skill if I don't use Epoch's monorepo?
You can, but the template assumes Epoch's monorepo conventions and specific libraries such as Stack Auth, tRPC, Zustand and React Query. Expect to adapt the folder layout and technical sections for a different stack or repository structure.
Why is the plan wrong or missing details?
The output is generated text and can contain wrong assumptions. Give a complete PRD, ask for one feature at a time, and have engineers review the plan before building from it.
How does it compare with writing a plan by hand or using another template?
This skill gives a consistent template covering architecture, data model, API, frontend and security. It does not check your code or verify its output, so it saves drafting time rather than replacing engineering review. If your stack is very different, a template written for your own conventions will fit better.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits engineers and tech leads on Epoch-style monorepos who want a consistent first-draft plan from a PRD, especially if they use Stack Auth, tRPC, Zustand or React Query. Teams with different stacks or repo layouts will spend time adapting the sections, and anyone who needs a verified plan should choose a process with proper engineering review instead.
Download the skill