SKILL.md

name: defining-stories description: Create user stories and epic design documents. Use when defining new features, writing Given-When-Then criteria, creating story logs, or designing larger features.

Defining Stories

Epic vs Story

Document	Purpose	When to Create
Epic	Design document defining scope and technical approach	Starting a larger feature
Story	Incremental deliverable with acceptance criteria	As needed during development

Agile approach: Stories emerge during development. Create each story when ready to implement.

User Story Format

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

Acceptance Criteria

- [ ] **Given** [precondition], **When** you [action], **Then** [expected result]

Focus on user-observable behavior
Include happy paths AND error cases
Leave checkboxes unchecked (PO checks them)

Verification Approach

Define how criteria will be verified:

Project Type	Options
CLI	Direct command execution
API	curl/httpie, API testing tools
Web UI	E2E tests, browser MCP tools
Mobile	Device/emulator, MCP tools
Library	Unit/integration tests

If MCP tools or skills for testing are available, use them. If unsure, ask PO.

Story Log

File: docs/stories/<YYYYMMDDTHHMMSS>_<name>.story.md

date -u +"%Y%m%dT%H%M%S"  # Generate timestamp

Use the story-template skill for structure.

Epic Documents

Directory: docs/stories/<YYYYMMDD>_<epic-name>/ File: <YYYYMMDDTHHMMSS>_<epic-name>.epic.md

Use the epic-template skill for structure.

スコア

総合スコア

60/100

リポジトリの品質指標に基づく評価

✓SKILL.md

SKILL.mdファイルが含まれている

+20

✓LICENSE

ライセンスが設定されている

+10

○説明文

100文字以上の説明がある

0/10

○人気

GitHub Stars 100以上

0/15

○最近の活動

3ヶ月以内に更新がある

0/10

○フォーク

10回以上フォークされている

0/5

✓Issue管理

オープンIssueが50未満

✓言語

プログラミング言語が設定されている

○タグ

1つ以上のタグが設定されている

0/5

defining-stories