flpbalada/fb-skills

theme-epic-story

Structure product work from strategic themes to epics, stories, and tasks.

First seen May 4, 2026

Installation

$ npx skills add flpbalada/fb-skills --skill theme-epic-story

Summary

  • Structure product work from strategic themes to epics, stories, and tasks.
  • Use when organizing backlogs, roadmaps, releases, stakeholder communication, or large initiatives into outcome-linked delivery units; avoid for writing one story only, requirements analysis, or effort estimates.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from flpbalada/fb-skills · top by installs.

npx skills add flpbalada/fb-skills

Browse all from flpbalada/fb-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 7
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,917 B
  • docs SUMMARY.md 310 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 10 installs

SKILL.md

Theme, Epic, Story

Goal

Structure work from strategy to execution. Keep user value separate from implementation tasks.

Hierarchy

  • Theme: strategic outcome. Why this matters.
  • Epic: major capability. What area changes.
  • Story: user need. What value is delivered.
  • Task: implementation work. How to build it.

Rules

  • Themes need measurable outcomes.
  • Epics must fit inside a planning horizon.
  • Stories must be user-centered and testable.
  • Tasks belong under stories, not beside themes.
  • Split oversized epics by workflow, role, data lifecycle, platform, or release slice.
  • Split oversized stories until they fit one sprint.
  • Keep non-goals explicit.

Flow

  1. Define theme goal and success metric.
  2. List epics needed to reach the goal.
  3. Define each epic scope and out-of-scope.
  4. Break each epic into stories.
  5. Add acceptance criteria to each story.
  6. Identify dependencies.
  7. Mark MVP vs later work.

Story Format

As a [user type],
I want [capability],
so that [benefit].

INVEST Check

  • Independent.
  • Negotiable.
  • Valuable.
  • Estimable.
  • Small.
  • Testable.

Resources

Output

## Theme
- Name:
- Goal:
- Success metrics:

## Epics
- [epic]: scope, out-of-scope, dependencies

## Release
- MVP:
- Later:
- Non-goals: