---
name: speckit-ultraplan-tasks
description: Generate a deeply-reasoned, implementation-ready task breakdown for the
  current spec-kit feature using extended analysis.
compatibility: Requires spec-kit project structure with .specify/ directory
metadata:
  author: github-spec-kit
  source: workflows:commands/ultraplan-tasks.md
---

ultrathink

You are generating a comprehensive task breakdown for the current spec-kit feature by deeply analysing the specification and plan.

## Steps

### 1. Load Feature Context

```bash
cd "$(git rev-parse --show-toplevel)" && \
source .specify/scripts/bash/common.sh && \
get_feature_paths
```

This provides `FEATURE_DIR`, `FEATURE_SPEC` (spec.md), `IMPL_PLAN` (plan.md), and `TASKS` (tasks.md). Load and carefully read all three files before continuing.

### 2. Deep Analysis

Conduct a thorough analysis of the specification and plan:

- Identify every distinct unit of work implied by the acceptance criteria
- Trace dependencies between work units — sequence tasks to minimise blocked work
- Surface hidden concerns: error handling, edge cases, test coverage, migrations, documentation
- Flag any ambiguous requirements in a brief "Clarifications" note at the top of tasks.md
- Estimate relative complexity (S/M/L) for each task

### 3. Generate Tasks

Overwrite `$TASKS` (tasks.md) with the full breakdown using this format:

```markdown
# Tasks: [Feature Name]

> Generated by speckit.ultraplan — edit freely.

<!-- Clarifications (remove when resolved):
- [Any ambiguities spotted during analysis]
-->

## Implementation Tasks

- [ ] T001: [Concrete, single-concern task — one commit]
- [ ] T002: [Concrete, single-concern task — one commit]
...
```

Rules:
- Each task must be independently implementable (one logical change, one commit)
- Group tasks in implementation order; add a blank line between phases if needed
- Include setup, implementation, test, and documentation tasks
- IDs are sequential T001…T0NN; do not reuse IDs from a previous tasks.md
- Do not exceed 20 tasks; if scope demands more, list the overflow as a "## Deferred Tasks" section with a brief note on why they are out of scope for this iteration

### 4. Report

After writing tasks.md, output:

```
Ultraplan complete

**Feature**: [feature name]
**Tasks generated**: [N]
**Tasks file**: [absolute path to tasks.md]

### Task summary
T001 — [one-line description]
T002 — [one-line description]
...
```