Task Planning Skill

Explores requirements via brainstorming, then creates structured task folder for implementation.

REQUIRED SUB-SKILL: Use superpowers:brainstorming FIRST to explore requirements before creating files.

When to Use

Starting a feature that spans multiple files
Work that needs design before implementation
Complex changes requiring step-by-step planning

Workflow

1. Run Brainstorming

MANDATORY: Invoke superpowers:brainstorming skill first to:

Clarify user intent and requirements
Explore technical approaches
Identify edge cases and constraints
Get user approval on design direction

Only proceed to step 2 after brainstorming is complete.

2. Determine Next Folder Number

CRITICAL: Use the Glob tool (not ls) to find existing task folders:

Glob pattern: _tasks/[0-9][0-9]-*

This returns all numbered task folders. Find the highest {NN}-* number and use next one (e.g., if 31-fix-stats-consumption exists, use 32).

WARNING: Do NOT use ls _tasks/ or Glob _tasks/* — these may miss subdirectories or return incomplete results.

3. Create Folder and Task File

Create folder and write _tasks/{NN}-{feature-name}/01-task.md with brainstorming output:

**Date:** YYYY-MM-DD
**Subject:** {Feature description from brainstorming}
**Status:** Planning

## Goal

{Goal refined during brainstorming}

## Requirements

{Requirements gathered during brainstorming}

## Technical Notes

{Constraints and considerations from brainstorming}

4. Create Plan File

Use superpowers:writing-plans to create detailed implementation plan, then write to _tasks/{NN}-{feature-name}/02-plan.md:

# {Feature Name} Implementation Plan

> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.

**Goal:** {One-line summary}

**Architecture:** {High-level approach}

---

## Task 1: {Description}

**Files:**
- Modify: `path/to/file`
- Create: `path/to/new/file`

**Steps:**
1. {Step details}
2. {Step details}

**Verification:** {How to verify this task is complete}

---

## Task 2: ...

5. Commit Planning Docs

git add _tasks/{NN}-{feature-name}/
git commit -m "docs: add task and plan for {feature-name}"

File Naming Convention

Files are numbered sequentially — no two files share the same number:

| File | Purpose | |------|---------| | 01-task.md | Requirements, goals, context | | 02-*.md | Second doc (design, plan, or other) | | 03-*.md | Third doc (if needed) | | ... | Continue sequentially |

Common patterns:

Task only: 01-task.md
Task + plan: 01-task.md, 02-plan.md
Task + design + plan: 01-task.md, 02-design.md, 03-plan.md

Notes

Always commit planning docs BEFORE starting implementation
Reference tech debt if task originates from _TECH_DEBT/
Keep plans actionable with specific file paths and verification steps