beo-planning

Convert CONTEXT.md and discovery results into plan.md, phase-contract.md, story-map.md, and task beads.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/minhtri2710/skills --skill beo-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beo-planning
Source: https://github.com/minhtri2710/skills/tree/main/skills/beo/planning
Command: npx skills add https://github.com/minhtri2710/skills --skill beo-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning and decomposition of feature work by converting CONTEXT.md and discovery outputs into a structured sequence of artifacts (discovery.md, plan.md, phase-contract.md, story-map.md) and bead-ready task definitions with dependencies, enabling disciplined execution.

Core Features & Use Cases

  • End-to-end planning lifecycle: discovery, planning, phase-contract, story-mapping and bead creation.
  • Ensures traceability from decisions to executable beads with explicit dependencies and artifacts.
  • Enables repeatable planning cadence for beo pipelines in collaborative contexts.

Quick Start

Review CONTEXT.md, write discovery.md, plan.md, phase-contract.md, and story-map.md, then create and wire beads.

Frequently Asked Questions about beo-planning

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

FAQPage Schema
How do I decompose feature work into structured execution plans?

Feature decomposition converts contextual inputs and discovery results into a structured sequence of artifacts including plan.md, phase-contract.md, and story-map.md, enabling disciplined execution through traceable task beads with explicit dependencies.

What is the best way to create a story map from product discovery outputs?

Creating a story map from discovery outputs involves translating stakeholder goals and contextual inputs into phase contracts and structured story-map.md files, ensuring traceability from initial decisions down to executable bead descriptions.

How do I structure phase contracts for early product development?

Structuring phase contracts requires reviewing CONTEXT.md and discovery results to define a structured sequence of artifacts, translating stakeholder goals into clear tasks, risks, and dependencies for each execution phase.

Can I use CONTEXT.md to generate task beads with dependencies?

CONTEXT.md serves as the primary input for generating bead-ready task definitions, allowing you to convert contextual inputs and stakeholder goals into executable beads wired with clear dependencies and associated risks.

What artifacts do I need for a complete planning lifecycle in product development?

A complete planning lifecycle requires producing discovery.md, plan.md, phase-contract.md, and story-map.md, followed by creating and wiring task beads to ensure repeatable planning cadence and full traceability.

How do I maintain traceability from planning decisions to executable tasks?

Traceability is maintained by converting contextual inputs into a structured artifact sequence, ensuring every decision in plan.md and phase-contract.md maps directly to story-map.md and executable bead descriptions with dependencies.