task-planning

# Task Planning Skill

## Overview

The **task-planning** skill guides planning of operational tasks that don't require test-driven development. Unlike feature work (which goes through brainstorming → rough-draft → TDD), operational tasks follow a simpler path: brainstorming → task-planning → direct execution.

This skill is invoked internally by the collab workflow for items classified as "task" type (docker, installs, configuration, organization, cleanup, deployment).

## When to Use

- After brainstorming completes for a "task" type work item
- For operational work that doesn't involve code implementation with tests
- When planning: docker container setup, library installations, folder organization, deployment procedures, cleanup tasks

## Collab Session Required

This skill operates within an active collab session. It reads the current work item from the session's design document and updates it with planning phases.

## Browser-Based Questions

When a collab session is active, use `render_ui` for all user interactions.

**Component selection:**
| Question Type | Component |
|--------------|-----------|
| Yes/No | Card with action buttons |
| Choose 1 of 2-5 | RadioGroup |
| Choose 1 of 6+ | MultipleChoice |
| Free text | TextInput or TextArea |

**Example - Yes/No:**
```
Tool: mcp__plugin_mermaid-collab_mermaid__render_ui
Args: {
  "project": "<cwd>",
  "session": "<session>",
  "ui": {
    "type": "Card",
    "props": { "title": "<question context>" },
    "children": [{ "type": "Markdown", "props": { "content": "<question>" } }],
    "actions": [
      { "id": "yes", "label": "Yes", "primary": true },
      { "id": "no", "label": "No" }
    ]
  },
  "blocking": true
}
```

**Terminal prompts only when:** No collab session exists (pre-session selection).

```
Collab Session Structure:
.collab/[session-name]/
├── design.md                 (updated with Prerequisites/Steps/Verification)
├── collab-state.json        (contains currentItem reference)
└── context-sna