create-tasks

Create GitHub Tasks

Analyze a feature plan or PRD and create the appropriate GitHub issue structure. Automatically decides whether to create a single issue or an epic with multiple task issues based on scope and complexity.

Configuration

Read cloudstack.json from the project root at the start of execution. Extract relevant fields:

• REPO_OWNER / REPO_NAME = repository.owner / repository.name (default: detect from git remote -v)

If cloudstack.json does not exist, auto-detect by parsing the GitHub remote URL:

git remote get-url origin | sed -E 's|.*github\.com[:/]([^/]+)/([^/.]+).*|\1 \2|'

Arguments

• {prd-path} -- Path to PRD file (optional, will search docs/prd/ or use conversation context)
• --dry-run -- Show what would be created without actually creating issues
• --epic-only -- Create only the epic issue, not individual tasks
• --no-epic -- Create only task issues, no parent epic

Decision Logic: Single vs Multiple Issues

Create a SINGLE issue when:

• Feature has <= 3 implementation tasks
• All tasks affect the same service/layer
• Work is small enough for one PR (roughly < 1 day of work)
• No PRD exists -- just a simple feature plan from conversation

Create an EPIC + task issues when:

• Feature has > 3 implementation tasks
• Tasks span multiple services or layers
• A PRD exists with structured sections
• Tasks could be assigned to different people or done in separate PRs
• --epic-only or --no-epic flags override this logic

Process

Step 1: Find the Plan

1. If path provided, read that file
2. Else search docs/prd/*.md for most recent PRD
3. Else look for feature plan in conversation context
4. If nothing found, ask user to describe the feature or run /plan-feature or /prd first

Step 2: Parse & Classify

Extract from the plan:

• Title: Feature name
• Summary: Description
• Acceptance Criteria: All AC items
• Tasks: Implementation tasks grouped by layer
• Out of Scope: Exclusions
• Labels: Derive from affected services (see Label Mapping below)