subtask-plan

Automates preparation and verification of carpentry and other craftwork estimates and invoices.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the creation and verification of subtask plans by automating upstream traceability, L1-L4 verification write-ups, and self-check logging, ensuring alignment with project requirements.

Core Features & Use Cases

  • Upstream Traceability: captures source text and delta rationale from plan inputs to ensure traceability.
  • Verification Plan Generation: auto-writes L1-L4 verification steps, coverage tables, and acceptance criteria alignment.
  • Self-Check & Dispatch: performs a four-question self-check and triggers autoworker:dispatch to advance the chain.

Quick Start

After autoworker:subtask-init completes, run autoworker:dispatch to generate and validate the verification plan.

Frequently Asked Questions about subtask-plan

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

FAQPage Schema
How do I automate subtask verification and traceability for my project plans?

To automate subtask verification, you can use a skill that populates upstream traceability, generates L1-L4 verification content, and logs self-checks to ensure plan completeness and acceptance criteria coverage. This process streamlines alignment with project requirements end-to-end.

What is L1-L4 verification coverage and how does it work for subtasks?

L1-L4 verification coverage is an automated tiered validation process that generates detailed verification steps and coverage tables for subtasks. It works by aligning acceptance criteria across four levels, ensuring comprehensive quality gates and traceability within your project workflow.

How do I generate verification steps and acceptance criteria for subtask plans?

You can generate verification steps and acceptance criteria by running an automation skill after subtask initialization. This automatically writes L1-L4 verification content, captures upstream source text, and aligns acceptance criteria to deliver complete traceability for your plans.

Do I need a subtask initialization step before running verification automation?

Yes, you need to complete subtask initialization first. The verification and traceability automation applies specifically after subtask-init completes, using its outputs to populate upstream rationale, generate L1-L4 verification plans, and perform self-checks before dispatching.

What's the best way to ensure quality gates and traceability in subtask planning?

The best way to ensure quality gates and traceability is implementing an automated verification workflow that captures upstream deltas, writes tiered L1-L4 verification content, and performs self-check logging before advancing the execution chain through dispatch triggers.

Why does my subtask plan fail acceptance criteria coverage checks?

Subtask plans fail acceptance criteria coverage when upstream traceability and L1-L4 verification content are incomplete. Automating the population of source text, delta rationale, and verification steps ensures comprehensive coverage and passes self-check quality gates before dispatch.