aiox-sm

Generate implementation-ready user stories from PRD content with acceptance criteria.

Updated May 28, 2026
One-click install
npx skills add https://github.com/GustaPaes/aiox-sprint-canvas --skill aiox-sm-gustapaes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiox-sm
Source: https://github.com/GustaPaes/aiox-sprint-canvas/tree/main/.claude/skills/AIOX/agents/sm
Command: npx skills add https://github.com/GustaPaes/aiox-sprint-canvas --skill aiox-sm-gustapaes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a Scrum Master workflow from vague PRD inputs into clear, complete, implementation-ready user stories with consistent acceptance criteria and QA thinking.

Core Features & Use Cases

  • User story creation from PRD: Drafts detailed stories derived from epic/PRD context, keeping scope tight and aligned to outcomes.
  • Story validation & completeness checking: Runs checklist-style validation to catch missing details before handoff.
  • Acceptance criteria, refinement, and sprint planning support: Produces acceptance criteria and helps organize stories for backlog grooming and sprint execution, including local branch workflow guidance.

Quick Start

Use aiox-sm to draft the next user story from the current PRD and then run the story draft checklist for completeness.

Frequently Asked Questions about aiox-sm

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

FAQPage Schema
How do I refine a PRD into actionable user stories for sprint planning?

To refine a PRD into actionable user stories, apply template-driven drafting procedures to extract epic context and generate implementation-ready outputs with consistent acceptance criteria.

What is the best way to draft acceptance criteria and validate user story completeness?

Drafting acceptance criteria and validating user story completeness requires running checklist-style validation procedures to catch missing details and prevent ambiguous handoffs during backlog grooming.

Can I use Scrum workflows to organize backlog grooming and local branch workflow guidance?

Scrum workflows support backlog grooming by organizing stories for sprint execution and providing local branch workflow guidance, ensuring deterministic outputs without executing any remote push operations.

Does this story creation approach work without remote repository push operations?

This story creation approach works entirely without remote push operations, relying on configured story-drafting and checklist procedures to produce deterministic, template-driven user stories locally.

Why does backlog grooming produce incomplete user stories from vague PRD inputs?

Backlog grooming produces incomplete user stories from vague PRD inputs when missing deterministic, template-driven story creation procedures that enforce strict scope alignment and comprehensive acceptance criteria.