Official agent skill

Breakdown Plan

by github in github/awesome-copilot

Issue Planning and Automation prompt that generates comprehensive project plans with Epic Feature Story/Enabler Test hierarchy, dependencies, priorities, and automated tracking.

OfficialMITAuto-check passedProduct & Project Management

Install Breakdown Plan

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

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

GitHub CLI
$ gh skill install github/awesome-copilot breakdown-plan --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-plan .claude/skills/breakdown-plan && 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-plan
GitHub stars
40k
Used in
1 other repo
Token cost
~3.8k tokens
SKILL.md length
921 words
Files
1
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

Issue Planning and Automation prompt that generates comprehensive project plans with Epic Feature Story/Enabler Test hierarchy, dependencies, priorities, and automated tracking.

  • Works in 9 steps: Project Overview → Work Item Hierarchy → GitHub Issues Breakdown → …
  • Tasks that involve Project management
  • SKILL.md covers Goal, GitHub Project Management Best…, Input Requirements and Output Format, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Breakdown Plan is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Issue Planning and Automation prompt that generates comprehensive project plans with Epic Feature Story/Enabler Test hierarchy, dependencies, priorities, and automated tracking.

Its SKILL.md is about 3.8k 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 Product & Project Management, covering Project management. It works with GitHub. 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 Project management

Example prompts

  • “/breakdown-plan”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Project Overview
  2. Work Item Hierarchy
  3. GitHub Issues Breakdown
  4. Priority and Value Matrix
  5. Estimation Guidelines
  6. Dependency Management
  7. Sprint Planning Template
  8. GitHub Project Board Configuration
  9. Automation and GitHub Actions

What it can do on your machine

Read from SKILL.md and the folder at commit 727ff2e. 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 (its code samples are markdown, mermaid and yaml).

    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 Plan loads about 3.8k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 921 words of instructions outside code blocks.

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

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 727ff2e, republished under its MIT licence (© github). 921 words, ~3,763 tokens.

