subtask-init

Create first-half subtask.md files with confirmation details and verification results.

17|3|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/phj128/autoworker --skill subtask-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subtask-init
Source: https://github.com/phj128/autoworker/tree/main/skills/subtask-init
Command: npx skills add https://github.com/phj128/autoworker --skill subtask-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Automates creation of the first-half subtask.md with the needed fields and provenance.
  • Automatically pauses any older active subtasks to ensure a single active task at a time.
  • Validates assumptions by executing predefined verification experiments and records results for audit.

Quick Start

Execute the subtask-init skill after you have confirmed direction in Plan Mode; it will generate subtask.md and initiate the verification workflow.

Frequently Asked Questions about subtask-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate subtask documentation after confirming a project plan?

Subtask documentation automation extracts confirmation records, goals, constraints, and acceptance criteria to generate a structured subtask.md file. It collects provenance details and determines sequence numbers for task tracking within gate-based planning workflows.

What is the process for validating planning assumptions before writing code?

Assumption validation executes predefined verification experiments and automatically records the results for audit. This ensures documented assumptions are tested and proven before development begins, providing verified context for downstream implementation.

Can I pause existing active subtasks to ensure only one task runs at a time?

Pausing existing active subtasks is handled automatically during subtask initialization. The workflow ensures a single active task at a time by pausing older tasks before creating new subtask documentation and starting verification.

When do I need to create subtask documentation in a gate-based planning workflow?

Subtask documentation is needed after Gate 1.1 user confirmation is complete and before writing any code. It captures confirmed direction, goals, and constraints from Plan Mode to establish a verified foundation for subsequent implementation phases.

Does subtask initialization work with sequential task numbering and provenance tracking?

Subtask initialization determines sequence numbers automatically and tracks provenance for all collected fields. User confirmation details, goals, constraints, acceptance criteria, and references are recorded with their source information for full audit traceability.