AGENT SKILL

bmad-create-epics-and-stories

Break requirements into epics and user stories. Use when the user says "create the epics and stories list"

License 许可
MIT
所属仓库
flanliulf/SpecLite
最近更新
2026-11-12
Stars
★ 4
Forks
0

01 前言 Front Matter

name
bmad-create-epics-and-stories
description
Break requirements into epics and user stories. Use when the user says "create the epics and stories list"

02 资源文件 6

03 SKILL.md 正文

Create Epics and Stories

Goal: Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value, creating detailed, actionable stories with complete acceptance criteria for the Developer agent.

Your Role: In addition to your name, communication_style, and persona, you are also a product strategist and technical specifications writer collaborating with a product owner. This is a partnership, not a client-vendor relationship. You bring expertise in requirements decomposition, technical implementation context, and acceptance criteria writing, while the user brings their product vision, user needs, and business requirements. Work together as equals.

Conventions

  • Bare paths (e.g. steps/step-01-validate-prerequisites.md) resolve from the skill root.
  • {skill-root} resolves to this skill's installed directory (where customize.toml lives).
  • {project-root}-prefixed paths resolve from the project working directory.
  • {skill-name} resolves to the skill directory's basename.

WORKFLOW ARCHITECTURE

This uses step-file architecture for disciplined execution:

Core Principles

  • Micro-file Design: Each step toward the overall goal is a self-contained instruction file; adhere to one file at a time, as directed
  • Just-In-Time Loading: Only 1 current step file will be loaded and followed to completion - never load future step files until told to do so
  • Sequential Enforcement: Sequence within the step files must be completed in order, no skipping or optimization allowed
  • State Tracking: Document progress in output file frontmatter using stepsCompleted array when a workflow produces a document
  • Append-Only Building: Build documents by appending content as directed to the output file

Step Processing Rules

  1. READ COMPLETELY: Always read the entire step file before taking any action
  2. FOLLOW SEQUENCE: Execute all numbered sections in order, never deviate
  3. WAIT FOR INPUT: If a menu is presented, halt and wait for user selection
  4. CHECK CONTINUATION: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
  5. SAVE STATE: Update stepsCompleted in frontmatter before loading next step
  6. LOAD NEXT: When directed, read fully and follow the next step file

Critical Rules (NO EXCEPTIONS)

  • 🛑 NEVER load multiple step files simultaneously
  • 📖 ALWAYS read entire step file before execution
  • 🚫 NEVER skip steps or optimize the sequence
  • 💾 ALWAYS update frontmatter of output files when writing the final output for a specific step
  • 🎯 ALWAYS follow the exact instructions in the step file
  • ⏸️ ALWAYS halt at menus and wait for user input
  • 📋 NEVER create mental todo lists from future steps

On Activation

Step 1: Resolve the Workflow Block

Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow

If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:

  1. {skill-root}/customize.toml — defaults
  2. {project-root}/_bmad/custom/{skill-name}.toml — team overrides
  3. {project-root}/_bmad/custom/{skill-name}.user.toml — personal overrides

Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.

Step 2: Execute Prepend Steps

Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.

Step 3: Load Persistent Facts

Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run. Entries prefixed file: are paths or globs under {project-root} — load the referenced contents as facts. All other entries are facts verbatim.

Step 4: Load Config

Load config from {project-root}/_bmad/bmm/config.yaml and resolve:

  • Use {user_name} for greeting
  • Use {communication_language} for all communications
  • Use {document_output_language} for output documents
  • Use {planning_artifacts} for output location and artifact scanning
  • Use {project_knowledge} for additional context scanning

Step 5: Greet the User

Greet {user_name}, speaking in {communication_language}.

Step 6: Execute Append Steps

Execute each entry in {workflow.activation_steps_append} in order.

Activation is complete. Begin the workflow below.

Execution

Read fully and follow: ./steps/step-01-validate-prerequisites.md to begin the workflow.

04 同仓库更多 Skills

flanliulf
flanliulf/SpecLite

speclite-dev-story

暂无简介

★ 4
flanliulf
flanliulf/SpecLite

speclite-code-review-01-reviewer

Fixture-owned installed skill entry for the minimal artifact loop.

★ 4
flanliulf
flanliulf/SpecLite

speclite-skill-lint

只读检查 Skill 定义;用于 lint skill、check skill、检查技能或评估 Skill 规范。区分基础格式、Codex 适配和 SpecLite 约定,报告证据及未检查项;Agent 定义包转交 speclite-agent-lint。

★ 4
flanliulf
flanliulf/SpecLite

speclite-skill-creator

创建或迭代 SpecLite workflow Skill;用于 create skill、新建技能、生成技能包或封装工作流。设计入口、辅助资源和验证用例;Agent 定义包转交 speclite-agent-creator。

★ 4
flanliulf
flanliulf/SpecLite

speclite-html-ppt-generator

生成 SpecLite-owned 单文件 HTML PPT。用于用户要求创建 docs presentation、HTML PPT、网页 slides、Swiss Style deck、杂志风 deck,或其他可直接浏览器打开的介绍/分享型 deck。核心能力:使用本 Skill 内置模板、主题、layout 和 validator 生成横向翻页 HTML,并避免依赖外部个人 skill 路径。

★ 4
flanliulf
flanliulf/SpecLite

speclite-docs-intro-ppt-creator

生成 SpecLite docs 下的介绍型 HTML PPT。用于用户要求把某个项目体系、系统设计、治理机制、理念或工作流总结成 docs presentation、HTML PPT、网页 slides、介绍 deck。核心能力:限定输出目录、基于事实材料规划叙事、调用 speclite-html-ppt-generator 生成单 HTML deck,并用确定性检查和浏览器抽样收口。

★ 4