Skip to content
Agentmart
Submit a tool

user-story-structure

Structure a development request into a clear user story with scope, acceptance criteria, dependencies, risks, and a delivery checklist.

Skill by hoskengadu

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/hoskengadu-user-story-structure

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Structure a development request into a clear user story with scope, acceptance criteria, dependencies, risks, and a delivery checklist.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/user-story-structure

What's inside

Skill name
user-story-structure
Description
Structure a development request into a clear user story with scope, acceptance criteria, dependencies, risks, and a delivery checklist.
License
MIT
Metadata
short-description: User story and acceptance criteria structuring
Instructions
22 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# User Story Structure

Use this skill when a request needs to be transformed into a clear development item.

## Required Focus

- restate the problem in one sentence
- define the user value and expected outcome
- identify in-scope and out-of-scope items
- capture assumptions explicitly
- list dependencies and blockers
- define acceptance criteria that are observable and testable
- note risks, edge cases, and non-functional requirements when relevant

## Rules

- Do not invent business rules that were not provided.
- Prefer acceptance criteria that can be validated by behavior or tests.
- Flag ambiguous requirements instead of silently resolving them.
- Keep the story narrow enough to be implemented and reviewed safely.

From hoskengadu/software-engineering-skills, MIT.

More from hoskengadu/software-engineering-skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Aug 20, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from hoskengadu

Cite this page

user-story-structure skill. Agent Mart. https://agentmart.dev/skills/hoskengadu-user-story-structure (last updated 2026-10-24)