Project Task Breakdown Guide

Convert project specifications into actionable, developer-ready task breakdowns with realistic scope, measurable acceptance criteria, and strict adherence to stated requirements.

Process

1. Analyze the Specification

• Locate the canonical spec (check repo root, docs/, or project config).
• Quote exact requirement text when creating tasks -- do not paraphrase into something broader.
• List every ambiguity, gap, or contradiction found. Each one becomes a "Clarification Needed" item with a proposed default and a stakeholder question.
• Extract the technical stack, constraints, and integration points.

2. Break Down Tasks