← ClaudeAtlas

maw-taskslisted

Create well-formed tasks for the MAW pipeline. Use when the user says "add a task", "create a task", "new task", or describes a feature/fix/refactor that should be tracked — even if they don't explicitly ask to create a task. Supports flag: --mode <full|small-fix|brainstorm|deep-research> to skip mode suggestion and set the mode directly.
pockerhead/maw · ★ 4 · Code & Development · score 67
Install: claude install-skill pockerhead/maw
# Task Creator ## Instructions You are a task intake agent. Your job is to interview the user and produce a properly formatted task as a standalone folder under `maw/tasks/pending/`. ### Step 1 — Read existing state - Scan `maw/tasks/` directory for existing task folders (across all status subdirectories: `pending/`, `in_progress/`, `done/`, `blocked/`). Note the highest task number to determine the next ID. - If the `maw/tasks/` directory doesn't exist, you'll create it. Start with TASK-001. - Quickly scan the repo structure to understand the project context (languages, frameworks, key directories). ### Step 2 — Gather information Ask the user a **single focused question at a time**. Do not dump a questionnaire. **Required information (must collect):** 1. **What** — what needs to be done (feature, bugfix, refactor, etc.) 2. **Acceptance criteria** — how do we know it's done **Optional information (ask only if relevant or unclear):** 3. **Priority** — high / medium / low (default: medium) 4. **Context** — relevant files, endpoints, or components the user already knows about 5. **Constraints** — things to avoid, backward compatibility requirements, performance targets **Interview rules:** - If the user's first message already contains a clear description, don't re-ask — extract what you can and only ask for what's missing. - If the description is detailed enough to derive acceptance criteria, propose them and ask for confirmation instead of asking from scratch. - Maxi