skills.rest
davekim917
davekim917COMMUNITY
Explore all skills by this author →
GitHub

team-plan

Convert approved designs into structured task plans with dependencies and acceptance criteria.

1|Updated Mar 6, 2026
Search Tags:#planning#specification#governance#traceability#risk-management#task-decomposition#design-to-build
One-click install
npx skills add https://github.com/davekim917/bootstrap --skill team-plan-davekim917
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-plan
Source: https://github.com/davekim917/bootstrap/tree/main/plugins/workflow/skills/team-plan
Command: npx skills add https://github.com/davekim917/bootstrap --skill team-plan-davekim917

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts approved designs into a deterministic, builder-ready execution plan, preventing guesswork and drift.

Core Features & Use Cases

  • Identifies task boundaries from designs and reviews
  • Groups tasks into independently executable units with clear ownership and pre-conditions
  • Produces complete task specifications including file paths, interfaces, test plans, and acceptance criteria
  • Applies constraint injection and render-check mapping to ensure governance and traceability
  • Validates plan completeness against dependencies and test coverage

Quick Start

Invoke /team-plan after a design review to generate a complete plan at docs/specs/<feature>/plan.md.

Frequently Asked Questions about team-plan

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

FAQPage Schema
How do I convert approved designs into builder-ready execution plans?▼

To turn designs into builder-ready execution plans, you can use a task planning process that analyzes design.md and review.md artifacts to generate grouped task specifications, dependencies, and acceptance criteria for verifiable delivery.

What is task decomposition for preventing scope creep in software engineering?▼

Task decomposition for preventing scope creep involves breaking approved designs into independently executable units with clear ownership, pre-conditions, and constraint injection to enforce traceability and ensure deterministic execution from inception to delivery.

How do I generate task specifications with file paths and test plans from a design review?▼

Generating task specifications from a design review requires analyzing decisions.yaml and CLAUDE.md artifacts to produce complete execution plans including file paths, interfaces, test plans, and acceptance criteria validated against dependencies.

Can I enforce traceability and render-check mapping when creating task plans?▼

Yes, you can enforce traceability and render-check mapping during task plan creation by applying constraint injection to the generated task specifications, validating plan completeness against dependencies and test coverage to prevent guesswork and drift.

Does task planning work without dependencies for governing software delivery?▼

Task planning for governing software delivery works without external dependencies, relying solely on input artifacts like design.md and review.md to produce structured task specs and dependency mappings for execution.

Related Skills

Explore More Software Engineering Skills→
davekim917davekim917
1

team-review

Run three independent design reviews and generate a consolidated report.

Community
Advanced
Alif-NAlif-N

planning-and-task-breakdown

Decompose specifications into verifiable tasks with acceptance criteria and dependency ordering.

Community
Intermediate
nahisahonahisaho
12

orchestrator

Coordinates 25 specialized AI agents for specification-driven development projects.

Community
Advanced
whichguywhichguy

kanban-orchestrator

Orchestrate Kanban task workflows with SOUL.md routing and dependency management.

Community
Advanced