How does it handle complex requirements?

It focuses on simplicity and value, breaking down complex needs into single pieces of value while avoiding unnecessary implementation details.

Can it generate technical tasks for developers?

Yes, the skill can generate specific technical task lists for non-user-facing work, such as database migrations or backend refactoring.

Does it include acceptance criteria?

Yes, for user-facing stories, it generates specific and measurable acceptance criteria to define exactly what 'done' looks like.

What format does this skill use for user stories?

It follows the industry-standard template: 'As a [type of user], I want [goal] so that [reason/benefit]' to ensure clarity and consistency.

User Story Architect

Name: User Story Architect
Author: timbuchinger

bytimbuchinger

Collaboration Tools

Generates concise, industry-standard user stories with acceptance criteria or technical task lists to streamline requirements gathering.

About

The User Story Architect skill empowers developers and project managers to quickly translate raw requirements into actionable, well-structured user stories. Following the standard 'As a... I want... so that...' format, it ensures consistency across your backlog while offering flexible options for either user-facing acceptance criteria or developer-focused task lists. By focusing on outcomes rather than over-engineered documentation, this skill helps teams define clear 'Definition of Done' boundaries for any feature or technical task.

Key Features

0 GitHub stars
Brief context summaries to align stakeholders and developers
Automated technical Task List creation for non-user-facing work
Standardized user story formatting (As a/I want/So that)
Context-aware generation of measurable Acceptance Criteria
Industry best-practice enforcement for agile documentation

Use Cases

Documenting technical infrastructure changes for engineering teams
Converting rough feature ideas into formal product backlog items
Defining clear completion criteria for development sprints

About

Key Features

0 GitHub stars
Brief context summaries to align stakeholders and developers
Automated technical Task List creation for non-user-facing work
Standardized user story formatting (As a/I want/So that)
Context-aware generation of measurable Acceptance Criteria
Industry best-practice enforcement for agile documentation

Use Cases

Documenting technical infrastructure changes for engineering teams
Converting rough feature ideas into formal product backlog items
Defining clear completion criteria for development sprints