skills.rest
Nathanto-ai
Nathanto-aiCOMMUNITY
Explore all skills by this author →
GitHub

user-story-writing

Convert vague requirements into SMARC-compliant user stories with acceptance criteria.

Updated Mar 5, 2026
Search Tags:#requirements#traceability#acceptance-criteria#user-story#story-writing#smarc
One-click install
npx skills add https://github.com/Nathanto-ai/liza-private --skill user-story-writing-nathanto-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-story-writing
Source: https://github.com/Nathanto-ai/liza-private/tree/main/skills/user-story-writing
Command: npx skills add https://github.com/Nathanto-ai/liza-private --skill user-story-writing-nathanto-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Writing precise, testable user stories from vague requirements is error-prone and time-consuming. This skill provides a disciplined template to convert inputs into SMARC-compliant stories that guide developers and QA.

Core Features & Use Cases

  • Canonical story format: As a <persona>, I want to <action>, so that <outcome>, with traceability to source material.
  • Reference-driven drafting: Uses provided references (e.g., references/user-story-format.md) to structure stories and ensure consistency.
  • Open questions & assumptions: Explicitly captures OQ and ASM sections to resolve ambiguities before coding.
  • Mode-aware drafting: Supports Liza mode (autonomous drafting) and Pairing mode (human-in-the-loop review).
  • Quality guardrails: Enforces SMARC criteria, acceptance criteria mapping, and dependency specification.
  • Outputs and reuse: Produces markdown story documents ready for commit and reuse across sprints.

Quick Start

Create and save a draft user-story document at the specified path using the canonical As a, I want to, so that format.

Frequently Asked Questions about user-story-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write user stories from vague feature requirements?▼

To write user stories from vague requirements, translate the input into a canonical persona-driven format: As a <persona>, I want to <action>, so that <outcome>. This ensures actionable stories for developers and QA.

What are SMARC-compliant user stories and how do they help development?▼

SMARC-compliant user stories enforce quality criteria during story decomposition. They ensure each story includes clear acceptance criteria, explicit dependencies, and open questions, reducing ambiguity before coding begins.

How do I capture open questions and assumptions in user story documents?▼

Capture open questions and assumptions in user story documents by explicitly defining OQ and ASM sections. This resolves ambiguities before coding and ensures cross-team alignment for story-driven development.

Can I generate markdown user stories for autonomous and human review workflows?▼

Yes, you can generate markdown user stories using Liza mode for autonomous drafting and Pairing mode for human-in-the-loop review. This produces ready-to-commit documents for cross-team alignment.

Does user story generation support traceability to source material?▼

Yes, user story generation supports traceability to source material. It uses reference-driven drafting to structure stories and ensures traceability back to the original requirements.

Related Skills

Explore More Software Engineering Skills→
MarkusonMarkuson

bmad-cis-agent-storyteller

Apply story frameworks and persona-based styles to raw user input.

Community
Advanced
mol4mol4
1

bmad-create-story

Generate implementation-ready markdown story files from BMAD epic and architecture artifacts.

Community
Advanced
elihuvillarauselihuvillaraus
2

pm-sprint

Prioritize agile backlogs using RICE, MoSCoW, and Value vs. Effort frameworks.

Community
Advanced
is-ivanovis-ivanov
2

story

Generate story specification documents from an MVP story list.

Community
Intermediate