planning-implementation

Generates tactical plan.md files with file-level steps and acceptance tests.

8|1|Updated Mar 28, 2026

Search Tags:#workflow #planning #development #implementation #agent #tactical

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the ambiguity in agent-driven development by providing a rigorous, scannable methodology for breaking down complex features into actionable, file-level implementation steps.

Core Features & Use Cases

Tactical Plan Generation: Enforces a structured plan.md template that maps vertical slices to specific file modifications and acceptance tests.
Scope Enforcement: Implements strict rules to keep plans under 300 lines and ensures atomic, verifiable commits for each slice.
Use Case: When tasked with a large feature, use this skill to generate a clear, step-by-step playbook that ensures the implementer agent stays focused, avoids scope creep, and maintains a working codebase throughout the process.

Quick Start

Invoke the planning-implementation skill to generate a structured tactical plan for the current feature request.

Frequently Asked Questions about planning-implementation

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

FAQPage Schema

How do I standardize agent planning into tactical implementation steps?▼

Standardize agent planning by enforcing a structured plan.md template that maps vertical slices to specific file modifications and acceptance tests. This methodology breaks complex features into actionable, file-level steps to prevent implementation drift.

What is the best way to prevent implementation drift in autonomous agent workflows?▼

Prevent implementation drift by generating a scannable, scoped tactical plan that enforces strict rules for atomic commits. This structured methodology requires precise file-level steps and acceptance test mappings to keep the implementer agent focused.

How do I generate a tactical plan for vertical slice implementation?▼

Generate a tactical plan by invoking the planning skill to create a structured playbook for the current feature request. The plan maps vertical slices to specific file modifications, keeping the document under 300 lines for scannable verification.

Can I use tactical planning to enforce atomic commits for feature development?▼

Yes, tactical planning implements strict scope enforcement rules that ensure atomic, verifiable commits for each vertical slice. This approach maintains a working codebase throughout the software development process by mapping acceptance tests to file modifications.

What are the limitations of using structured tactical plans for complex software development?▼

A key limitation is that structured tactical plans must stay under 300 lines to remain scannable, which may restrict use on exceptionally large features. The methodology specifically targets complex software development workflows requiring precise file-level steps.

Why does my autonomous agent lose scope during complex feature implementation?▼

Autonomous agents lose scope due to ambiguity in development tasks. A rigorous, scannable methodology that maps vertical slices to specific file modifications and acceptance tests provides the step-by-step playbook needed to avoid scope creep.