From autoworker
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.
npx claudepluginhub phj128/autoworker --plugin autoworkerThis skill uses the workspace's default tool permissions.
After Plan Mode discussion is complete and user has confirmed direction, invoke this skill to create the first half of subtask.md.
Complete subtask verification plan: upstream traceability table + L1-L4 test plan + self-check. Call after autoworker:subtask-init. Makes subtask ready for code implementation.
Generates executable Markdown implementation plans for multi-step tasks from context briefs, resolving ambiguities, ordering dependencies, and enabling parallel worker execution.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
After Plan Mode discussion is complete and user has confirmed direction, invoke this skill to create the first half of subtask.md.
Glob `subtask_*.md` (current directory) + Glob `claude_docs/subtask/*.md` (archive)
→ Extract all sequence numbers → take max + 1
Review the conversation and extract:
Extract assumptions that depend on external systems from plan and conversation. Each assumption needs:
Pure internal logic changes (e.g., refactoring, documentation): Write one line No external dependencies | — | —.
Glob/Grep search for related files → confirm paths and line numbers
Do not guess line numbers — must Read to confirm.
Extract from plan file / conversation:
Glob `subtask_*.md` (exclude subtask_template.md) →
For each file grep `status: active` →
Edit all found to `status: paused`
Purpose: Ensure at most 1 active subtask at any time. Creating a new subtask automatically pauses old ones.
Language rule: subtask.md is an internal work document. Write it in the user's conversation language (as configured in their CLAUDE.md or inferred from their messages). Do NOT use the task's target language — e.g., if the task is "translate to English", the subtask itself should still be in the user's language.
Reference the table structure in subtask template, Write file:
subtask_<sequence>_<name>_<date>.md
First line after title: write status: active (flush left, grep-friendly format).
Include these sections (result columns left empty):
Line by line, read the "verification experiment" column of the assumptions table:
Hard rules:
Subtask first half created: subtask_<sequence>_<name>.md
- Assumption verification: <N>/<N> passed
- Acceptance criteria: <N> (or "No quantitative metrics")
- Paused old subtask: <list paused filenames, or "None">
→ Automatically invoking autoworker:subtask-plan
After outputting the summary above, immediately invoke autoworker:subtask-plan. Do not wait for user instructions, do nothing else.