team-plan

Generate tactical implementation plans from structure, design, and research files.

8|1|Updated Mar 28, 2026

Search Tags:#automation #workflow #planning #development #implementation #orchestration

Ready to run

npx skills add https://github.com/bostonaholic/team --skill team-plan-bostonaholic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-plan
Source: https://github.com/bostonaholic/team/tree/main/skills/team-plan
Command: npx skills add https://github.com/bostonaholic/team --skill team-plan-bostonaholic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the ambiguity of moving from a high-level design to actionable development steps by automatically generating a structured, tactical implementation plan.

Core Features & Use Cases

Automated Planning: Derives file-level steps and acceptance test mappings from existing structure, design, and research artifacts.
Workflow Integration: Acts as a critical bridge in the QRSPI pipeline, ensuring the implementer has a clear, step-by-step roadmap.
Use Case: After completing the design phase for a new API endpoint, use this skill to generate the specific implementation tasks required to build the feature.

Quick Start

Run the team-plan skill to generate the implementation steps for the most recent project directory.

Frequently Asked Questions about team-plan

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

FAQPage Schema

How do I generate a tactical implementation plan from design artifacts?▼

To generate a tactical implementation plan, you synthesize existing structure.md, design.md, and research.md artifacts into actionable, file-level development steps. This process bridges high-level design and actual coding by deriving clear steps and acceptance test mappings.

Why does my implementation planning workflow fail without structure.md?▼

Implementation planning fails because the tool requires a valid project directory with structure.md, design.md, and research.md to function. Without these specific research and design artifacts, it cannot synthesize actionable development steps or map acceptance tests.

When do I need automated implementation planning in software development?▼

You need automated implementation planning when moving from a high-level design to actionable development steps. It eliminates ambiguity by automatically generating a structured, step-by-step roadmap for the implementation phase of a feature.

Can I use this tactical planning approach for my API endpoint development?▼

Yes, you can use this tactical planning approach for API endpoint development. After completing the design phase, it automatically generates the specific implementation tasks required to build the feature, providing a clear roadmap for the implementer.

What is the best way to map acceptance tests to development steps?▼

The best way to map acceptance tests to development steps is by synthesizing structure, design, and research artifacts within an orchestration workflow. This automatically derives file-level steps and their corresponding acceptance test mappings for clear implementation.