project-planning — GitHub Copilot plugin: plans, epics, PRDs
A GitHub Copilot plugin for project work: it breaks features down, writes PRDs and architecture specs, builds implementation plans and files GitHub Issues.
copilot plugin install project-planning@awesome-copilotWhat project-planning does
Eight namespaced slash commands live under project-planning. One turns a feature into implementation steps, another drafts a PRD from an epic, a third produces the technical architecture from that PRD. There is a command for the epic PRD itself, and its output feeds the architecture spec. Separate commands create and update implementation plan files for new features, refactoring, package upgrades or infrastructure.
Seven subagents come along: task-planner, task-researcher, planner, plan, prd, implementation-plan, research-technical-spike. The prd agent writes a Markdown PRD with user stories, acceptance criteria and metrics, and can open GitHub Issues after you confirm. The create-github-issues-feature-from-implementation-plan command does the same from plan phases using the feature_request.yml and chore_request.yml templates — so those templates need to exist in the repo, or there is nothing to file against.
Technical spikes get their own time-boxed documents for decisions you want researched before coding. Installation goes through Copilot CLI; no API key or extra setup is involved. One caveat: the feature breakdown follows the Epoch monorepo structure, so on a differently shaped project the steps may not match your layout.
What it helps with
- split a feature into implementation phases
- draft a PRD from an epic
- derive architecture from an existing PRD
- file GitHub Issues from plan phases
- write a technical spike for an open decision
Example prompts for the agent
- /project-planning:breakdown-feature-prd — write a PRD for this new feature based on the epic
- /project-planning:create-implementation-plan — plan the refactor of the billing module
- /project-planning:create-github-issues-feature-from-implementation-plan — open issues for each plan phase
How to install project-planning
Command from the source
copilot plugin install project-planning@awesome-copilotStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about project-planning
How do I install project-planning in GitHub Copilot?
Through Copilot CLI: copilot plugin install project-planning@awesome-copilot.
What does project-planning do?
It adds commands and subagents for planning work: feature breakdown, PRDs, epic architecture, implementation plans, GitHub Issues and technical spikes.
How is create-implementation-plan different from update-implementation-plan?
The first creates a new plan file; the second adds new or changed requirements to an existing one.
Source text
project-planning · MIT
# Project Planning & Management Plugin Tools and guidance for software project planning, feature breakdown, epic management, implementation planning, and task organization for development teams. ## Installation ```bash # Using Copilot CLI copilot plugin install project-planning@awesome-copilot ``` ## What's Included ### Commands (Slash Commands) | Command | Description | |---------|-------------| | `/project-planning:breakdown-feature-implementation` | Prompt for creating detailed feature implementation plans, following Epoch monorepo structure. | | `/project-planning:breakdown-feature-prd` | Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic. | | `/project-planning:breakdown-epic-arch` | Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document. | | `/project-planning:breakdown-epic-pm` | Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification. | | `/project-planning:create-implementation-plan` | Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure. | | `/project-planning:update-implementation-plan` | Update an existing implementation plan file with new or update requirements to provide new features, refactoring existing code or upgrading packages, design, architecture or infrastructure. | | `/project-planning:create-github-issues-feature-from-implementation-plan` | Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates. | | `/project-planning:create-technical-spike` | Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation. | ### Agents | Agent | Description | |-------|-------------| | `task-planner` | Task planner for creating actionable implementation plans - Brought to you by microsoft/edge-ai | | `task-researcher` | Task research specialist for comprehensive project analysis - Brought to you by microsoft/edge-ai | | `planner` | Generate an implementation plan for new features or refactoring existing code. | | `plan` | Strategic planning and architecture assistant focused on thoughtful analysis before implementation. Helps developers understand codebases, clarify requirements, and develop comprehensive implementation strategies. | | `prd` | Generate a comprehensive Product Requirements Document (PRD) in Markdown, detailing user stories, acceptance criteria, technical considerations, and metrics. Optionally create GitHub issues upon user confirmation. | | `implementation-plan` | Generate an implementation plan for new features or refactoring existing code. | | `research-technical-spike` | Systematically research and validate technical spike documents through exhaustive investigation and controlled experimentation. | ## Source This plugin is part of [Awesome Copilot](https://github.com/github/awesome-copilot), a community-driven collection of GitHub Copilot extensions. ## License MIT
© Awesome Copilot Community · MIT · github/awesome-copilot
