SDD Autopilot FAQs

Question 1

What are the requirements for using SDD Autopilot?

Accepted Answer

It is highly recommended to have steering documents configured in your project directory so the autopilot understands your specific coding standards and architectural preferences.

Question 2

What is the SDD Autopilot skill?

Accepted Answer

It is an automation tool for Claude Code that orchestrates a series of specialized sub-agents to handle every phase of software development, from initial specs to final implementation.

Question 3

When should I use Autopilot versus manual coding?

Accepted Answer

Autopilot is best for routine, well-defined tasks, rapid prototyping, or when you want to generate a baseline implementation to be refined later.

Question 4

Can I restart the autopilot if it fails or stops?

Accepted Answer

Yes, the skill supports a phaseNumber argument, allowing you to resume the automated workflow from any specific phase in the development process without starting over.

Question 5

How does the autopilot handle decision-making?

Accepted Answer

The parent session refers to steering documents in your project to make decisions that align with your technical requirements. If a decision is ambiguous, it follows industry best practices or pauses for user input.

SDD Autopilot

Key Features

Use Cases

SDD Autopilot

Key Features

Use Cases