Structured Development Process FAQs

Question 1

What happens during the independent verification phase?

Accepted Answer

The process spawns a fresh agent with read-only access and browser tools to verify the feature from a user's perspective, ensuring that the person (or agent) who wrote the code is not the one certifying it.

Question 2

When should I use the dev-process skill instead of standard coding?

Accepted Answer

You should use dev-process for any task involving multi-file changes, architectural shifts, or features requiring high reliability. It is the default workflow for all work beyond simple, single-file bug fixes.

Question 3

Does it support requirement tracking?

Accepted Answer

Yes, it integrates with the beads system to create individual issues for every acceptance criterion, ensuring every requirement is tracked, tested, and verified before the task is marked complete.

Question 4

What is the 'Current State Verification' requirement?

Accepted Answer

It is a mandatory gate that requires the agent to prove the target code is live and active via terminal commands (grep, git log, etc.) before any architectural spec can be written, preventing errors based on stale mental models.

Question 5

How does this skill handle parallel development?

Accepted Answer

It utilizes a subagent-driven development model to launch multiple agents for independent implementation legs, significantly speeding up complex builds while managing file-level dependencies.

Structured Development Process

Structured Development Process

主な機能

ユースケース

主な機能

ユースケース