Skill

Community

verifying-implementation

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

Developer verification ensures the implementation is ready for acceptance testing.

Verification Checklist

Copy and track progress:

Developer Verification:
- [ ] All acceptance criteria manually tested
- [ ] 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

Step-by-Step Process

1. Manual Testing

For each acceptance criterion:

Set up the Given precondition
Execute the When action
Verify the Then result
Document observations

2. Automated Tests

Run the project's test suite:

# Example commands (adapt to your project)
npm test
deno task test
pytest

3. Code Quality

# Linting (adapt to your project)
npm run lint
deno lint
ruff check .

Check for:

No console.log, print(), or debug statements
No uncontextualized TODO comments
No commented-out code blocks

4. Update Story Log

Fill in "Acceptance Checks" section:

### Acceptance Checks

**Status: Pending Product Owner Review**

Developer verification completed:
- Tested all 5 acceptance criteria manually
- Verified error messages display correctly
- Confirmed existing features still work
- All 23 tests pass

Important

Do NOT check acceptance criteria checkboxes — that is the product owner's responsibility
Set status to "Pending Product Owner Review"
Note any observations or edge cases discovered

Links

GitHub Stats

0 forks

Updated 6 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

verifying-implementation | story | ClaudePluginHub