verifying-stories | story-driven | ClaudePluginHub

Skill

Community

verifying-stories

From story-driven

0

Description

Guides developer verification before handoff. Use when completing implementation, preparing for acceptance testing, or self-reviewing work before commit or PR.

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Skill Content

Verifying Implementation

Execute the verification approach defined in the story log.

Checklist

Developer Verification:
- [ ] Acceptance criteria verified (per defined approach)
- [ ] Error cases verified
- [ ] Existing functionality not broken
- [ ] All automated tests pass
- [ ] Linting passes
- [ ] No debug prints left behind
- [ ] No TODO without context
- [ ] Story log updated

Run Tests

npm test        # or
deno task test  # or
pytest

Code Quality

Check for:

No console.log, print(), or debug statements
No uncontextualized TODO comments

Update Story Log

### Acceptance Checks

**Status: Pending Product Owner Review**

Developer verification completed:
- [How each criterion was verified]
- [Observations or limitations]

Important

Do NOT check acceptance criteria checkboxes — PO responsibility
If verification approach wasn't defined or situation has changed, ask PO
Use available MCP tools or skills for testing if present
If verification is limited, explain what wasn't verifiable

Links

GitHub Stats

0 forks

Updated 2 hours ago

Related Skills

Agent Development

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.

From plugin-dev

Command Development

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.

From plugin-dev

Hook Development

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.

From plugin-dev