App User Story QA

App User Story QA is a Quality skill for Claude Code, published by majiayu000 in spellbook.

265 stars26 forkson majiayu000/spellbookAdded 2026/09/02+1% in starsRepository updated 2026/08/31

agent-skillsai-agent-skillsai-agentsai-coding-assistantautomationclaudeclaude-codeclaude-code-skillscode-reviewcodexcodex-skillscross-runtimedeveloper-toolsmulti-agentproductivityprompt-engineeringskill-librarysoftware-developmentspellbookworkflows

Install in seconds

Install App User Story QA

Copy App User Story QA into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/majiayu000/spellbook/tree/main/skills/app-user-story-qa ~/.claude/skills/app-user-story-qa

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/majiayu000/spellbook.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/app-user-story-qa/SKILL.md in majiayu000/spellbook
Installs to: ~/.claude/skills/app-user-story-qa
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1418 skills

What App User Story QA does

App User Story QA turns a broad request to test an app into a tracked loop of feature inventory, code-backed expected behavior, and user-story tests. Use it to audit every surface, classify failures, and retest documented defects after fixes.

App User Story QA is cataloged under Quality on DirSkills. App User Story QA comes from a repository tagged agent-skills, ai-agent-skills, ai-agents, ai-coding-assistant and automation.

Documentation

README

Excerpt

App User Story QA

Purpose

Use this skill to turn a broad "test every feature in this app" request into a controlled loop with one source of truth. Anchor every feature to code, track expected behavior in a canonical spreadsheet, run tests against each user story, and classify failures. Apply fixes only when the current request explicitly authorizes them.

Route

Use plan_first for most runs. Switch to clarify_first only when the app boundary, writable checkout, production risk, or acceptance criteria are unclear enough that a wrong assumption would waste substantial work.

Before editing:

This is the opening of the README. Read the full README on GitHub.

Frequently asked about App User Story QA

What else does majiayu000 publish alongside App User Story QA?
App User Story QA is one of 25 skills that DirSkills catalogs from majiayu000/spellbook, the repository it ships in. Its siblings there include AGENTS.md Scaffold, API Design and Agents Md Optimize. Each one is a separate skill with its own page in this directory, installs the same way App User Story QA does, and is maintained by majiayu000 in that same repository. The rest of the collection is listed on the majiayu000/spellbook page.
How does App User Story QA compare to other Quality skills?
App User Story QA ranks #1268 by stars among the 1418 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of App User Story QA against them. Open each page to compare what they document and how they install.