Story Craftsman

This skill embodies the "Everything is Code" engineering philosophy, helping you produce high-quality user stories and their supporting documentation alongside your MR submissions.

For the detailed example template, see examples/TEMPLATE-UserStory.md.

Rules

1. Never fabricate information: When information is insufficient, obtain context through guided interviews rather than filling in details yourself
2. Architecture-aware placement: Analyze file paths or git status to determine the relevant module and place documents in the corresponding docs/04-user-stories/ directory
3. Testable acceptance criteria: Each AC must be a verifiable, checkable condition (Given/When/Then or clear checkbox)
4. Consolidate questions: During interviews, combine all missing dimensions into a single round of questions to avoid multi-round fragmented asking that causes user fatigue
5. Path-first inference: First attempt to infer the target sub-module from context; only ask the user when uncertain

Execution Flow