Download SKILL.mdSave it as .claude/skills/breakdown-plan/SKILL.md (or your agent's skills folder).
name
breakdown-plan
description
Issue Planning and Automation prompt that generates comprehensive project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated tracking.

GitHub Issue Planning & Project Automation Prompt

Goal

Act as a senior Project Manager and DevOps specialist with expertise in Agile methodology and GitHub project management. Your task is to take the complete set of feature artifacts (PRD, UX design, technical breakdown, testing plan) and generate a comprehensive GitHub project plan with automated issue creation, dependency linking, priority assignment, and Kanban-style tracking.

GitHub Project Management Best Practices

Agile Work Item Hierarchy
  • Epic: Large business capability spanning multiple features (milestone level)
  • Feature: Deliverable user-facing functionality within an epic
  • Story: User-focused requirement that delivers value independently
  • Enabler: Technical infrastructure or architectural work supporting stories
  • Test: Quality assurance work for validating stories and enablers
  • Task: Implementation-level work breakdown for stories/enablers
Project Management Principles
  • INVEST Criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
  • Definition of Ready: Clear acceptance criteria before work begins
  • Definition of Done: Quality gates and completion criteria
  • Dependency Management: Clear blocking relationships and critical path identification
  • Value-Based Prioritization: Business value vs. effort matrix for decision making

Input Requirements

Before using this prompt, ensure you have the complete testing workflow artifacts:

Core Feature Documents
  1. Feature PRD: /docs/ways-of-work/plan/{epic-name}/{feature-name}.md
  2. Technical Breakdown: /docs/ways-of-work/plan/{epic-name}/{feature-name}/technical-breakdown.md
  3. Implementation Plan: /docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md
  • Test Planning: Use plan-test prompt for comprehensive test strategy, quality assurance planning, and test issue creation
  • Architecture Planning: Use plan-epic-arch prompt for system architecture and technical design
  • Feature Planning: Use plan-feature-prd prompt for detailed feature requirements and specifications

Output Format

Create two primary deliverables:

  1. Project Plan: /docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md
  2. Issue Creation Checklist: /docs/ways-of-work/plan/{epic-name}/{feature-name}/issues-checklist.md
Project Plan Structure
1. Project Overview
  • Feature Summary: Brief description and business value
  • Success Criteria: Measurable outcomes and KPIs
  • Key Milestones: Breakdown of major deliverables without timelines
  • Risk Assessment: Potential blockers and mitigation strategies
2. Work Item Hierarchy
mermaid
graph TD
    A[Epic: {Epic Name}] --> B[Feature: {Feature Name}]
    B --> C[Story 1: {User Story}]
    B --> D[Story 2: {User Story}]
    B --> E[Enabler 1: {Technical Work}]
    B --> F[Enabler 2: {Infrastructure}]

    C --> G[Task: Frontend Implementation]
    C --> H[Task: API Integration]
    C --> I[Test: E2E Scenarios]

    D --> J[Task: Component Development]
    D --> K[Task: State Management]
    D --> L[Test: Unit Tests]

    E --> M[Task: Database Schema]
    E --> N[Task: Migration Scripts]

    F --> O[Task: CI/CD Pipeline]
    F --> P[Task: Monitoring Setup]
3. GitHub Issues Breakdown
Epic Issue Template
markdown
# Epic: {Epic Name}

## Epic Description

{Epic summary from PRD}

## Business Value

- **Primary Goal**: {Main business objective}
- **Success Metrics**: {KPIs and measurable outcomes}
- **User Impact**: {How users will benefit}

## Epic Acceptance Criteria

- [ ] {High-level requirement 1}
- [ ] {High-level requirement 2}
- [ ] {High-level requirement 3}

## Features in this Epic

- [ ] #{feature-issue-number} - {Feature Name}

## Definition of Done

- [ ] All feature stories completed
- [ ] End-to-end testing passed
- [ ] Performance benchmarks met
- [ ] Documentation updated
- [ ] User acceptance testing completed

## Labels

`epic`, `{priority-level}`, `{value-tier}`

## Milestone

{Release version/date}

## Estimate

{Epic-level t-shirt size: XS, S, M, L, XL, XXL}
Feature Issue Template
markdown
# Feature: {Feature Name}

## Feature Description

{Feature summary from PRD}

## User Stories in this Feature

- [ ] #{story-issue-number} - {User Story Title}
- [ ] #{story-issue-number} - {User Story Title}

## Technical Enablers

- [ ] #{enabler-issue-number} - {Enabler Title}
- [ ] #{enabler-issue-number} - {Enabler Title}

## Dependencies

**Blocks**: {List of issues this feature blocks}
**Blocked by**: {List of issues blocking this feature}

## Acceptance Criteria

- [ ] {Feature-level requirement 1}
- [ ] {Feature-level requirement 2}

## Definition of Done

- [ ] All user stories delivered
- [ ] Technical enablers completed
- [ ] Integration testing passed
- [ ] UX review approved
- [ ] Performance testing completed

## Labels

`feature`, `{priority-level}`, `{value-tier}`, `{component-name}`

## Epic

#{epic-issue-number}

## Estimate

{Story points or t-shirt size}
User Story Issue Template
markdown
# User Story: {Story Title}

## Story Statement

As a **{user type}**, I want **{goal}** so that **{benefit}**.

## Acceptance Criteria

- [ ] {Specific testable requirement 1}
- [ ] {Specific testable requirement 2}
- [ ] {Specific testable requirement 3}

## Technical Tasks

- [ ] #{task-issue-number} - {Implementation task}
- [ ] #{task-issue-number} - {Integration task}

## Testing Requirements

- [ ] #{test-issue-number} - {Test implementation}

## Dependencies

**Blocked by**: {Dependencies that must be completed first}

## Definition of Done

- [ ] Acceptance criteria met
- [ ] Code review approved
- [ ] Unit tests written and passing
- [ ] Integration tests passing
- [ ] UX design implemented
- [ ] Accessibility requirements met

## Labels

`user-story`, `{priority-level}`, `frontend/backend/fullstack`, `{component-name}`

## Feature

#{feature-issue-number}

## Estimate

{Story points: 1, 2, 3, 5, 8}
Technical Enabler Issue Template
markdown
# Technical Enabler: {Enabler Title}

## Enabler Description

{Technical work required to support user stories}

## Technical Requirements

- [ ] {Technical requirement 1}
- [ ] {Technical requirement 2}

## Implementation Tasks

- [ ] #{task-issue-number} - {Implementation detail}
- [ ] #{task-issue-number} - {Infrastructure setup}

## User Stories Enabled

This enabler supports:

- #{story-issue-number} - {Story title}
- #{story-issue-number} - {Story title}

## Acceptance Criteria

- [ ] {Technical validation 1}
- [ ] {Technical validation 2}
- [ ] Performance benchmarks met

## Definition of Done

- [ ] Implementation completed
- [ ] Unit tests written
- [ ] Integration tests passing
- [ ] Documentation updated
- [ ] Code review approved

## Labels

`enabler`, `{priority-level}`, `infrastructure/api/database`, `{component-name}`

## Feature

#{feature-issue-number}

## Estimate

{Story points or effort estimate}
4. Priority and Value Matrix
PriorityValueCriteriaLabels
P0HighCritical path, blocking releasepriority-critical, value-high
P1HighCore functionality, user-facingpriority-high, value-high
P1MediumCore functionality, internalpriority-high, value-medium
P2MediumImportant but not blockingpriority-medium, value-medium
P3LowNice to have, technical debtpriority-low, value-low
5. Estimation Guidelines
Story Point Scale (Fibonacci)
  • 1 point: Simple change, <4 hours
  • 2 points: Small feature, <1 day
  • 3 points: Medium feature, 1-2 days
  • 5 points: Large feature, 3-5 days
  • 8 points: Complex feature, 1-2 weeks
  • 13+ points: Epic-level work, needs breakdown
T-Shirt Sizing (Epics/Features)
  • XS: 1-2 story points total
  • S: 3-8 story points total
  • M: 8-20 story points total
  • L: 20-40 story points total
  • XL: 40+ story points total (consider breaking down)
6. Dependency Management
mermaid
graph LR
    A[Epic Planning] --> B[Feature Definition]
    B --> C[Enabler Implementation]
    C --> D[Story Development]
    D --> E[Testing Execution]
    E --> F[Feature Delivery]

    G[Infrastructure Setup] --> C
    H[API Design] --> D
    I[Database Schema] --> C
    J[Authentication] --> D
Dependency Types
  • Blocks: Work that cannot proceed until this is complete
  • Related: Work that shares context but not blocking
  • Prerequisite: Required infrastructure or setup work
  • Parallel: Work that can proceed simultaneously
7. Sprint Planning Template
Sprint Capacity Planning
  • Team Velocity: {Average story points per sprint}
  • Sprint Duration: {2-week sprints recommended}
  • Buffer Allocation: 20% for unexpected work and bug fixes
  • Focus Factor: 70-80% of total time on planned work
Sprint Goal Definition
markdown
## Sprint {N} Goal

**Primary Objective**: {Main deliverable for this sprint}

**Stories in Sprint**:

- #{issue} - {Story title} ({points} pts)
- #{issue} - {Story title} ({points} pts)

**Total Commitment**: {points} story points
**Success Criteria**: {Measurable outcomes}
8. GitHub Project Board Configuration
Column Structure (Kanban)
  1. Backlog: Prioritized and ready for planning
  2. Sprint Ready: Detailed and estimated, ready for development
  3. In Progress: Currently being worked on
  4. In Review: Code review, testing, or stakeholder review
  5. Testing: QA validation and acceptance testing
  6. Done: Completed and accepted
Show full SKILL.md (369 more words)Show less
Custom Fields Configuration
  • Priority: P0, P1, P2, P3
  • Value: High, Medium, Low
  • Component: Frontend, Backend, Infrastructure, Testing
  • Estimate: Story points or t-shirt size
  • Sprint: Current sprint assignment
  • Assignee: Responsible team member
  • Epic: Parent epic reference
9. Automation and GitHub Actions
Automated Issue Creation
yaml
name: Create Feature Issues

on:
  workflow_dispatch:
    inputs:
      feature_name:
        description: 'Feature name'
        required: true
      epic_issue:
        description: 'Epic issue number'
        required: true

jobs:
  create-issues:
    runs-on: ubuntu-latest
    steps:
      - name: Create Feature Issue
        uses: actions/github-script@v7
        with:
          script: |
            const { data: epic } = await github.rest.issues.get({
              owner: context.repo.owner,
              repo: context.repo.repo,
              issue_number: ${{ github.event.inputs.epic_issue }}
            });

            const featureIssue = await github.rest.issues.create({
              owner: context.repo.owner,
              repo: context.repo.repo,
              title: `Feature: ${{ github.event.inputs.feature_name }}`,
              body: `# Feature: ${{ github.event.inputs.feature_name }}\n\n...`,
              labels: ['feature', 'priority-medium'],
              milestone: epic.data.milestone?.number
            });
Automated Status Updates
yaml
name: Update Issue Status

on:
  pull_request:
    types: [opened, closed]

jobs:
  update-status:
    runs-on: ubuntu-latest
    steps:
      - name: Move to In Review
        if: github.event.action == 'opened'
        uses: actions/github-script@v7
        # Move related issues to "In Review" column

      - name: Move to Done
        if: github.event.action == 'closed' && github.event.pull_request.merged
        uses: actions/github-script@v7
        # Move related issues to "Done" column
Issue Creation Checklist
Pre-Creation Preparation
  • Feature artifacts complete: PRD, UX design, technical breakdown, testing plan
  • Epic exists: Parent epic issue created with proper labels and milestone
  • Project board configured: Columns, custom fields, and automation rules set up
  • Team capacity assessed: Sprint planning and resource allocation completed
Epic Level Issues
  • Epic issue created with comprehensive description and acceptance criteria
  • Epic milestone created with target release date
  • Epic labels applied: epic, priority, value, and team labels
  • Epic added to project board in appropriate column
Feature Level Issues
  • Feature issue created linking to parent epic
  • Feature dependencies identified and documented
  • Feature estimation completed using t-shirt sizing
  • Feature acceptance criteria defined with measurable outcomes
Story/Enabler Level Issues documented in /docs/ways-of-work/plan/{epic-name}/{feature-name}/issues-checklist.md
  • User stories created following INVEST criteria
  • Technical enablers identified and prioritized
  • Story point estimates assigned using Fibonacci scale
  • Dependencies mapped between stories and enablers
  • Acceptance criteria detailed with testable requirements

Success Metrics

Project Management KPIs
  • Sprint Predictability: >80% of committed work completed per sprint
  • Cycle Time: Average time from "In Progress" to "Done" <5 business days
  • Lead Time: Average time from "Backlog" to "Done" <2 weeks
  • Defect Escape Rate: <5% of stories require post-release fixes
  • Team Velocity: Consistent story point delivery across sprints
Process Efficiency Metrics
  • Issue Creation Time: <1 hour to create full feature breakdown
  • Dependency Resolution: <24 hours to resolve blocking dependencies
  • Status Update Accuracy: >95% automated status transitions working correctly
  • Documentation Completeness: 100% of issues have required template fields
  • Cross-Team Collaboration: <2 business days for external dependency resolution
Project Delivery Metrics
  • Definition of Done Compliance: 100% of completed stories meet DoD criteria
  • Acceptance Criteria Coverage: 100% of acceptance criteria validated
  • Sprint Goal Achievement: >90% of sprint goals successfully delivered
  • Stakeholder Satisfaction: >90% stakeholder approval for completed features
  • Planning Accuracy: <10% variance between estimated and actual delivery time

This comprehensive GitHub project management approach ensures complete traceability from epic-level planning down to individual implementation tasks, with automated tracking and clear accountability for all team members.

© 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-plan of github/awesome-copilot.

Open the folder on GitHubat commit 727ff2e

Used in 1 other repository

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

Compare with similar skills

Breakdown Plan 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 Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Breakdown Plan this skillgithub/awesome-copilot40k1 repos~3.8kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Project Managerpwrdrvr/openclaw-codex-app-server265—~1.5kAutomated safety check: PassMIT
Find Project Anomaliespenpot/penpot61k—~1.2kAutomated safety check: PassMPL-2.0
PublishQ00/ouroboros6.2k—~2.7kAutomated safety check: PassMIT
Gh Read Inspectoreclipse-rdf4j/rdf4j420—~950Automated safety check: PassBSD-3-Clause

Similar skills

  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Project Manager

    pwrdrvr/openclaw-codex-app-server

    Manage GitHub issues and the GitHub Project board for the current repository, while keeping the local tracker in sync.

    265 GitHub stars~1.5k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed
  • Check a GitHub milestone against the Main project board, report the five anomaly types to tmp/<MILESTONE-ANOMALIES.md, and fix missing milestone assignments on request.

    61k GitHub stars~1.2k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Publish

    Q00/ouroboros

    Publish Seed specification as GitHub Issues for team-based project management

    6.2k GitHub stars~2.7k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Gh Read Inspector

    eclipse-rdf4j/rdf4j

    Retrieve GitHub issues, pull requests, and milestones with read-only, whitelisted gh commands only.

    420 GitHub stars~950 tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Manages GitHub issues and project boards with swarm coordination: issue creation and triage, issue-to-task conversion, progress tracking and stale issue cleanup.

    816 GitHub starsUsed in 6 repos~7.1k tokens
    Product & Project ManagementAuto-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

Works with

Questions about Breakdown Plan

What does Breakdown Plan do?

Issue Planning and Automation prompt that generates comprehensive project plans with Epic Feature Story/Enabler Test hierarchy, dependencies, priorities, and automated tracking. Breakdown Plan is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Issue Planning and Automation prompt that generates comprehensive project plans with Epic Feature Story/Enabler Test hierarchy, dependencies, priorities, and automated tracking.

When should I use Breakdown Plan?

Breakdown Plan fits situations like: tasks that involve Project management.

How do I install Breakdown Plan in Claude Code?

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

How do I install Breakdown Plan in Codex?

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

Can I use Breakdown Plan 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-plan -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-plan, .gemini/skills/breakdown-plan, .github/skills/breakdown-plan and .opencode/skills/breakdown-plan in your project.

What does Breakdown Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Breakdown Plan is instructions for the agent only.

Does Breakdown Plan 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 Plan 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 Plan use?

Breakdown Plan 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 Plan use?

About 3.8k tokens (SKILL.md is roughly 15k 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 Plan?

Skills that share tags, products or a category with Breakdown Plan: CCPM Project Management (automazeio/ccpm, 8.4k stars), Project Manager (pwrdrvr/openclaw-codex-app-server, 265 stars), Find Project Anomalies (penpot/penpot, 61k stars) and Publish (Q00/ouroboros, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Breakdown Plan?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 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.