Guides product owner through systematic acceptance testing. Use when verifying acceptance criteria, checking story completion, or conducting final review before marking a story as done.
/plugin marketplace add kecbigmt/story-driven-cc/plugin install kecbigmt-story@kecbigmt/story-driven-ccThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Product owner verifies each acceptance criterion is met.
Before starting:
Find the story document:
ls docs/stories/**/*.story.md
Read through all criteria to understand scope.
For each acceptance criterion:
Criterion [N] of [Total]:
Given: [precondition]
When: [action]
Then: [expected result]
Steps to verify:
1. [Setup step]
2. [Action step]
3. [Verification step]
Result: [ ] Pass [ ] Fail [ ] Blocked
Notes: _______________
If PASS: Check the criterion's checkbox in the story log
If FAIL:
If BLOCKED:
All criteria pass:
### Acceptance Checks
**Status: Accepted**
All acceptance criteria verified and passing.
Tested on: [date]
Any criteria fail:
### Acceptance Checks
**Status: Needs Revision**
Failing criteria:
- Criterion 2: [description of failure]
Required fixes:
- [Specific fix needed]
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.