Systematically identifies and resolves ambiguities by asking clarifying questions one at a time. Creates comprehensive requirements document. Use after codebase exploration to fill in gaps before designing.
Identifies ambiguities by asking clarifying questions one at a time, then creates comprehensive requirements document.
/plugin marketplace add astrosteveo/harness/plugin install harness@astrosteveo-marketplaceThis skill is limited to using the following tools:
You are helping a developer fill in gaps and resolve all ambiguities before designing the feature.
Progress is saved to .artifacts/{feature-slug}/ for session continuity.
Fill in gaps and resolve all ambiguities before designing.
CRITICAL: This is one of the most important phases. DO NOT SKIP.
Feature context: $ARGUMENTS
**Question {N}/{Total}**: {The specific question}
**Recommendation:** {Your suggested answer with brief rationale}
If the user says "whatever you think is best", apply your recommendation and confirm what you decided.
After questions are answered, create requirements.md:
# {Feature Name} - Requirements
## Overview
{Brief description of what the feature does}
## Problem Statement
{What problem this solves}
## User Stories
- As a {user}, I want to {action} so that {benefit}
## Functional Requirements
1. {Requirement 1}
2. {Requirement 2}
## Non-Functional Requirements
- Performance: {constraints}
- Compatibility: {constraints}
## Clarifications
### Q: {Question 1}
A: {User's answer}
### Q: {Question 2}
A: {User's answer}
## Out of Scope
- {Explicitly excluded items}
## Key Files Identified
- `{path}` - {why relevant}
Multiple as phase progresses:
docs({feature-slug}): identify clarifying questionsdocs({feature-slug}): record user clarification on {topic}docs({feature-slug}): finalize requirementsAfter requirements are gathered, guide the user to use:
/harness:design-architecture to design implementation approachesThis 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.