new-tasklisted

# New Task Create `docs/tasks/$ID-$NAME/requirements.md` from user input. > Part of the task planning workflow. See [references/workflow-overview.md](references/workflow-overview.md) for the full pipeline. ## Guiding Principles Before writing anything, apply these checks: - State your assumptions explicitly. If uncertain about what the user wants, ask -- don't guess. - If the request has multiple interpretations, present them and let the user pick. - If the scope seems too large for a single task, say so and suggest splitting. - Push back if something is unclear. Name what's confusing and ask. ## Process 1. **Scan skills** -- check available skills for topic matches relevant to the user's request. Load any matched skills before proceeding. 2. **Read project docs** -- find and read project documentation relevant to the domain (READMEs, how-to guides, concept docs, CLAUDE.md). 3. **Determine task ID** -- scan `docs/tasks/` for existing folders. Assign the next 3-digit sequential ID (e.g. if `042-*` exists, next is `043`). If `docs/tasks/` doesn't exist, start at `001`. 4. **Derive task name** -- create a short kebab-case name from the user's description (e.g. `add-team-settings`). 5. **Create task folder** -- `mkdir -p docs/tasks/$ID-$NAME` 6. **Write requirements.md** -- use the template and rules below. Fill in Problem, Goals, and Acceptance Criteria from user input. Add Out of Scope based on reasonable boundaries. List any unresolved questions in Open Questions. 7. **R