review-tasklisted

# Review Task Docs Review all planning documents for a task and leave structured inline comments flagging problems, questions, and improvements. This is a planning review -- you use the full codebase as ground truth to verify claims in the docs. > Part of the task planning workflow. See [references/workflow-overview.md](references/workflow-overview.md) for the full pipeline. ## Input The user provides a task ID (e.g. `042`) or a task folder name (e.g. `042-add-team-settings`). If ambiguous, check `docs/tasks/` for a matching folder. ## Process ### Step 1: Load Context 1. Find the task folder under `docs/tasks/` matching the provided ID 2. Read ALL docs: `requirements.md`, `solution.md`, `context.md`, `plan.md` 3. Read any project docs referenced by the task docs (linked concept docs, how-to guides) ### Step 2: Codebase Verification For each doc, verify claims against the actual codebase: **requirements.md** - Are acceptance criteria testable and unambiguous? - Do referenced features/pages actually exist? - Are there implicit dependencies not mentioned? - Does "Out of Scope" make sense, or will the task be incomplete without those items? **solution.md** - Do listed file paths exist (for `~` modified files) or make sense as new files (`+`)? - Do referenced types, functions, and services have the described signatures? - Does the approach match established project patterns? - Are there security concerns -- auth, tenant isolation, input validation? - Does the test cover