git-issue-plan-workflow

What I do

I implement a standardized GitHub issue creation and planning workflow:

1. Gather Issue Requirements: Prompt user for structured issue description following industry best practices
2. Determine Issue Scope: Ask if issue needs to be broken into sub-issues
3. Create GitHub Issue: Use GitHub CLI to create issue with appropriate labels
4. Create Git Branch: Generate branch from issue number (e.g., GIT-123)
5. Generate PLAN file: Create comprehensive plan with phases and todo list in PLANS/ directory
6. Commit and Push: Commit PLAN file with semantic formatting and push to remote
7. Prompt Execution: Ask user if they want to proceed with plan execution

Framework Skills Used

This workflow delegates to these framework skills for specialized functionality:

When to use me

Use this workflow when:

• Starting a new development task tracked in GitHub Issues
• You want a standardized approach to issue creation and planning
• You need to break down large work into structured phases
• Following the practice of planning before implementation

Prerequisites

• GitHub CLI (gh) installed and authenticated
• Git repository initialized with GitHub remote
• Write access to repository
• gh auth status shows valid authentication

Steps

Step 1: Gather Issue Description

Prompt the user for a structured issue description with these sections:

Required Information:

1. Title: Concise title (max 72 characters)
2. Overview: Brief description of what needs to be done
3. Acceptance Criteria: Definition of done (bullet points)
4. Scope: Files or areas affected
5. Technical Notes: Implementation considerations (optional)

Prompt Template:

Please provide the following for your GitHub issue:

1. **Title** (required): Brief title for the issue
   Example: "Implement user authentication API"

2. **Overview** (required): What does this issue accomplish?
   Example: "Add JWT-based authentication endpoints for user login/registration"

3. **Acceptance Criteria** (required): How do we know it's done?
   Example:
   - Users can register with email/password
   - Users can login and receive JWT token
   - Protected routes validate JWT

4. **Scope** (required): What files/areas will be affected?
   Example: src/api/auth/, src/middleware/, tests/auth/

5. **Technical Notes** (optional): Any implementation details?
   Example: Use bcrypt for password hashing, 24h token expiry