[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M757PTHT2DM3KVNFPZTSRW3D":3,"skill-same:01M757PTHT2DM3KVNFPZTSRW3D":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M757PTHT2DM3KVNFPZTSRW3D","bmad-create-epics-and-stories",null,"Break requirements into epics and user stories. Use when the user says \"create the epics and stories list\"","SevWren\u002FDaily-Motivation-Brain-Helper","SevWren","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4411791?v=4","01M757KRED8NN6CAZAHKC73C6K","01M757KRFHMA61WJTBVGCAPXS0",1,"MIT","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-create-epics-and-stories\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: bmad-create-epics-and-stories\ndescription: 'Break requirements into epics and user stories. Use when the user says \"create the epics and stories list\"'\n---\n\n# Create Epics and Stories\n\n**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.\n\n**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.\n\n## Conventions\n\n- Bare paths (e.g. `steps\u002Fstep-01-validate-prerequisites.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## WORKFLOW ARCHITECTURE\n\nThis uses **step-file architecture** for disciplined execution:\n\n### Core Principles\n\n- **Micro-file Design**: Each step toward the overall goal is a self-contained instruction file; adhere to one file at a time, as directed\n- **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\n- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed\n- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document\n- **Append-Only Building**: Build documents by appending content as directed to the output file\n\n### Step Processing Rules\n\n1. **READ COMPLETELY**: Always read the entire step file before taking any action\n2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate\n3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection\n4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)\n5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step\n6. **LOAD NEXT**: When directed, read fully and follow the next step file\n\n### Critical Rules (NO EXCEPTIONS)\n\n- 🛑 **NEVER** load multiple step files simultaneously\n- 📖 **ALWAYS** read entire step file before execution\n- 🚫 **NEVER** skip steps or optimize the sequence\n- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step\n- 🎯 **ALWAYS** follow the exact instructions in the step file\n- ⏸️ **ALWAYS** halt at menus and wait for user input\n- 📋 **NEVER** create mental todo lists from future steps\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `uv run {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**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:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny 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.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat 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.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` and resolve:\n- Use `{user_name}` for greeting\n- Use `{communication_language}` for all communications\n- Use `{document_output_language}` for output documents\n- Use `{planning_artifacts}` for output location and artifact scanning\n- Use `{project_knowledge}` for additional context scanning\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.\n\n## Execution\n\nRead fully and follow: `.\u002Fsteps\u002Fstep-01-validate-prerequisites.md` to begin the workflow.\n","# Create Epics and Stories\n\n**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.\n\n**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.\n\n## Conventions\n\n- Bare paths (e.g. `steps\u002Fstep-01-validate-prerequisites.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## WORKFLOW ARCHITECTURE\n\nThis uses **step-file architecture** for disciplined execution:\n\n### Core Principles\n\n- **Micro-file Design**: Each step toward the overall goal is a self-contained instruction file; adhere to one file at a time, as directed\n- **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\n- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed\n- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document\n- **Append-Only Building**: Build documents by appending content as directed to the output file\n\n### Step Processing Rules\n\n1. **READ COMPLETELY**: Always read the entire step file before taking any action\n2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate\n3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection\n4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)\n5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step\n6. **LOAD NEXT**: When directed, read fully and follow the next step file\n\n### Critical Rules (NO EXCEPTIONS)\n\n- 🛑 **NEVER** load multiple step files simultaneously\n- 📖 **ALWAYS** read entire step file before execution\n- 🚫 **NEVER** skip steps or optimize the sequence\n- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step\n- 🎯 **ALWAYS** follow the exact instructions in the step file\n- ⏸️ **ALWAYS** halt at menus and wait for user input\n- 📋 **NEVER** create mental todo lists from future steps\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `uv run {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**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:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny 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.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat 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.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` and resolve:\n- Use `{user_name}` for greeting\n- Use `{communication_language}` for all communications\n- Use `{document_output_language}` for output documents\n- Use `{planning_artifacts}` for output location and artifact scanning\n- Use `{project_knowledge}` for additional context scanning\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.\n\n## Execution\n\nRead fully and follow: `.\u002Fsteps\u002Fstep-01-validate-prerequisites.md` to begin the workflow.\n",{"name":5,"description":7},"main","b469548b8e522c5d7fbf5e126591af14e0dc3744",".claude\u002Fskills\u002Fbmad-create-epics-and-stories",0,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper","https:\u002F\u002Fgithub.com\u002FSevWren","Mindset:  Improving yourself one day at a time -> made possible by utilizing today's technologies to fit your individual needs.","2026-10-25 09:39:17",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add SevWren\u002FDaily-Motivation-Brain-Helper --skill bmad-create-epics-and-stories",{"tool":37,"command":38},"bunx","bunx skills add SevWren\u002FDaily-Motivation-Brain-Helper --skill bmad-create-epics-and-stories",{"tool":40,"command":41},"pnpm","pnpm dlx skills add SevWren\u002FDaily-Motivation-Brain-Helper --skill bmad-create-epics-and-stories","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-create-epics-and-stories\u002FSKILL.md",true,[45,51,57,61,65,69],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"customize.toml","OTHER","其他",1665,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-create-epics-and-stories\u002Fcustomize.toml",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"steps\u002Fstep-01-validate-prerequisites.md","REFERENCE","参考文档",10960,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-create-epics-and-stories\u002Fsteps\u002Fstep-01-validate-prerequisites.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"steps\u002Fstep-02-design-epics.md",8809,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-create-epics-and-stories\u002Fsteps\u002Fstep-02-design-epics.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"steps\u002Fstep-03-create-stories.md",8351,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-create-epics-and-stories\u002Fsteps\u002Fstep-03-create-stories.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"steps\u002Fstep-04-final-validation.md",5324,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-create-epics-and-stories\u002Fsteps\u002Fstep-04-final-validation.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"templates\u002Fepics-template.md",1105,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-create-epics-and-stories\u002Ftemplates\u002Fepics-template.md",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M757YEXC4V515X48TR4A7FW3","repo-doc-audit","Performs a comprehensive Repository Documentation Audit and Governance Standard (RDAGS) against an entire codebase. Use this skill whenever the user wants to audit, evaluate, or assess repository documentation — including requests like \"audit my repo docs\", \"find doc inconsistencies\", \"check for documentation drift\", \"governance review\", \"find dead or orphan knowledge\", \"check my CLAUDE.md or AGENTS.md for accuracy\", or any systematic documentation quality evaluation. Always trigger this skill when the user asks to run a documentation audit or governance review, even if they describe only part of the standard (e.g., \"check traceability\" or \"find contradictions in my docs\"). Produces five output files: Repository-Audit-Report.md (full 18-section report) plus Direct-Contradictions.md, Semantic-Contradictions.md, Traceability-Failures.md, and Proposed-Repository-Governance-Improvements.md as standalone action-oriented findings documents.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Frepo-doc-audit\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M757YCKK0QMK7JRZFPMXTGN4","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fwriting-great-skills\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M757Y8AM0HGTW50KFG5MWCRD","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fwrite-a-skill\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M757Y5RN0J4Y7XQQKSR8Z7D3","teach","Teach the user a new skill or concept, within this workspace.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fteach\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M757Y0R3DYWN3D07TKJWXDMD","self-reflect","Enterprise-grade forensic self-reflection over recent git history. Multi-axis audit with pass\u002Ffail gates, mandate compliance matrix, platform drift forensics, test quality review, and ranked generation constraints.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fself-reflect\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":18},"01M757XYVBYVHJPP46YNDQGJER","handoff","Compact the current conversation into a handoff document for another agent to pick up.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fhandoff\u002FSKILL.md",[],[]]