write-taskslisted

# Write Tasks Turn `docs/specs/<slug>/_prd.md` (and `_techspec.md` when present) into the executable task graph: one `task_NN.md` per task plus `_tasks.md`, the manifest that `implement-task`, `implement-spec`, and any future daemon schedule from. The artifacts are the contract — a fresh agent session must be able to pick up one task file and build it with no other context than the spec folder. ## Preconditions `$ARGUMENTS` names the spec. `_prd.md` must exist. If `_techspec.md` is missing on a feature with real architectural surface, run `write-techspec` first and then decompose — authoring the missing artifact is the resolution, never a reason to stop for permission. Under autonomous work this needs no confirmation: directing autonomous work authorizes the whole authoring chain for every Spec already in the approved queue, per `docs/agents/autonomous-work.md`. Ask for acceptance only when explicitly told to decompose *without* a tech spec, and then compensate with deeper codebase exploration before decomposing. ### Project Constraint preflight Run this preflight before deriving or approving a breakdown: 1. Classify the Spec. A Spec under `docs/specs/_archived/`, or one proven to have completed before this contract applied, is a completed or archived legacy Spec. Leave every legacy artifact byte-identical: do not backfill, reformat, regenerate, or otherwise rewrite it. 2. For every active, non-archived, and not already completed Spec, require the PRD and ev