claude

user-story-skills

27 skills and slash commands for user story refinement across the full lifecycle — discovery, refinement, planning, QA, compliance, and post-release.

0 on GitHubby Jörn Dinklav1.0.0MITupdated 6 months ago

Not in a marketplace yet, so it loads for one session with --plugin-dir.

Plugin user-story-skills in jdinkla/user-story-skills. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (27)

  • story-a11y-linter

    Check a user story against WCAG 2.2 standards — find accessibility issues with cited WCAG criteria, conformance level (A/AA/AAA), impact, affected users, code examples, and assistive-tech considerations. Use when the user asks for an a11y review, accessibility check, WCAG audit, or to catch a11y iss

  • story-agentic-ai

    Assess whether a user story is suitable for implementation by an autonomous AI agent (Claude with tool use, etc.) — scores across 8 criteria including decomposability, tool availability, determinism, and observability. Use when the user asks "can an AI agent build this?", wants to decide between hum

  • story-alternative-solutions

    Propose 2–4 alternative technical/UX approaches to deliver the same business value, with tradeoff analysis, effort estimates, and a recommendation. Use when the user asks "what are other ways to solve this?", wants to explore options before committing to an approach, or needs a build-vs-buy-vs-hybri

  • story-auto-documentation

    Pre-draft documentation updates for a user story — Overview, User Guide, API Reference, Configuration, Changelog — ready for Confluence, Notion, README, or API docs. Use when the user asks "draft the docs for this", wants release notes, or needs markdown-ready documentation before a feature ships.

  • story-bias-audit

    Audit an AI/ML or data-driven user story for algorithmic bias and discrimination — identify bias types, proxy variables, protected groups affected, fairness metrics, regulatory requirements (EU AI Act, NYC LL144, EEOC, etc.), and testing recommendations. Use when the user asks about algorithmic fair

  • story-business-value

    Articulate the business value of a user story across user, business, strategic, and technical dimensions — with evidence, success metrics, and risk of inaction. Use when the user asks "why does this matter?", wants a value statement, needs to pitch a story to stakeholders, or asks for success metric

  • story-doc-drift

    Predict where implementation is likely to drift from the original user-story requirements and design detection + reconciliation strategies across READMEs, ADRs, API docs, runbooks, user guides, and changelogs. Use when the user asks about doc drift, keeping docs in sync with code, scope-creep detect

  • story-edge-cases

    Adversarial edge-case hunting — identify 8–15 scenarios that could break a feature, thinking like an attacker and chaos engineer, across input validation, state, concurrency, integration, user behavior, data, and performance. Use when the user asks "what could break this?", wants edge cases, or need

  • story-failure-scenarios

    Identify 6–10 failure modes for a user story across infrastructure, data, integration, user error, business logic, security, and performance — with triggers, impact, detection, recovery, and prevention. Use when the user asks "how could this fail?", wants resilience/SRE thinking, or is planning grac

  • story-feedback-sentiment

    Design a post-release feedback-sentiment-monitoring strategy for a user story — sources, sentiment indicators, categories, alert rules, response templates, and reporting cadence. Use when the user asks how to monitor user reception, track sentiment, handle feedback, or set up post-launch listening.

  • story-gherkin

    Translate a user story into 2–5 Gherkin (Given/When/Then) BDD scenarios covering happy path, alternatives, edge cases, and error conditions. Use when the user asks for Gherkin / BDD scenarios, Cucumber steps, acceptance test scenarios, or "write this as Given/When/Then".

  • story-implementation

    Produce a rough technical implementation plan for a user story — 6–12 tasks organized by phase (Data/Backend, Frontend, Integration, Testing, Deployment) with effort estimates, technical considerations, and risks. Use when the user asks "how would we build this?", wants a task breakdown, or needs an

  • story-invest

    Evaluate a user story against the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) with pass/partial/fail ratings, concrete suggestions, and a coaching note. Use when the user asks for an INVEST review, wants to score a story, or asks "is this story ready/well-formed?"

  • story-kickoff

    Produce a development-readiness checklist for a user story across Clarity, Scope, Dependencies, Design, Technical, and Team dimensions — marking each item ready/needs-attention/blocked. Use when the user asks "is this story ready to start?", wants a kickoff checklist, or is about to pull a story int

  • story-nonfunctional

    Extract 6–12 specific, measurable nonfunctional requirements (performance, scalability, security, reliability, accessibility, observability, usability, maintainability) for a user story, with priority and rationale. Use when the user asks about NFRs, quality attributes, SLAs, or "what should this th

  • story-persona-empathy

    Run a Persona Empathy Mapping analysis on a user story — simulate 2–4 distinct user personas and critique whether the story actually solves their real pain points. Use when the user asks to validate a story from user-perspective, run empathy mapping, check who the story serves, or ask "does this act

  • story-pii-scanner

    PII/privacy scan of a user story — identify personal data collected/processed, assess whether a DPIA is required, map GDPR/CCPA/HIPAA/PCI-DSS obligations, data subject rights, cross-border concerns, and 4–8 privacy recommendations. Use when the user asks about privacy risk, PII handling, DPIA, GDPR

  • story-qa

    Identify comprehensive test coverage for a user story — 8–15 test cases across unit/integration/E2E levels and happy/edge/error/security/performance types. Use when the user asks for a QA plan, test coverage analysis, "what should we test?", or wants a test-pyramid-balanced list of test cases.

  • story-questions

    Surface unknowns, assumptions, and clarifying questions for a user story before implementation begins — categorized and prioritized. Use when the user asks "what's missing from this story?", "what questions should I ask?", or wants to find hidden assumptions before development.

  • story-requirements-breakdown

    Split a large user story into 3–7 smaller, independently deliverable sub-stories with acceptance criteria, dependencies, and a suggested implementation order. Use when the user says "this story is too big", asks to split/break down a story, or needs help slicing an epic into sprint-sized pieces.

  • story-security

    Full application-security analysis of a user story — OWASP Top 10 coverage, XSS/CSRF/IDOR, authn/authz, crypto, input validation, compliance (GDPR/PCI/HIPAA), with 6–12 findings including attack scenarios, severity, mitigations, and CWE/OWASP references. Use when the user asks for a security review,

  • story-stakeholder-impact

    Identify which downstream teams and stakeholders (support, sales, ops, legal, DevOps, security, etc.) need to be informed or involved when a story ships, with communication plan and timeline. Use when the user asks "who else needs to know about this?", wants a rollout comms plan, or is preparing a c

  • story-summary

    Generate a 30-second quick-reference summary of a user story — one-liner, what/who/why, key features, acceptance summary, complexity indicator, and tags. Use when the user wants a TL;DR, backlog-scanning summary, or handoff-ready synopsis of a story.

  • story-synthetic-data

    Specify the mock/synthetic test data needed to thoroughly test a user story — entities, scenarios (happy/edge/error/perf), constraints, generation approach, and seed SQL. Use when the user asks "what test data do we need?", wants a data fixture plan, or is setting up a test environment.

  • story-telemetry-predictor

    Predict exactly which events, metrics, dashboards, and A/B tests to track for a user story — tying each back to the business value it should prove. Use when the user asks "what should we track?", wants telemetry / analytics plans, success metrics, dashboards, or KPIs for a feature.

  • story-user-journey

    Map a user story to the broader user journey(s) it touches and surface gaps, broken handoffs, dead ends, or fragmentation. Use when the user asks to check journey fit, find missing steps, understand where a story sits end-to-end, or spot workflow fragmentation.

  • story-visual-regression

    Predict which existing screens or components may break visually based on the CSS/component changes described in a user story — affected screens, risk levels, affected visual elements, screenshot checklist. Use when the user asks about visual regression risk, which screens to screenshot-test, or what

