Official agent skill

Breakdown Feature Implementation

by github in github/awesome-copilot

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

OfficialMITAuto-check passedAgent Workflows

Install Breakdown Feature Implementation

skills CLI
$ npx skills add github/awesome-copilot --skill breakdown-feature-implementation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/awesome-copilot breakdown-feature-implementation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/breakdown-feature-implementation .claude/skills/breakdown-feature-implementation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
breakdown-feature-implementation
GitHub stars
40k
Used in
2 other repos
Token cost
~1.2k tokens
SKILL.md length
398 words
Files
1
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

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

  • Tasks that involve Planning
  • SKILL.md covers Goal, Output Format and Context Template
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Monorepo tooling

What it does

Breakdown Feature Implementation is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Prompt for creating detailed feature implementation plans, following Epoch monorepo structure.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Planning and Monorepo tooling. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

When your agent uses it

  • Tasks that involve Planning
  • Tasks that involve Monorepo tooling

Example prompts

  • “/breakdown-feature-implementation”

Requirements

  • Docker

What it can do on your machine

Read from SKILL.md and the folder at commit 7cce7cf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Breakdown Feature Implementation loads about 1.2k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 398 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 7cce7cf, republished under its MIT licence (© github). 398 words, ~1,169 tokens.

Download SKILL.mdSave it as .claude/skills/breakdown-feature-implementation/SKILL.md (or your agent's skills folder).
name
breakdown-feature-implementation
description
Prompt for creating detailed feature implementation plans, following Epoch monorepo structure.

Feature Implementation Plan Prompt

Goal

Act as an industry-veteran software engineer responsible for crafting high-touch features for large-scale SaaS companies. Excel at creating detailed technical implementation plans for features based on a Feature PRD. Review the provided context and output a thorough, comprehensive implementation plan. Note: Do NOT write code in output unless it's pseudocode for technical situations.

Output Format

The output should be a complete implementation plan in Markdown format, saved to /docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md.

File System

Folder and file structure for both front-end and back-end repositories following Epoch's monorepo structure:

apps/
  [app-name]/
services/
  [service-name]/
packages/
  [package-name]/
Implementation Plan

For each feature:

Goal

Feature goal described (3-5 sentences)

Requirements
  • Detailed feature requirements (bulleted list)
  • Implementation plan specifics
Technical Considerations
System Architecture Overview

Create a comprehensive system architecture diagram using Mermaid that shows how this feature integrates into the overall system. The diagram should include:

  • Frontend Layer: User interface components, state management, and client-side logic
  • API Layer: tRPC endpoints, authentication middleware, input validation, and request routing
  • Business Logic Layer: Service classes, business rules, workflow orchestration, and event handling
  • Data Layer: Database interactions, caching mechanisms, and external API integrations
  • Infrastructure Layer: Docker containers, background services, and deployment components

Use subgraphs to organize these layers clearly. Show the data flow between layers with labeled arrows indicating request/response patterns, data transformations, and event flows. Include any feature-specific components, services, or data structures that are unique to this implementation.

  • Technology Stack Selection: Document choice rationale for each layer
  • Integration Points: Define clear boundaries and communication protocols
  • Deployment Architecture: Docker containerization strategy
  • Scalability Considerations: Horizontal and vertical scaling approaches
Show full SKILL.md (142 more words)Show less
Database Schema Design

Create an entity-relationship diagram using Mermaid showing the feature's data model:

  • Table Specifications: Detailed field definitions with types and constraints
  • Indexing Strategy: Performance-critical indexes and their rationale
  • Foreign Key Relationships: Data integrity and referential constraints
  • Database Migration Strategy: Version control and deployment approach
API Design
  • Endpoints with full specifications
  • Request/response formats with TypeScript types
  • Authentication and authorization with Stack Auth
  • Error handling strategies and status codes
  • Rate limiting and caching strategies
Frontend Architecture
Component Hierarchy Documentation

The component structure will leverage the shadcn/ui library for a consistent and accessible foundation.

Layout Structure:

Recipe Library Page
├── Header Section (shadcn: Card)
│   ├── Title (shadcn: Typography `h1`)
│   ├── Add Recipe Button (shadcn: Button with DropdownMenu)
│   │   ├── Manual Entry (DropdownMenuItem)
│   │   ├── Import from URL (DropdownMenuItem)
│   │   └── Import from PDF (DropdownMenuItem)
│   └── Search Input (shadcn: Input with icon)
├── Main Content Area (flex container)
│   ├── Filter Sidebar (aside)
│   │   ├── Filter Title (shadcn: Typography `h4`)
│   │   ├── Category Filters (shadcn: Checkbox group)
│   │   ├── Cuisine Filters (shadcn: Checkbox group)
│   │   └── Difficulty Filters (shadcn: RadioGroup)
│   └── Recipe Grid (main)
│       └── Recipe Card (shadcn: Card)
│           ├── Recipe Image (img)
│           ├── Recipe Title (shadcn: Typography `h3`)
│           ├── Recipe Tags (shadcn: Badge)
│           └── Quick Actions (shadcn: Button - View, Edit)
  • State Flow Diagram: Component state management using Mermaid
  • Reusable component library specifications
  • State management patterns with Zustand/React Query
  • TypeScript interfaces and types
Security Performance
  • Authentication/authorization requirements
  • Data validation and sanitization
  • Performance optimization strategies
  • Caching mechanisms

Context Template

  • Feature PRD: [The content of the Feature PRD markdown file]

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/breakdown-feature-implementation of github/awesome-copilot.

Open the folder on GitHubat commit 7cce7cf

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Breakdown Feature Implementation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Breakdown Feature Implementation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Breakdown Feature Implementation this skillgithub/awesome-copilot40k2 repos~1.2kAutomated safety check: PassMIT
Write Tech Specbholmesdev/hubble.md1.5k—~1.1kAutomated safety check: NotesMIT
OpenSpec Guided OnboardingFission-AI/OpenSpec71k1 repos~4.5kAutomated safety check: PassMIT
Paseo Committeegetpaseo/paseo20k1 repos~496Automated safety check: PassCustom licence
Improvefossasia/eventyay-interpretation1.6k10 repos~3.7kAutomated safety check: WarnMIT
Implementation Plan Creatortailcallhq/forgecode7.6k1 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Write Tech Spec

    bholmesdev/hubble.md

    Write a TECH.md spec for a significant Hubble feature after researching the monorepo architecture.

    1.5k GitHub stars~1.1k tokensUpdated 6 days ago
    DevelopmentAuto-check: notes
  • OpenSpec Guided Onboarding

    Fission-AI/OpenSpec

    Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.

    71k GitHub starsUsed in 1 repo~4.5k tokens
    Agent WorkflowsAuto-check passed
  • Paseo Committee

    getpaseo/paseo

    Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.

    20k GitHub starsUsed in 1 repo~496 tokens
    Agent WorkflowsAuto-check passed
  • Improve

    fossasia/eventyay-interpretation

    Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute.

    1.6k GitHub starsUsed in 10 repos~3.7k tokens
    Agent WorkflowsAuto-check: warnings
  • Implementation Plan Creator

    tailcallhq/forgecode

    Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.

    7.6k GitHub starsUsed in 1 repo~1.1k tokens
    Agent WorkflowsAuto-check passed
  • Plan Preview

    u-ichi/reviewable-html-workbench

    Plan Mode の <proposedplan を出す直前に、計画の段階・依存関係・検証観点を一時HTMLで視覚確認したい時に使う agent-internal skill。Use this agent-internal skill to create a temporary HTML preview for a plan just before presenting…

    298 GitHub starsUsed in 1 repo~1.8k tokens
    Agent WorkflowsAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo
  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed
  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed
  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Questions about Breakdown Feature Implementation

What does Breakdown Feature Implementation do?

Prompt for creating detailed feature implementation plans, following Epoch monorepo structure. Breakdown Feature Implementation is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Prompt for creating detailed feature implementation plans, following Epoch monorepo structure.

When should I use Breakdown Feature Implementation?

Breakdown Feature Implementation fits situations like: tasks that involve Planning; tasks that involve Monorepo tooling.

How do I install Breakdown Feature Implementation in Claude Code?

Run `npx skills add github/awesome-copilot --skill breakdown-feature-implementation -a claude-code`. Or copy the skill folder (skills/breakdown-feature-implementation in github/awesome-copilot) into .claude/skills/breakdown-feature-implementation in your project. Claude Code loads it when a task matches its description.

How do I install Breakdown Feature Implementation in Codex?

Run `npx skills add github/awesome-copilot --skill breakdown-feature-implementation -a codex`. Or copy the skill folder (skills/breakdown-feature-implementation in github/awesome-copilot) into .agents/skills/breakdown-feature-implementation in your project. Codex loads it when a task matches its description.

Can I use Breakdown Feature Implementation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill breakdown-feature-implementation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/breakdown-feature-implementation, .gemini/skills/breakdown-feature-implementation, .github/skills/breakdown-feature-implementation and .opencode/skills/breakdown-feature-implementation in your project.

What does Breakdown Feature Implementation need to run?

SKILL.md names no scripts, command-line tools or credentials: Breakdown Feature Implementation is instructions for the agent only. Our summary lists: Docker.

Does Breakdown Feature Implementation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Breakdown Feature Implementation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Breakdown Feature Implementation use?

Breakdown Feature Implementation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Breakdown Feature Implementation use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Breakdown Feature Implementation?

Skills that share tags, products or a category with Breakdown Feature Implementation: Write Tech Spec (bholmesdev/hubble.md, 1.5k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars), Paseo Committee (getpaseo/paseo, 20k stars) and Improve (fossasia/eventyay-interpretation, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Breakdown Feature Implementation?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,792 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 8, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.