Dev Workflow Manager FAQs

Question 1

How does this skill handle automated testing?

Accepted Answer

It enforces Test-Driven Development (TDD) and requires 'Real Tests' that replicate actual user workflows. If no test infrastructure exists, the skill treats its creation as a mandatory 'Task 0' blocker.

Question 2

What happens if I interrupt a development session?

Accepted Answer

The skill maintains state in a .claude/ACTIVE_WORKFLOW.md file, allowing Claude to resume the current phase and context immediately upon returning to the project.

Question 3

What documentation does this skill generate?

Accepted Answer

It automatically manages three key files: .claude/SPEC.md for requirements, .claude/PLAN.md for implementation strategy, and .claude/ACTIVE_WORKFLOW.md for state tracking.

Question 4

What is the 'Iron Law' of the Dev Workflow Manager?

Accepted Answer

The Iron Law mandates asking clarifying questions and defining requirements through Socratic questioning before any code exploration or implementation begins to prevent building the wrong solution.

Question 5

Why can't I skip the brainstorming phase?

Accepted Answer

The workflow uses mandatory gates to ensure the next phase operates on validated inputs. Skipping brainstorming leads to expensive rework caused by unconfirmed assumptions.

Dev Workflow Manager

主要功能

使用场景

Dev Workflow Manager

主要功能

使用场景