supervisor-plan-tasks

Decompose architectural plans into vertical implementation slices with TDD integration.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dayvidpham/pasture --skill supervisor-plan-tasks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: supervisor-plan-tasks
Source: https://github.com/dayvidpham/pasture/tree/main/.opencode/skill/supervisor-plan-tasks
Command: npx skills add https://github.com/dayvidpham/pasture --skill supervisor-plan-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the dual-export anti-pattern where workers lack ownership of full production code paths, preventing fragmented development and ensuring clear accountability during implementation phases.

Core Features & Use Cases

  • Vertical Slice Decomposition: Breaks ratified plans into discrete, end-to-end tasks (types, tests, implementation, wiring) owned by a single worker.
  • Layered TDD Integration: Enforces a layer-cake approach where tests define contracts and implementation follows, ensuring high-quality, verifiable code.
  • Use Case: When transitioning from a high-level architectural plan to execution, use this skill to generate specific, parallelizable tasks for a team that maintain end-to-end integrity for each feature.

Quick Start

Use the supervisor-plan-tasks skill to decompose the current ratified plan into vertical slices by requesting a review-effort budget and generating the corresponding task list.

Frequently Asked Questions about supervisor-plan-tasks

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

FAQPage Schema
How do I decompose architectural plans into vertical slices for parallel execution?▼

Decomposing architectural plans into vertical slices breaks high-level designs into discrete end-to-end tasks, ensuring full-stack ownership and parallel execution. Each slice covers types, tests, implementation, and wiring owned by a single worker.

What is the dual-export anti-pattern in software engineering workflows?▼

The dual-export anti-pattern occurs when workers lack ownership of full production code paths, causing fragmented development. Vertical slice decomposition solves this by assigning end-to-end task ownership to maintain clear accountability during implementation.

How do I integrate TDD into task planning during the transition from design to implementation?▼

Integrating TDD into task planning uses a layer-cake approach where tests define contracts and implementation follows. This enforces high-quality, verifiable code by generating tasks that maintain end-to-end integrity for each feature.

Can I configure review-cycle budgeting for task decomposition?▼

Configuring review-cycle budgeting for task decomposition is supported by requesting a review-effort budget when generating the task list. This satisfies requirements for clear integration point documentation and TDD-based development.

Does vertical slice decomposition work without dependencies for task management?▼

Vertical slice decomposition operates independently without external dependencies, generating parallelizable tasks directly from ratified plans. It requires no prerequisite tools to break plans into discrete end-to-end implementation slices.

Why does fragmented development occur when transitioning from architectural plans to execution?▼

Fragmented development occurs during the transition from architectural plans to execution when tasks lack full-stack ownership. Decomposing plans into vertical slices prevents this by ensuring each worker owns complete production code paths end-to-end.