Which project management tools are supported?

The skill supports Beans, GitHub Issues, Azure DevOps, and standard Markdown plan files for tracking work items.

How does it handle existing code context?

It explores your current codebase before breaking down a phase to ensure the proposed features align with the latest architecture and previously implemented modules.

Does this skill write the code for me?

No, it focuses on the planning and definition stage, creating the work items and acceptance criteria that guide the subsequent implementation phase.

What is a vertical slice in this context?

A vertical slice refers to a feature that includes all layers of the stack (UI, logic, database) to deliver a complete piece of functionality rather than just a horizontal layer.

Plan Phase Breakdown

Name: Plan Phase Breakdown
Author: alphaleonis

byalphaleonis

0•

Productividad y Flujo de Trabajo

Decomposes project phases and epics into implementable features with clear acceptance criteria and vertical slices.

The Breakdown Phase skill streamlines the transition from high-level project planning to implementation by systematically decomposing epics or plan phases into independently reviewable features. It analyzes the current state of your codebase to ensure technical feasibility, drafts features focused on vertical slices, and automatically generates work items in platforms like GitHub, Azure DevOps, or Markdown. By establishing clear acceptance criteria and identifying dependencies upfront, it helps developers maintain momentum and ensures that each unit of work delivers tangible value.

Características Principales

01Automated codebase exploration to verify current technical state

02Focuses on vertical slices for end-to-end functionality

03Maintains project hierarchy by linking features to parent phases

04Generates work items for GitHub, Azure DevOps, Beans, or Markdown

050 GitHub stars

06Decomposes epics into 1-3 hour implementable features

Casos de Uso

01Updating project plans with specific acceptance criteria before starting code

02Splitting a complex project epic into manageable PR-sized tasks

03Translating high-level roadmap phases into detailed developer work items

Características Principales

01Automated codebase exploration to verify current technical state

02Focuses on vertical slices for end-to-end functionality

03Maintains project hierarchy by linking features to parent phases

04Generates work items for GitHub, Azure DevOps, Beans, or Markdown

050 GitHub stars

06Decomposes epics into 1-3 hour implementable features

Casos de Uso

01Updating project plans with specific acceptance criteria before starting code

02Splitting a complex project epic into manageable PR-sized tasks

03Translating high-level roadmap phases into detailed developer work items