skills.rest
prestarius
prestariusCOMMUNITY
Explore all skills by this author →
GitHub

epic-numbering

Apply standardized numbering scheme to Epics, User Stories, and Tasks in planning documents.

1|Updated Jun 9, 2026
Search Tags:#planning#epics#agile#backlog#user-stories#numbering
One-click install
npx skills add https://github.com/prestarius/jet-skills-stack --skill epic-numbering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epic-numbering
Source: https://github.com/prestarius/jet-skills-stack/tree/main/skills/epic-numbering
Command: npx skills add https://github.com/prestarius/jet-skills-stack --skill epic-numbering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Numbering Epics, User Stories, and Tasks helps teams maintain clear hierarchy, stable IDs, and traceability across planning and changes.

Core Features & Use Cases

  • Stable ID scheme for Epics, User Stories, and Tasks, enabling easy tracking across releases.
  • Safe reordering without renumbering existing items, preserving historical context and references.
  • Applicable to backlogs, roadmaps, sprint plans, and release plans to maintain consistency during restructuring.

Quick Start

Use the epic-numbering convention to label Epics as Epic 1 — <name>, User Stories as US 1.1 — <name>, and Tasks as 1.1.1 — <name>, and keep IDs stable when reordering.

Frequently Asked Questions about epic-numbering

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

FAQPage Schema
How do I keep epic numbering stable when reordering items in an agile backlog?▼

Stable epic numbering is maintained by applying a standardized ID scheme that prevents renumbering existing items during reordering, preserving historical context and traceability across releases.

What is the best way to number epics, user stories, and tasks in a project backlog?▼

The best way to number backlog items is using a hierarchical convention: Epic 1, User Stories as US 1.1, and Tasks as 1.1.1, ensuring consistent naming and clear hierarchy across roadmaps and sprint plans.

Why does reordering my agile backlog renumber existing user stories and break references?▼

Reordering breaks references when a numbering scheme dynamically updates IDs based on list position. Applying stable IDs that persist during restructuring prevents this issue and obscures historical context.

Can I apply a standardized epic-numbering scheme to both sprint plans and release roadmaps?▼

Yes, a standardized epic-numbering scheme is applicable to backlogs, roadmaps, sprint plans, and release plans, enabling consistent naming and traceability across all agile planning and restructuring efforts.

Do I need any specific agile tools or dependencies to start using an epic-numbering convention?▼

No specific tools or dependencies are required to start using the epic-numbering convention. You can label Epics, User Stories, and Tasks using the hierarchical naming format directly in your existing planning environment.

When should I not use a fixed numbering scheme for my project backlog?▼

You should avoid a fixed numbering scheme if your agile team frequently restructures the entire backlog hierarchy and does not require stable IDs for historical tracking across releases.

Related Skills

Explore More Product & Management Skills→
bbolek-apbbolek-ap

create-work-breakdown

Generate and extend backlog files under .project/backlog/ using canonical WBS templates.

Community
Advanced
omeraltnomeraltn

agency-sprint-prioritizer

Prioritize product backlog items using RICE and value-effort scoring.

Community
Advanced
LucaDeLeoLucaDeLeo
1

bmad-bmm-sprint-planning

Derive a sprint plan from project epics and generate a sprint backlog.

Community
Advanced
thomasholknielsenthomasholknielsen
6

azure-devops

Configure Azure DevOps work items, pipelines, and branch policies.

Community
Advanced