gxpm-planning

Break plans into traceable vertical slices with dependencies and acceptance criteria.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/laozhong86/gxpm --skill gxpm-planning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gxpm-planning
Source: https://github.com/laozhong86/gxpm/tree/main/skills/gxpm-planning
Command: npx skills add https://github.com/laozhong86/gxpm --skill gxpm-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning at scale often stalls in ambiguous plans; gxpm-planning provides a disciplined method to break strategy into traceable, independently-creatable vertical slices.

Core Features & Use Cases

  • Breaks plans into independently-grabbable issues using tracer-bullet vertical slices.
  • Converts discussions into structured PRDs and implementation tickets.
  • Helps manage dependencies and ensure end-to-end coverage across schema, API, UI, and tests.

Quick Start

Draft vertical-slice tickets from an existing plan by outlining end-to-end slices with dependencies.

Frequently Asked Questions about gxpm-planning

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

FAQPage Schema
How do I break down an ambiguous product plan into actionable issue tickets?▼

Plan decomposition reduces ambiguity by breaking strategy into traceable, implementation-ready vertical slices. It converts discussions into structured PRDs and independently-grabbable issues with explicit dependencies.

What is the best way to create implementation tickets with end-to-end vertical slices?▼

Creating implementation tickets with vertical slices involves outlining end-to-end slices that ensure coverage across schema, API, UI, and tests. This method applies tracer-bullet slicing to enforce testable acceptance criteria.

Can I convert unstructured project discussions into structured PRDs for issue tracking?▼

Yes, you can convert discussions into structured PRDs by applying disciplined plan decomposition. This process transforms conversations into traceable, implementation-ready tickets within planning and triage contexts.

Does vertical slice planning help manage dependencies across schema, API, and UI layers?▼

Vertical slice planning helps manage dependencies by enforcing end-to-end slicing across schema, API, UI, and tests. It ensures explicit dependency tracking and testable acceptance criteria for each slice.

When should I use tracer-bullet vertical slices for product management planning?▼

Use tracer-bullet vertical slices when turning ambiguous plans into issues or creating implementation tickets. This approach ensures independently-creatable slices with end-to-end coverage and explicit dependencies.

Plan decomposition is not working for complex architecture, what are the limitations?▼

Plan decomposition requires existing plans to function effectively and may stall if the initial strategy lacks clarity. It enforces end-to-end vertical slicing, which might be rigid for architecture contexts needing isolated layer changes.