spec-breakdown

Purpose

Transform spec-review or bugfix investigation artifacts into a coarse task list and task prompts based on business requirements alone. Code investigation is deferred to task-implement.

Input

One of:

• Spec-review artifacts at claude-output/{id}/spec-review/source.md
• Bugfix investigation report at claude-output/{id}/bugfix/investigation-report.md (Status: FINAL)

Coarse Task Criteria

Primary rule

A task is appropriately scoped if it can be described in a single sentence without "and".

• If not: split into separate tasks
• If yes: the task is valid even if it involves heavy internal processing with no user-visible outcome

Split signals (detectable from spec text)

• Additive connectives (e.g. "also", "additionally" — or equivalent in the spec language) appear more than once → split candidate
• Sequential dependency language (e.g. "after X is done", "once X is complete" — or equivalent in the spec language) → split into before/after tasks
• Multiple distinct actors appear with independent goals (e.g., user + admin each triggering separate flows) → split candidate; actors cooperating in a single flow do not qualify

Content rules

• Do NOT reference specific files or class names — those are determined by task-implement
• Exception: if a file/class is explicitly named in the spec, it may be referenced