sdd-plan-taskslisted

# Plan SDD tasks 1. Resolve `tasks/prd-[slug]/`. Require and read `prd.md` and `techspec.md`, in that order, once per version. Then inventory `tasks.md`, `task_*.md`, and `done/task_*.md`. Reuse an existing plan without overwriting; for an authorized update, preserve IDs, handoffs, and completed tasks. **Output:** sources and state reconciled; broken links or conflicting IDs block only the affected update. 2. Extract obligations, decisions, components, risks, and tests in one pass. Preserve IDs; for legacy sources, assign local IDs and origin section. Map each item to delivery and evidence, or to a pending item that changes scope/acceptance. **Output:** complete, traceable inventory, including out-of-scope limits. 3. Use vertical slices: one reviewable result, implementation, and tests in the same task. Separate foundation only when it unlocks multiple deliveries or enables independent migration. Model acyclic dependencies and file/contract collisions; number new tasks after the largest ID in root and `done/`. **Output:** every non-pending item has a task; every task has origin, limits, dependencies, and verification. 4. Apply the TechSpec profile. In desktop C#/.NET, omit E2E even locally and record the exclusion; keep relevant unit/integration tests and a manual script for visual acceptance. In mixed repositories, classify by project. For other targets, use E2E only when relevant to the contract. Prefer local validation that proves behavior. A fake does not pro