plan

Decompose software requirements into epics and dependency-tracked stories.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/firefly-events/plugin-hive --skill plan-firefly-events
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/firefly-events/plugin-hive/tree/main/skills/plan
Command: npx skills add https://github.com/firefly-events/plugin-hive --skill plan-firefly-events

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Decompose complex software requirements into epics and dependency-tracked stories to enable structured, auditable planning across multiple teams.

Core Features & Use Cases

  • Phase-driven planning: Research, design discussion, HV (horizontal/vertical) planning, and story decomposition are orchestrated as a unified workflow.
  • Cross-functional coordination: Coordinates researchers, writers, TPMs, architects, and developers through a shared planning narrative.
  • Traceable artifacts: Produces research briefs, design discussions, HV plans, and canonical story YAMLs that map to an epic.
  • Memory and references loading: Loads relevant memories and reference material to inform decisions and ensure consistency.
  • Gates and reviews: Supports collaborative review gates and escalation handling to align with governance.

Quick Start

Provide a requirement description and let plan orchestrate research, design, HV planning, and story decomposition.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I decompose complex software requirements into epics and dependency-tracked stories?

Decomposing software requirements into epics and dependency-tracked stories involves orchestrating research, design discussions, HV planning, and story decomposition to produce traceable artifacts like canonical story YAMLs mapped to an epic.

What is the best way to coordinate cross-functional planning for medium and large software projects?

Cross-functional planning for medium and large projects is coordinated through a shared planning narrative that aligns researchers, writers, TPMs, architects, and developers using collaborative review gates and escalation handling.

When do I need phase-driven planning for research, design discussion, and HV planning?

You need phase-driven planning when managing medium and large projects that require structured, auditable planning across multiple teams, utilizing research briefs, design discussions, and HV plans to ensure cross-functional alignment.

Can I load existing memories and reference material to inform software story decomposition?

Yes, you can load existing memories and reference material to inform software story decomposition, ensuring consistency and context-aware decisions throughout the research, design discussion, and HV planning phases.

Does this software planning workflow support collaborative review gates and escalation handling?

Yes, the software planning workflow supports collaborative review gates and escalation handling to align planning artifacts with governance and ensure structured, auditable coordination across cross-functional teams.

What traceable artifacts are produced during end-to-end software requirement decomposition?

End-to-end software requirement decomposition produces traceable artifacts including a research brief, design discussion, HV plan, and ready-to-implement canonical story YAMLs that map directly to an epic.