magnus919_agent-skills/spec-driven-development/templates/TASK-PLAN.md

Task Plan: <Project / Feature Name>

Source Specification

• Spec: SPEC.md (version <x.y.z>)
• Spec review gate: Approved / Conditions
• Plan author:
• Plan version: 0.1.0

Phase Overview

Metric	Value
Total tasks
Task groups
Critical path	tasks
Estimated total effort
Dependencies	real dependencies

Execution Order

<Recommended execution order. Start with foundational tasks (contracts, schemas, interfaces), then core logic, then integration, then edge cases and error handling.>

Task Groups

Group 1:

Spec reference: SPEC.md — Section Preconditions: Dependencies:

ID	Task	Spec Ref	Est. Size	Preconditions
T-001		AC-001.x	S/M/L
T-002		AC-001.x	S/M/L	T-001

Group 2:

...

Critical Path

<Chain of dependent tasks determining overall timeline. Tasks on the critical path have zero float — delay in any one delays the entire plan.>

Task Cards

Copy this structure for each task.

---

T-001:

• Type: feature / refactor / test / docs / config
• Spec reference: SPEC.md — US-001, AC-001.1, AC-001.2
• Dependencies:
• Estimated size: Small (<1h) / Medium (1-2h) / Large (2-4h)
• Preconditions:

Description:

<What this task implements, derived from the spec.>

Acceptance Criteria:

• AC-001.1: <condition — directly from SPEC.md>
• AC-001.2: <condition — directly from SPEC.md>

Implementation Agent Directives:

<This section becomes the context file (CLAUDE.md / .cursorrules / AGENTS.md) for the implementation agent running this task.>

• Load SPEC.md section for behavioral requirements
• Load the interface contract from SPEC.md section
• Implement in this scope:
• Do NOT implement:

---

Revision History

Version	Date	Author	Change
0.1.0			Initial plan from SPEC.md v0.x