planning

Formalize a feature plan from discovery to execution tracks.

225|71|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/hoangnb24/skills --skill planning-hoangnb24
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/hoangnb24/skills/tree/main/.agents/skills/planning
Command: npx skills add https://github.com/hoangnb24/skills --skill planning-hoangnb24

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Planning pipeline helps teams convert vague feature ideas into concrete, actionable roadmaps by coordinating discovery, synthesis, risk assessment, and bead-based decomposition.

Core Features & Use Cases

  • Discovery and architecture snapshot to identify existing patterns and constraints.
  • Synthesis and gap analysis to propose approaches and risk mitigation.
  • Bead-based decomposition to create executable tracks and dependencies for delivery.
  • Use Case: When asked to plan a feature, generate a complete execution plan with tracks and beads.

Quick Start

Provide a complete feature plan by running discovery, synthesis, spike planning, and bead decomposition for the requested feature.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I turn a vague feature idea into a structured execution plan?

To turn a vague idea into an execution plan, the pipeline runs discovery to identify constraints, synthesis for gap analysis, and bead-based decomposition to create actionable delivery tracks.

What is bead-based decomposition for feature planning?

Bead-based decomposition in feature planning breaks down proposed approaches into executable tracks and dependencies, allowing teams to coordinate delivery from synthesis directly into actionable development tasks.

How do I create a feature roadmap that includes risk assessment?

Creating a feature roadmap with risk assessment involves running synthesis and gap analysis to propose approaches, followed by structured risk mitigation steps before executing bead-based decomposition.

What's the best way to plan software delivery tracks from initial discovery?

The best way to plan delivery tracks is applying a coordinated pipeline: discovery for architecture snapshots, synthesis for approach proposals, and bead decomposition to map dependencies and execution.

Does this feature planning approach work without pre-existing architecture documentation?

Yes, the feature planning workflow includes an initial discovery phase designed to identify existing patterns and constraints, effectively generating an architecture snapshot if formal documentation is missing.

When should I not use bead decomposition for roadmap planning?

You should avoid bead decomposition for roadmap planning when a feature idea remains completely unvalidated, as the pipeline requires sufficient discovery and synthesis inputs to formalize meaningful execution tracks.