PlugWiki

Breakdown Feature Implementation Skill: PRD to Technical Plan

Turns a feature PRD into a detailed engineering implementation plan in Markdown, with Mermaid diagrams. Listed in github/awesome-copilot.

Installs
9.2K
on skills.sh
Stars
40.7K
on GitHub
Updated
Oct 2026
last repo commit

breakdown-feature-implementation makes your agent act as a veteran SaaS engineer and write a thorough plan from a Feature PRD you paste in. The plan covers file layout, goal, requirements, system architecture, database schema, API design, front-end structure, security and performance. It says not to write code except pseudocode.

It saves the plan to /docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md. The skill is written for one team's stack, named in the text as Epoch's monorepo, tRPC, Stack Auth, shadcn/ui and Zustand/React Query. Adapt those to yours.

Good for

  • Product-minded engineers who already have a feature PRD
  • Tech leads who want architecture, database and API design written down before coding
  • Teams on a monorepo with apps, services and packages folders

Install breakdown-feature-implementation

Claude Code

  1. 1

    Copy this prompt.

    Install the breakdown-feature-implementation skill in Claude Code. Run this command:
    
    npx skills add https://github.com/github/awesome-copilot --skill breakdown-feature-implementation
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

The awesome-copilot README is written for GitHub Copilot. It does not name Claude Code, so these are the standard skill-folder routes.

Built from the package data we hold. Not yet tested by us. Source.

What's in the skill

When it loads

Prompt for creating detailed feature implementation plans, following Epoch monorepo structure.

Sections in SKILL.md

  1. Goal
  2. Output Format
  3. File System
  4. Implementation Plan
  5. Context Template

Key facts

Installs on skills.sh
9,243 (Nov 2, 2026)
Last repo commit
Oct 30, 2026
Files in the folder
1 file: SKILL.md

What it includes

  • Reads the Feature PRD you provide as the context for the plan

    The prompt ends with a context template that holds the content of the Feature PRD markdown file.

    Read · Input: Feature PRD

  • Lists the folders for front-end and back-end under apps, services and packages

    The layout follows what SKILL.md calls Epoch's monorepo structure.

    File system layout

  • Writes a 3 to 5 sentence goal and a bulleted requirement list

    Each feature gets a goal and detailed requirements with implementation specifics.

    Goal and requirements

  • Draws a Mermaid diagram across five layers with labeled data flow

    The layers are frontend, API, business logic, data and infrastructure. It also asks for stack choices, integration points, deployment and scaling notes.

    System architecture overview

  • Draws a Mermaid entity-relationship diagram and specifies tables and indexes

    Also covers foreign keys and the migration strategy.

    Database schema design

  • Specifies endpoints, TypeScript types, Stack Auth rules, errors, rate limits and caching

    The text names tRPC endpoints and Stack Auth.

    API design

  • Documents the component tree with shadcn/ui parts, state flow and TypeScript types

    It includes a sample layout tree for a recipe library page and asks for Zustand and React Query state patterns.

    Frontend architecture

  • Lists auth rules, validation, performance work and caching

    The last of five technical-consideration sections.

    Security and performance

  • Writes implementation-plan.md under /docs/ways-of-work/plan/{epic-name}/{feature-name}/

    The output path is fixed by the prompt.

    Write · Save the plan

From the official docs

Permissions

Low risk

The skill writes one plan file, and the Copilot plugin route adds agents that can edit files, run commands and open GitHub issues. Use the skill-only route unless you want those agents.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • The Copilot plugin adds agents that can edit files

    The plugin lists 7 agents. implementation-plan, task-planner, task-researcher and research-technical-spike include edit and terminal-run tools. prd includes create_issue, update_issue and add_issue_comment. Install only the skill if you do not want these. github.com

  • It writes a file into your repo

    The plan is saved to /docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md. It would replace a file of the same name, so check the path first. github.com

  • Community content, not reviewed by GitHub for you

    The awesome-copilot README says the customizations are sourced from third-party developers and asks you to inspect them before installing. Read the SKILL.md first. github.com

Technical details
Scopes
  • Writes one Markdown plan file under /docs/ways-of-work/plan/

  • The Copilot plugin route adds 7 agents (see findings)

Questions

What does breakdown-feature-implementation do?

It turns a Feature PRD into a full technical plan: file layout, architecture and database diagrams, API and front-end design, security and performance. It saves the result as a Markdown file.

How do I install it?

Use the install box above. In GitHub Copilot CLI it can also come with the project-planning plugin, which adds seven agents. Read the safety box before you take the plugin.

Where does the plan go?

To /docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md, a path fixed in the prompt. Tell your agent the epic and feature names.

Does it write code?

No code, per SKILL.md: "Do NOT write code in output unless it's pseudocode for technical situations."

Is it tied to a specific tech stack?

Yes. The prompt names Epoch's monorepo layout, tRPC, Stack Auth, shadcn/ui, Zustand and React Query. If your stack differs, say so up front.

Is it safe?

The skill itself bundles no scripts and writes one Markdown file. The larger risk is the project-planning plugin, whose agents can edit files, run terminal commands or create GitHub issues. Skip the plugin if you only want this skill.

Does it work in Claude Code or the Claude app?

The file is a standard SKILL.md, and the install box shows how to place it in Claude Code or upload it to Claude. The awesome-copilot README targets GitHub Copilot, and nothing in the repo says this skill was tested in Claude.

Information

updated Nov 2, 2026

Folder
skills/breakdown-feature-implementation

github/awesome-copilotskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 6
  1. github/awesome-copilot README · github.com
  2. project-planning plugin.json · github.com
  3. breakdown-feature-implementation SKILL.md · github.com
  4. implementation-plan agent · github.com
  5. prd agent · github.com
  6. task-planner agent · github.com

Updated Nov 2, 2026.