Breakdown-Plan

# 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`

Related Planning Prompts

- **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

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

# 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