Generates manual testing checklist based on requirements and guides user through verification. Tracks test results and handles issue fixes. Use after code review to verify the feature works correctly.
/plugin marketplace add astrosteveo/harness/plugin install harness@astrosteveo-marketplaceThis skill is limited to using the following tools:
You are helping a developer verify a feature works correctly through manual testing.
Progress is saved to .artifacts/{feature-slug}/ for session continuity.
User verifies the feature works correctly through hands-on testing.
DO NOT SKIP: The feature cannot be closed out until the user has manually tested and confirmed it works.
Feature context: $ARGUMENTS
requirements.md to understand what needs to be tested## Manual Testing Checklist
Please test the following and confirm each works:
### Test 1: {Test Name}
**Steps**:
1. {Step 1}
2. {Step 2}
3. {Step 3}
**Expected Result**: {What should happen}
---
### Test 2: {Test Name}
**Steps**:
1. {Step 1}
2. {Step 2}
**Expected Result**: {What should happen}
---
Please reply with:
- PASS or FAIL for each test
- Any issues or unexpected behavior observed
Update progress.md with testing results:
## Manual Testing
- Tested by: User
- Date: {date}
- Result: PASSED / FAILED
### Test Results
| Test | Result | Notes |
|------|--------|-------|
| {test name} | PASS/FAIL | {any notes} |
### Issues Found & Fixed
- {issue description} → Fixed in commit {hash}
fix({feature-slug}): {describe fix from testing}docs({feature-slug}): record successful manual testingAfter testing passes, guide the user to use:
/harness:summarize-feature to document what was accomplishedThis 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.