skills.rest
juanca202
juanca202COMMUNITY
Explore all skills by this author →
Website𝕏@juanca202GitHub

work-define

Creates and updates user stories with acceptance criteria, INVEST validation, and DoR checks.

Updated May 8, 2026
Search Tags:#requirements#acceptance criteria#spec-driven development#invest#user story#definition of ready#srs decomposition
One-click install
npx skills add https://github.com/juanca202/sdd-devkit --skill work-define-juanca202
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-define
Source: https://github.com/juanca202/sdd-devkit/tree/main/skills/work-define
Command: npx skills add https://github.com/juanca202/sdd-devkit --skill work-define-juanca202

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Turning a business need into a well-formed, ready-to-implement user story is slow and inconsistent: acceptance criteria get written without normative language, dependencies go undocumented, and stories reach development half-defined. This Skill standardizes the creation and updating of user stories (US-XXX) so every story follows the same template, quality rubrics, and traceability conventions. ## Core Features & Use Cases - User story authoring: Generates US-XXX folders with a canonical README template covering description (Como/Quiero/Para), business rules (BR-XX), acceptance criteria (AC-XXX with RFC 2119 keywords and ISO 25010 categories), references, and observations. - Quality validation: Scores each story against the INVEST rubric and a six-criterion Definition of Ready, promoting stories to Ready only when all checks pass, otherwise keeping them in Draft with documented gaps. - SRS decomposition and batching: Splits an existing SRS-XXX specification into multiple user stories, inheriting requirements, repositories, and wireframes, and orders dependent stories before assigning IDs. - Use Case: A product owner describes a new checkout discount feature. The Skill asks structured questions to close gaps, writes US-007 with categorized acceptance criteria, generates UI wireframes, delegates technical documentation to design-define, and hands off to test-define or work-plan once the story is Ready. ## Quick Start Ask the agent to create a user story for the functionality you need documented, for example by describing the actor, the need, and the business value of the feature.

Frequently Asked Questions about work-define

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

FAQPage Schema
How do I create a user story with acceptance criteria?▼

Describe the actor, need, and business value, and the Skill writes a US-XXX folder with a README containing acceptance criteria (AC-XXX) using RFC 2119 normative keywords and functional or ISO 25010 categories. Missing information is resolved through structured questions before drafting.

How to split an SRS requirements specification into user stories?▼

Point the Skill at an existing SRS-XXX and it groups its FR-XXX/NFR-XXX requirements into candidate stories, inherits verification criteria, repositories, and wireframes, then writes back a derived-stories table into the SRS. Deferred requirements are excluded from the batch.

What makes a user story Ready versus Draft?▼

A story reaches Ready only when it has at least one categorized AC-XXX, a complete six-criterion DoR, no failing INVEST dimensions, identified affected repositories, and no open observations. Otherwise it stays in Draft with gaps documented.

Can I update acceptance criteria IDs in an existing user story?▼

No. AC-XXX identifiers are immutable once published because test cases and coverage files reference them verbatim. New criteria take the next free ID and removed ones are marked obsolete in their own text.

Does this Skill create technical design documentation or tasks?▼

No. Technical documentation (models, APIs, flows, diagrams) is delegated to the design-define skill via a subagent, and tasks (TK-XXX) and test cases (TC-XXX) are created only by work-plan and test-define after handoff.

Related Skills

Explore More Product & Management Skills→
khairulariffinkakhairulariffinka
1

srs

Convert business requirements into structured software requirements with traceability artifacts.

Community
Advanced
bacocobacoco
67

bmad-story-planning

Generate developer-ready user stories with acceptance criteria from epics and architecture decisions.

Community
Advanced
oVservantoVservant

technical-architect-agent

Examine PRDs and design specs to produce technical blueprints with ADRs, diagrams, data models, and API specifications.

Community
Advanced
wenyuewenyue

triage

Move GitHub issues and external PRs through a triage state machine with agent-ready briefs.

Community
Advanced