Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-02-20 02:15:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

refresh readme

Browse Source
This commit is contained in:
Aaron Powell
2026-02-05 13:56:13 +11:00
parent 9c4b267576
commit 647889c0ac
42 changed files with 213 additions and 551 deletions
Download Patch File Download Diff File Expand all files Collapse all files

62
plugins/project-planning/README.md
View File

@@ -1,4 +1,4 @@
# Project Planning Plugin
# Project Planning & Management Plugin
Tools and guidance for software project planning, feature breakdown, epic management, implementation planning, and task organization for development teams.
@@ -6,7 +6,7 @@ Tools and guidance for software project planning, feature breakdown, epic manage
```bash
# Using Copilot CLI
copilot plugin install github/awesome-copilot/plugins/project-planning
copilot plugin install project-planning@awesome-copilot
```
## What's Included
@@ -15,54 +15,26 @@ copilot plugin install github/awesome-copilot/plugins/project-planning
| Command | Description |
|---------|-------------|
| `/project-planning:breakdown-feature-implementation` | Create detailed feature implementation plans |
| `/project-planning:breakdown-feature-prd` | Break down features into PRD format |
| `/project-planning:breakdown-epic-arch` | Architecture breakdown for epics |
| `/project-planning:breakdown-epic-pm` | Product management breakdown for epics |
| `/project-planning:create-implementation-plan` | Generate implementation plans |
| `/project-planning:update-implementation-plan` | Update existing implementation plans |
| `/project-planning:create-github-issues-feature-from-implementation-plan` | Create GitHub issues from plans |
| `/project-planning:create-technical-spike` | Create technical spike documents |
| `/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` | Plan and organize development tasks |
| `task-researcher` | Research context for task planning |
| `planner` | General planning assistance |
| `plan` | Quick planning mode |
| `prd` | Product Requirements Document creation |
| `implementation-plan` | Detailed implementation planning |
| `research-technical-spike` | Technical spike research and documentation |
### Skills
| Skill | Description |
|-------|-------------|
| `planning-guidelines` | Guidelines for task tracking and spec-driven workflows |
## Usage Examples
### Break down a feature
```
/project-planning:breakdown-feature-implementation
I need to implement user authentication with OAuth2
```
### Create an implementation plan
```
/project-planning:create-implementation-plan
Feature: Shopping cart checkout flow
Requirements: Support credit cards, PayPal, and Apple Pay
```
### Use the planning agent
```
@task-planner Help me plan the migration from REST to GraphQL
```
| `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

41
plugins/project-planning/skills/planning-guidelines/SKILL.md
View File

@@ -1,41 +0,0 @@
---
name: planning-guidelines
description: 'Project planning guidelines including task implementation tracking and specification-driven workflow practices for software development teams.'
---
# Planning Guidelines
This skill provides guidelines and best practices for project planning and implementation tracking.
## Included Guidelines
### Task Implementation Tracking
Guidelines for implementing task plans with progressive tracking and change records.
See: [Task Implementation Instructions](../../../instructions/task-implementation.instructions.md)
Key practices:
- Read and understand the complete plan before starting
- Process tasks in order, one at a time
- Track progress in `.copilot-tracking/changes/` files
- Mark tasks complete as you go
- Follow existing workspace patterns and conventions
### Specification-Driven Workflow
A structured approach ensuring requirements are clearly defined, designs are planned, and implementations are documented.
See: [Spec-Driven Workflow v1](../../../instructions/spec-driven-workflow-v1.instructions.md)
Key artifacts to maintain:
- **`requirements.md`**: User stories and acceptance criteria in EARS notation
- **`design.md`**: Technical architecture and sequence diagrams
- **`tasks.md`**: Detailed, trackable implementation plan
## When to Use
Activate these guidelines when:
- Starting a new feature implementation
- Breaking down epics into tasks
- Creating implementation plans
- Tracking progress on complex work
- Ensuring documentation stays in sync with code