メニュー
Turn a feature or epic into a prioritized, estimated, INVEST-compliant user-story backlog in the tracker. Use when the user wants to create, split, estimate, or prioritize user stories. Not for source code or a PRD.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Initialize or refresh the project memory bank. Use when the user wants to set up or regenerate the project's memory files. Not for updating one memory file after it exists or editing a single rule directly.
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.
Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.
Generate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.
| name | 02-user-stories |
| description | Turn a feature or epic into a prioritized, estimated, INVEST-compliant user-story backlog in the tracker. Use when the user wants to create, split, estimate, or prioritize user stories. Not for source code or a PRD. |
| argument-hint | clarify-scope | split-epic | draft-stories | estimate-impact | prioritize | sync-tracker |
Produces a prioritized backlog of INVEST-compliant user stories, each estimated for effort and impact and carrying a pragmatic functional Definition of Done, then saved to the project's configured tracker.
| # | Action | Role | Input |
|---|---|---|---|
| 01 | clarify-scope | Clarify the request through Product Owner questioning; decide epic vs single story | feature or epic description |
| 02 | split-epic | Decompose the confirmed scope into candidate vertical-slice stories | confirmed scope from 01 |
| 03 | draft-stories | Write each candidate as an INVEST story with acceptance criteria and a functional DoD | candidate stories from 02 |
| 04 | estimate-impact | Rate each story for effort (points) and impact on the existing system | drafted stories from 03 |
| 05 | prioritize | Rank the backlog by value against effort and impact | estimated stories from 04 |
| 06 | sync-tracker | Gate on Definition of Ready, get explicit approval, save to the tracker | ranked backlog from 05 |
Run 01 → 02 → 03 → 04 → 05 → 06, passing each ## Test first. A single story skips the epic split.
Before running an action, read its file in actions/, not only the table or assets.
references/rating.md: INVEST, the Definition of Ready and functional Definition of Done, the minor/major/critic impact scale, and the prioritization method.assets/user-story-template.md: user story body template.