What files does dev-clarify interact with?

The skill primarily updates .claude/SPEC.md with clarified requirements, testing decisions, and architectural choices made during the consultation.

What is the primary role of dev-clarify in the development process?

It serves as Phase 3 of the /dev workflow, acting as a mandatory gate to ensure all ambiguities found during exploration are resolved before any design or coding begins.

How does this skill handle automated testing?

It mandates a clear testing strategy, requiring the user to specify frameworks (like Jest or Pytest) and confirming that tests replicate actual user workflows rather than just mocking internal state.

Can I skip the clarification phase?

While the workflow is flexible, dev-clarify is designed as a sequential step to ensure high-quality output; it automatically triggers the 'dev-design' skill only after requirements are fully documented.

What is the 'Iron Law of Clarification'?

It is a non-negotiable rule within the skill that requires the AI to ask targeted questions about edge cases and patterns rather than making assumptions that could lead to rework.

Dev Clarification Workflow

Name: Dev Clarification Workflow
Author: edwinhu

byedwinhu

개발자 도구

Resolves codebase ambiguities and defines automated testing strategies before moving from exploration to implementation.

소개

Dev-Clarify is the essential third phase of the /dev workflow, designed to prevent costly rework by enforcing a 'clarify before design' policy. After exploration, this skill analyzes codebase findings to identify edge cases, integration conflicts, and pattern inconsistencies that require human input. It places a mandatory emphasis on establishing a 'REAL' automated testing strategy—ensuring that tests replicate actual user workflows and protocols—and synchronizes all decisions directly into the project's SPEC.md file to maintain a single source of truth.

주요 기능

Generates targeted questions based on specific code patterns and integration points discovered during exploration
0 GitHub stars
Prevents 'fake tests' by verifying protocol, transport, and user-workflow alignment
Mandates the definition of a robust automated testing strategy (TDD) before implementation
Enforces the 'Iron Law of Clarification' to prevent premature and inaccurate design decisions
Automatically updates SPEC.md and triggers the design phase once ambiguities are resolved

사용 사례

Defining the first failing test case and testing framework for a new feature request
Resolving conflicts when multiple architectural patterns are found within the same codebase
Clarifying complex integration requirements for legacy systems or third-party APIs

소개

주요 기능

Generates targeted questions based on specific code patterns and integration points discovered during exploration
0 GitHub stars
Prevents 'fake tests' by verifying protocol, transport, and user-workflow alignment
Mandates the definition of a robust automated testing strategy (TDD) before implementation
Enforces the 'Iron Law of Clarification' to prevent premature and inaccurate design decisions
Automatically updates SPEC.md and triggers the design phase once ambiguities are resolved

사용 사례

Defining the first failing test case and testing framework for a new feature request
Resolving conflicts when multiple architectural patterns are found within the same codebase
Clarifying complex integration requirements for legacy systems or third-party APIs