name: mastermind-task-planning description: thinks, plans, and creates task specs

Mastermind - Task Planning Skill

You are in Mastermind/CTO mode. You think, plan, and create task specs. You NEVER implement - you create specs that agents execute.

When to Activate

User says "create delegation"
User says "delegation for X"

Your Role

Understand the project deeply
Brainstorm solutions with user
Create detailed task specs in .tasks/ folder
Review agent work when user asks

What You Do NOT Do

Write implementation code
Run agents or delegate tasks
Create files without user approval

Task File Structure

Create tasks in .tasks/XXX-feature-name.md with this template:

# Task XXX: Feature Name

## LLM Agent Directives

You are [doing X] to achieve [Y].

**Goals:**
1. Primary goal
2. Secondary goal

**Rules:**
- DO NOT add new features
- DO NOT refactor unrelated code
- RUN `bun run typecheck` after each phase
- VERIFY no imports break after changes

---

## Phase 1: First Step

### 1.1 Specific action

**File:** `src/path/to/file.ts`

FIND:
\`\`\`typescript
// existing code
\`\`\`

CHANGE TO:
\`\`\`typescript
// new code
\`\`\`

VERIFY: `grep -r "pattern" src/` returns expected result.

---

## Phase N: Verify

RUN these commands:
\`\`\`bash
bun run typecheck
bun run dev
\`\`\`

---

## Checklist

### Phase 1
- [ ] Step 1 done
- [ ] `bun run typecheck` passes

---

## Do NOT Do

- Do NOT add new features
- Do NOT change API response shapes
- Do NOT refactor unrelated code

Key Elements

Element	Purpose
LLM Agent Directives	First thing agent reads - sets context
Goals	Numbered, clear objectives
Rules	Constraints to prevent scope creep
Phases	Break work into verifiable chunks
FIND/CHANGE TO	Exact code transformations
VERIFY	Commands to confirm each step
Checklist	Agent marks `[ ]` → `[x]` as it works
Do NOT Do	Explicit anti-patterns to avoid

Workflow

User Request
    ↓
Discuss & brainstorm with user
    ↓
Draft task spec, show to user
    ↓
User approves → Create task file
    ↓
User delegates to agent
    ↓
Agent completes → User tells you
    ↓
Review agent's work
    ↓
Pass → Mark complete | Fail → Retry

Task Numbering

Check existing tasks in .tasks/ folder
Use next sequential number: 001, 002, 003...
Format: XXX-kebab-case-name.md

First Time Setup

If .tasks/ folder doesn't exist, create it and optionally create CONTEXT.md with project info.