Analyze a set of GitHub Issues, identify dependencies, propose an execution order, and define work units. Output a persistent plan document that survives context loss.
If reading issues from GitHub fails, display the error message and stop. If the specified parent issue has no sub-issues, inform the user there are no issues to plan.
When determining order, consider practical benefits: foundational tools first (e.g., a commit skill before other skills, so it can be used during their development).
Plan work by analyzing GitHub Issues, identifying dependencies, proposing execution order, and defining work units that map to feature branches. Outputs a persistent plan document. Use when: plan work, planning, prioritize issues, organize issues, create a plan, work breakdown, define work units, what should I work on first, /planning. Source: caldiaworks/caldiaworks-marketplace.