Slash commands (27)

  • /user-story-skills:story-a11y-linter

    Check a user story against WCAG 2.2 — find accessibility issues with cited criteria, conformance level, impact, and fixes.

  • /user-story-skills:story-agentic-ai

    Assess whether a user story is suitable for implementation by an autonomous AI agent across 8 criteria, with a suitability score.

  • /user-story-skills:story-alternative-solutions

    Propose 2–4 alternative technical/UX approaches to deliver the same business value, with tradeoffs and a recommendation.

  • /user-story-skills:story-auto-documentation

    Pre-draft documentation updates for a user story — overview, user guide, API reference, configuration, changelog, in markdown.

  • /user-story-skills:story-bias-audit

    Audit a user story for algorithmic bias — bias types, proxy variables, protected groups, fairness metrics, regulatory requirements.

  • /user-story-skills:story-business-value

    Articulate user, business, strategic, and technical value of a user story with evidence and success metrics.

  • /user-story-skills:story-doc-drift

    Predict where implementation may drift from requirements, and design detection + reconciliation strategies across docs.

  • /user-story-skills:story-edge-cases

    Adversarial edge-case hunting — 8–15 scenarios that could break the feature, thinking like an attacker and chaos engineer.

  • /user-story-skills:story-failure-scenarios

    Identify 6–10 failure modes for a user story with triggers, impact, detection, recovery, and prevention strategies.

  • /user-story-skills:story-feedback-sentiment

    Design a post-release feedback-sentiment-monitoring strategy — sources, indicators, alert rules, response templates, cadence.

  • /user-story-skills:story-gherkin

    Translate a user story into 2–5 Gherkin (Given/When/Then) BDD scenarios covering happy, alternative, edge, and error paths.

  • /user-story-skills:story-implementation

    Produce a rough technical implementation plan — 6–12 tasks by phase, with effort estimates, tech considerations, and risks.

  • /user-story-skills:story-invest

    Evaluate a user story against the INVEST criteria with pass/partial/fail ratings, suggestions, and a coaching note.

  • /user-story-skills:story-kickoff

    Produce a development-readiness checklist for a user story across Clarity, Scope, Dependencies, Design, Technical, and Team.

  • /user-story-skills:story-nonfunctional

    Extract 6–12 specific, measurable nonfunctional requirements for a user story with priority and rationale.

  • /user-story-skills:story-persona-empathy

    Run Persona Empathy Mapping on a user story — simulate personas and critique how well the story solves their real pain points.

  • /user-story-skills:story-pii-scanner

    PII/privacy scan of a user story — personal data, DPIA requirement, GDPR/CCPA/HIPAA/PCI obligations, and recommendations.

  • /user-story-skills:story-qa

    Identify 8–15 test cases across unit/integration/E2E and happy/edge/error/security/performance for a user story.

  • /user-story-skills:story-questions

    Surface unknowns, assumptions, and clarifying questions for a user story — categorized and prioritized.

  • /user-story-skills:story-requirements-breakdown

    Split a large user story into 3–7 smaller, independently deliverable sub-stories with dependencies and a suggested order.

  • /user-story-skills:story-security

    Full security analysis of a user story — OWASP Top 10, XSS/CSRF/IDOR, authn/authz, crypto, compliance, with 6–12 findings.

  • /user-story-skills:story-stakeholder-impact

    Identify downstream teams affected by a user story going live, their communication needs, and engagement timeline.

  • /user-story-skills:story-summary

    Generate a 30-second quick-reference summary of a user story — one-liner, what/who/why, key features, complexity, tags.

  • /user-story-skills:story-synthetic-data

    Specify test/mock data for a user story — entities, scenarios, constraints, generation approach, and seed SQL.

  • /user-story-skills:story-telemetry-predictor

    Predict events, metrics, dashboards, and A/B tests to track for a user story — each tied to the business value it should prove.

  • /user-story-skills:story-user-journey

    Map a user story to the broader user journey(s) and surface gaps, broken handoffs, and dead ends.

  • /user-story-skills:story-visual-regression

    Predict which existing screens/components might break visually based on a user story's CSS/component changes.

