← ClaudeAtlas

subtask-initlisted

Create subtask document (first half): user confirmation, goals, assumptions. Auto-runs assumption verification experiments and fills in results. Call after Gate 1.1 (user confirmation) is done, before writing any code.
phj128/autoworker · ★ 13 · AI & Automation · score 74
Install: claude install-skill phj128/autoworker
# autoworker:subtask-init — Create Subtask First Half (Gate 1.3 Step A+B) After Plan Mode discussion is complete and user has confirmed direction, invoke this skill to create the first half of subtask.md. ## Execution Flow ### 1. Determine Sequence Number ``` Glob `subtask_*.md` (current directory) + Glob `claude_docs/subtask/*.md` (archive) → Extract all sequence numbers → take max + 1 ``` ### 2. Extract Confirmation Record from Conversation Context Review the conversation and extract: - **Confirmation method**: AskUserQuestion / confirmed in plan discussion / explicit in user instruction - **Key Q&A**: scope, completion criteria, constraints, preferences - **Goal**: WHY + WHAT (1-3 sentences) - **Success criteria**: specific measurable items - **Acceptance criteria**: Extract quantifiable metrics from plan (metric name + measurement method + expected value/range + tolerance). When no quantitative metrics exist, explicitly write "No quantitative metrics, reason: <fill in>" ### 3. Identify Core Assumptions Extract assumptions that depend on external systems from plan and conversation. Each assumption needs: - Assumption description (I assume X because Y) - Verification experiment (one-line command) **Pure internal logic changes** (e.g., refactoring, documentation): Write one line `No external dependencies | — | —`. ### 4. Search for Reference Files ``` Glob/Grep search for related files → confirm paths and line numbers ``` **Do not guess line numbers** — must Read