tasks

Generate phase-based RED-GREEN task breakdowns from architecture design documents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/macollins27/guardrails-plugin --skill tasks-macollins27
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tasks
Source: https://github.com/macollins27/guardrails-plugin/tree/main/skills/tasks
Command: npx skills add https://github.com/macollins27/guardrails-plugin --skill tasks-macollins27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Task breakdown translates architecture design and planning documents into a concrete, executable list of tasks, enabling safe, self-contained work units for subagents.

Core Features & Use Cases

  • Phase-based planning: breaks features into 3-6 phases with clear RED-GREEN cycles and a final gate.
  • File/test specificity: each task specifies exact files, exact signatures, and concrete Given/When/Then test details.
  • Constitution-aware: tasks reference constitutional constraints and ensure compliance per phase.
  • Self-contained handoff: any task can be executed in isolation by a fresh subagent with no prior context.

Quick Start

Read the feature’s specs and design, then generate specs/NNN-feature/tasks.md with a phase-based RED-GREEN task breakdown.

Frequently Asked Questions about tasks

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

FAQPage Schema
How do I break architecture design documents into test-driven tasks?▼

To break architecture design into test-driven tasks, analyze the design and planning documents to generate a structured phase-based task breakdown, producing a complete specs directory file with RED-GREEN task pairs and gate checkpoints.

What is a RED-GREEN task pair in phase-based planning?▼

A RED-GREEN task pair in phase-based planning defines a specific failing test first, followed by the implementation task to make that test pass, ensuring test-driven development cycles within isolated subagent execution units.

How do I generate subagent-ready task files from feature specs?▼

Generating subagent-ready task files requires analyzing feature specs to output a structured tasks.md file containing exact file paths, precise signatures, and Given/When/Then test details so any fresh subagent can execute tasks in isolation.

Can I use phase-based task breakdowns for fresh subagent execution?▼

Yes, phase-based task breakdowns are specifically designed for fresh subagent execution by creating self-contained work units that specify exact files, concrete test details, and constitutional constraints without requiring prior context.

How do gate checkpoints work in test-driven task generation?▼

Gate checkpoints in test-driven task generation act as phase transition validation points within the 3-6 phase breakdown, ensuring all RED-GREEN cycles for a phase are complete and constitutional constraints are met before proceeding.

What limitations exist when translating design documents into task breakdowns?▼

Translating design documents into task breakdowns requires existing architecture design and planning documents as input, and relies on strict adherence to constitutional, PATTERNS, and TESTING-RULES constraints to ensure the generated tasks remain executable by subagents.