View source on GitHub

Similar plugins

AgentBBS cross-host agent federation (ADR-164). Phase 1: register/publish/watch/human-join room coordination. Phase 2 (v3.40.0): signed cross-host federation — identity, peer_add (pin by nodeId+Ed25519 key), peers, serve (read-only pull), sync (pull + union-merge what verifies). Registry-anchored pinning; works on any network (no tailnet required); coordinates work claims (ClaimIssued/Released/Handoff/Ack). Degrades gracefully when agentbbs is absent.

1 skill

ruvnet/ruflo 81,589

clay

claudecodex

Work with Clay from Claude Code: set up and sign in to the clay CLI, query and analyze Clay tables, search Clay's GTM database for people and companies, manage audiences, signals, routines and workflows, and draft and review Sequencer campaigns. Includes hooks that auto-approve the plugin's own clay CLI calls and Clay skills; requires a Clay account.

38 skills · hooks

anthropics/claude-plugins-official 47,076

Require a human approval signal before an AI agent can post PR reviews, comments, merges, or writes to CI configuration. Joins protect-mcp and signed-audit-trails in the governance category; composes with protect-mcp for runtime enforcement.

1 skill · 2 commands · 1 agent · hooks

wshobson/agents 42,461

Maven Bio

claude

Evidence-backed BioPharma research workflows over Maven Bio's drug, trial, company, and deal knowledge graph. Skills for competitive pipelines, indication landscapes, asset profiles, deal and financing activity, and evidence synthesis grounded in FDA, SEC, clinical, and press sources. Requires a Maven Bio account.

16 skills · 1 agent · 1 MCP server

anthropics/knowledge-work-plugins 35,601

14 bundled product skills with 19 Python tools: product-skills fork-orchestrator with continuous-discovery loop (deterministic 16-lane router, Torres cadence tracker, OST linter, /cs-product + /cs-grill-product + /cs-product-loop), product manager toolkit (RICE, PRDs), product strategist, UX researcher, UI design system, competitive teardown, landing page generator, SaaS scaffolder, product analytics, experiment designer, product discovery, roadmap communicator, spec-to-repo, design-qa (UI finish gate: inert controls, missing states, rendered WCAG 2.2 checks). Companion standalone plugins: agile-product-owner, code-to-prd, apple-hig-expert, research-summarizer, design-qa.

14 skills · 3 commands · 1 agent · hooks

alirezarezvani/claude-skills 29,725

Real-time statusline showing context usage, active tools, running agents, and todo progress. Always visible below your input, zero config required.

1 skill

jarrodwatts/claude-hud 29,182

Maintain user-story-skills?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted