planner-task-breakdown

Decompose planner work into four-field tasks with sizing rules.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/gonz0w/bgsd-oc --skill planner-task-breakdown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner-task-breakdown
Source: https://github.com/gonz0w/bgsd-oc/tree/main/skills/planner-task-breakdown
Command: npx skills add https://github.com/gonz0w/bgsd-oc --skill planner-task-breakdown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines a robust task decomposition framework for planners, ensuring every task has precise four-field specs (files, action, verify, done) and a sizing policy to enable autonomous execution across phases.

Core Features & Use Cases

  • Four-field task anatomy: enforce <files>, <action>, <verify>, <done> specification for every task.
  • Task types & sizing: guidelines for auto vs checkpoint tasks and 15-60 minute sizing.
  • TDD detection heuristic: recommended RED-GREEN-REFACTOR workflow for critical logic.
  • Specificity and user-setup: standards to ensure deterministic execution and external-service readiness.
  • Execution guidance: placeholders like {{phase}} to support phase-aware planning.

Quick Start

Document a phase task using the four-field anatomy and run a planning pass to generate detailed tasks.

Frequently Asked Questions about planner-task-breakdown

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

FAQPage Schema
How do I break down complex software phases into executable tasks?

Task decomposition splits complex phase planning into precise tasks using a four-field specification of files, action, verify, and done to ensure autonomous execution. This enforces deterministic sizing of 15-60 minutes per task.

What is the four-field task specification format for software planning?

The four-field task specification formats each planner task with files, action, verify, and done fields. This structure enforces specificity checks and sizing rules to enable consistent autonomous execution across phases.

How do I apply TDD heuristics during task decomposition?

TDD heuristics during task decomposition recommend a RED-GREEN-REFACTOR workflow for critical logic. This ensures test verification is embedded directly within the task specification for robust phase planning.

How do I size tasks for 15-60 minute autonomous execution?

Task sizing for autonomous execution requires breaking work into 15-60 minute increments using defined auto and checkpoint task types. This ensures each task remains specific and deterministic for agent execution.

Does task decomposition work with external service detection?

Task decomposition supports external service detection by embedding specificity and user-setup standards within the task specification. This ensures external-service readiness and deterministic execution across all generated planner tasks.

When should I not use auto tasks in phase planning?

Auto tasks should be avoided in phase planning when execution requires manual verification or external-service setup. In these cases, use checkpoint task types to ensure deterministic execution and proper completion feedback.