# Plan Slice

Context: @references/orchestrator-pattern.md ∧ @references/conventions.md

**Autonomy**: check `.tff-cc/settings.yaml` → `autonomy.mode` before pausing.

## Prerequisites
status = planning
SPEC.md ∃ at `.tff-cc/milestones/<milestone>/slices/<id>/SPEC.md`

## Steps

### 1. Load Spec
READ `.tff-cc/milestones/<milestone>/slices/<id>/SPEC.md`
READ `.tff-cc/milestones/<milestone>/slices/<id>/RESEARCH.md` (if ∃)
LOAD @skills/writing-plans/SKILL.md

### 2. File Structure
Map files to create/modify BEFORE tasks.
∀ file: one responsibility, follow existing codebase patterns.
Present file map to user.

### 3. Task Decomposition
DECOMPOSE spec → tasks:
- 1 task = 1 logical unit (may be multiple commits)
- ∀ task: description, files (create/modify/test), acceptance criteria refs (AC1, AC2...), deps
- TDD steps ∀ task:
  1. Write failing test (exact code)
  2. Run test (exact command + expected FAIL)
  3. Write implementation (exact code)
  4. Run test (exact command + expected PASS)
  5. Commit (exact git command)
- Exact file paths, ¬ "add to the service"
- Code snippets, ¬ "implement validation"

### 4. Write PLAN.md
WRITE `.tff-cc/milestones/<milestone>/slices/<id>/PLAN.md`:

```
# [Slice] Implementation Plan

> For agentic workers: execute task-by-task with TDD.

**Goal:** [from SPEC.md]
**Architecture:** [from SPEC.md]
**Tech Stack:** [relevant to slice]

## File Structure
[files to create/modify with responsibilities]

---

### Task N: [Component]
**Files:** Create/Modify/Test with exact paths
**Traces to:** AC1, AC3

- [ ] Step 1: Write failing test [exact code]
- [ ] Step 2: Run [exact command], verify FAIL
- [ ] Step 3: Implement [exact code]
- [ ] Step 4: Run [exact command], verify PASS
- [ ] Step 5: Commit [exact git command]
```

### 5. Create Tasks + Detect Waves
CREATE tasks: `tff-tools` ∀ task w/ deps
DETECT: `tff-tools waves:detect --tasks '[{"id":"T01","dependsOn":[]},{"id":"T02","dependsOn":["T01"]}]'` → show user

### 6. Architecture Review (F-lite ∧ F-full)
LOAD @skills/architecture-review/SKILL.md + @skills/writing-plans/SKILL.md → SPAWN subagent: {plan_content, spec_content}
Issues → revise plan

### 7. Plan Review
DISPATCH anonymous reviewer via Agent tool (prompt: @skills/brainstorming/SKILL.md § Plan Document Reviewer)
Issues → fix, re-dispatch (max 3)

### 8. Plannotator Review
invoke Skill `plannotator-annotate` with arg `.tff-cc/milestones/<milestone>/slices/<id>/PLAN.md`
feedback → revise ∨ approved → continue

### 9. Worktree + Transition
`tff-tools worktree:create --slice-id <id>`
CHECK: `ok` = true → continue | `ok` = false → warn (worktree failure is non-blocking at plan time; execute-slice will block F-lite/F-full if worktree still missing)
`tff-tools slice:transition --slice-id <id> --status executing`
CHECK: `ok` = true → continue | `ok` = false → warn user, offer retry ∨ abort
  IF `ok` = true ∧ `warnings.length > 0`:
    ∀ warning ∈ warnings: display `⚠ <warning>` to user

## Auto-Transition
After completing all steps above:
1. READ `.tff-cc/settings.yaml` → check `autonomy.mode`
2. IF `plan-to-pr`:
   - Non-gate steps: IMMEDIATELY invoke the next workflow — do NOT ask user
   - Human gates (plan approval, spec approval, completion): pause ∧ ask
3. IF `guided`: suggest next step with `/tff:<command>`, wait for user
4. Log: `[tff] <slice-id>: planning → executing`
