theme-epic-story

Structure product work into Theme, Epic, and Story hierarchies.

23|4|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/flpbalada/thinking-toolkit --skill theme-epic-story
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: theme-epic-story
Source: https://github.com/flpbalada/thinking-toolkit/tree/main/plugins/theme-epic-story/skills/theme-epic-story
Command: npx skills add https://github.com/flpbalada/thinking-toolkit --skill theme-epic-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizes large product initiatives by structuring work into Theme, Epic, and Story, enabling clearer planning, prioritization, and stakeholder alignment.

Core Features & Use Cases

  • Hierarchical structure: Theme (strategic) → Epic (tactical) → Story (operational) to align work across levels.
  • Backlog & roadmap clarity: Helps teams plan releases, allocate scope, and communicate progress to stakeholders.
  • INVEST-aligned Stories: Provides guidance to craft small, valuable, testable work items with clear acceptance criteria.
  • Collaboration & governance: Enables cross-team coordination with common terminology and alignment on goals.
  • Use Case Example: For a large product initiative, define Theme "Improve onboarding," Epics such as "Authentication Flow" and "Tutorials," and multiple Stories detailing specific tasks.

Quick Start

Identify your strategic Theme, then define Epics that support it, and break Epics into Stories. Create Theme objectives and key results, add Epics with clear objectives, and fill Stories with actionable acceptance criteria. Use this structure to populate your backlog and roadmap in your PM tool.

Frequently Asked Questions about theme-epic-story

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

FAQPage Schema
How do I structure my product backlog using theme, epic, and story hierarchy?

To structure a product backlog with theme, epic, and story hierarchy, define strategic Themes first, break them into tactical Epics, and split Epics into operational Stories. This aligns work across levels to improve planning, prioritization, and stakeholder alignment.

What is the best way to organize large product initiatives for roadmap planning?

The best way to organize large product initiatives for roadmap planning is applying a hierarchical structure. Grouping work into Themes, Epics, and Stories helps allocate scope, plan releases, and communicate progress clearly to stakeholders.

How do I write INVEST-aligned user stories for backlog grooming?

To write INVEST-aligned user stories for backlog grooming, break down Epics into small, valuable, testable work items. Fill each Story with actionable acceptance criteria to ensure they meet INVEST principles for clear operational execution.

Can I use this theme-epic-story structure for cross-team collaboration?

Yes, you can use the theme-epic-story structure for cross-team collaboration. It establishes common terminology and aligns goals across teams, enabling better coordination and governance across large product initiatives.

How does defining a theme differ from creating an epic in product management?

Defining a Theme differs from creating an Epic because Themes represent strategic objectives, while Epics are tactical initiatives supporting those objectives. Breaking Epics into operational Stories ensures work aligns with top-level strategic goals.

When do I need to use a hierarchical breakdown for my product roadmap?

You need to use a hierarchical breakdown for your product roadmap when managing large initiatives that require clear planning, prioritization, and stakeholder alignment. Structuring work from strategic Themes down to operational Stories clarifies scope and progress.