planning

Coordinate discovery, synthesis, spike verification, and bead-based decomposition for feature planning.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mthangtr/groaly --skill planning-mthangtr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/mthangtr/groaly/tree/main/.claude/skills/planning
Command: npx skills add https://github.com/mthangtr/groaly --skill planning-mthangtr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex features is often manual and error-prone. This skill automates end-to-end feature planning by guiding discovery, synthesis, spike verification, bead-based decomposition, and track planning.

Core Features & Use Cases

  • Discovery-driven planning: gather context from the codebase to inform roadmaps.
  • Synthesis, validation, and risk assessment: propose approaches, assess tradeoffs, and validate with spikes.
  • Bead-based decomposition: break work into executable beads with clear acceptance criteria and dependencies, and generate an execution plan.

Quick Start

Plan a feature end-to-end by running through discovery, synthesis, spikes, beads, and execution planning.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I plan a feature end-to-end from codebase discovery to execution?

Feature planning involves structured phases: gathering codebase context during discovery, synthesizing approaches, verifying with spikes, and decomposing work into executable beads. This generates concrete roadmaps with artifacts like discovery.md and execution plans.

What is bead-based decomposition for engineering roadmaps?

Bead-based decomposition breaks feature work into executable units with clear acceptance criteria and dependencies. It translates synthesized approaches and validated spikes into an actionable execution plan for engineering tasks.

How do I validate technical approaches and assess risks before committing to a feature roadmap?

Approach validation uses spike verification to test proposed solutions against codebase realities. Risk assessment occurs during the synthesis phase, evaluating tradeoffs before finalizing the decomposition and track planning artifacts.

Can I use this structured discovery process for migrations and refactors, not just new features?

Structured discovery applies to product initiatives and engineering roadmap tasks across codebases. It enables concrete roadmaps for new features, migrations, or refactors by coordinating synthesis, spike verification, and bead decomposition.

What artifacts are generated during the feature planning workflow?

The workflow outputs discovery.md for context, approach.md for synthesized strategies, spike results for verification, beads for decomposed tasks, and a final execution plan to guide track planning and implementation.

What's the best way to structure feature discovery and synthesis for complex codebases?

Structured discovery gathers codebase context to inform roadmaps, followed by synthesis to propose approaches and assess tradeoffs. This multi-phase workflow enforces validation through spikes before generating an execution plan.