task-builder

Generate a tasks.md file with T-XXX IDs, AC coverage, and parallelization markers.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/gaabscps/ai-squad --skill task-builder-gaabscps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-builder
Source: https://github.com/gaabscps/ai-squad/tree/main/squads/sdd/skills/task-builder
Command: npx skills add https://github.com/gaabscps/ai-squad --skill task-builder-gaabscps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Task Builder solves the manual, error-prone process of turning an approved Spec and Plan into a precise, task-level plan (tasks.md) that can be executed in phases with AC coverage and [P] parallelization markers.

Core Features & Use Cases

  • Interactive vertical-slice decomposition following GitHub Spec Kit patterns.
  • Generates a detailed tasks.md with T-XXX IDs, US references, AC coverage, and optional [P] markers.
  • Validates preconditions and enforces approval states before producing drafts.

Quick Start

Invoke /task-builder FEAT-NNN after Spec and Plan are approved to generate the initial tasks draft.

Frequently Asked Questions about task-builder

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

FAQPage Schema
How do I decompose an approved spec into a task graph for SDD-style development?

To decompose an approved spec into a task graph, you can automate the creation of a granular tasks.md file that maps T-XXX tasks with acceptance criteria coverage and parallelization markers. This enforces preconditions and translates plans into verifiable execution.

What is the best way to generate a tasks.md file with acceptance criteria coverage?

Generating a tasks.md file with AC coverage is best handled by an automated workflow that decomposes approved specs into atomic tasks with US references and optional [P] parallelization markers. This ensures verifiable phased execution.

How does vertical-slice decomposition work with GitHub Spec Kit patterns?

Vertical-slice decomposition with Spec Kit patterns works by interactively translating approved specs and plans into a detailed tasks.md file. It assigns T-XXX IDs and maps acceptance criteria coverage for each slice.

Do I need an approved plan before generating task-level execution plans?

Yes, you need an approved plan and spec before generating task-level execution plans. The workflow validates preconditions and enforces approval states before producing any task drafts, though a PM-mode bypass logic is supported.

Can I use task decomposition for phased project management with parallelization markers?

Yes, you can use task decomposition for phased project management by generating a tasks.md file with optional [P] parallelization markers. This allows verifiable, phased execution of the approved spec and plan.

Why does automated task scoping enforce preconditions before producing drafts?

Automated task scoping enforces preconditions to ensure specs and plans are fully approved before generating drafts. This prevents errors from manual translation and maintains valid approval states through atomic session state writes.