aiox-sm

Transform PRD requirements into validated user stories with acceptance criteria.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/freitassph/aiox-core --skill aiox-sm-freitassph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiox-sm
Source: https://github.com/freitassph/aiox-core/tree/main/.codex/skills/aiox-sm
Command: npx skills add https://github.com/freitassph/aiox-core --skill aiox-sm-freitassph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams consistently transform PRDs and existing requirements into well-formed user stories, with clear acceptance criteria and a sprint-ready backlog.

Core Features & Use Cases

  • User story creation from PRD: Converts product intent into actionable stories with coherent scope and outcomes.
  • Story validation and completeness checking: Verifies drafts for missing details, ambiguity, and gaps against the expected structure.
  • Acceptance criteria definition and refinement: Produces crisp criteria and iterates on stories for sprint planning and backlog grooming.
  • Use Case: You provide a PRD draft and need sprint-ready stories, validated checklists, and acceptance criteria suitable for execution within the next sprint.

Quick Start

Tell the AI: "Act as aiox-sm and draft the next user story from this PRD, then produce a story completeness checklist and acceptance criteria."

Frequently Asked Questions about aiox-sm

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

FAQPage Schema
How do I create sprint-ready user stories from a PRD?

To create user stories from a PRD, provide the requirements draft to generate actionable stories with coherent scope, validated completeness checklists, and defined acceptance criteria for sprint execution.

What is the best way to write acceptance criteria for backlog grooming?

Writing acceptance criteria for backlog grooming involves refining drafted user stories to produce crisp criteria, verify structural completeness, and resolve ambiguity for sprint-ready execution.

Can I use a Scrum Master persona for sprint planning and story refinement?

Yes, adopting a Scrum Master persona applies to sprint planning and story refinement by validating story completeness and generating structured acceptance criteria directly from project artifacts.

Does this approach validate user story completeness against expected structure?

Yes, the process validates user story completeness by checking drafts for missing details and ambiguity against the expected structure to ensure coherent scope and clear outcomes.

How does it handle requirements not explicitly stated in the PRD?

The process executes only declared dependencies and generates stories strictly from provided PRD requirements, ensuring it does not invent requirements or add undocumented scope.