Principled Implementation Strategy FAQs

Question 1

What is the benefit of using git worktrees for task isolation?

Accepted Answer

Git worktrees allow each task to run in a completely separate directory with its own branch, ensuring that parallel tasks or sub-agents don't interfere with each other or the main working directory.

Question 2

Is this skill manually invocable by the user?

Accepted Answer

No, this is a background knowledge skill that informs Claude's behavior and decision-making automatically when it detects implementation-related context or directory structures.

Question 3

How does the manifest.json file function in this skill?

Accepted Answer

The .impl/manifest.json acts as the single source of truth, tracking the state, status, and metadata of all tasks throughout the implementation lifecycle to ensure atomic updates.

Question 4

How does the skill handle task failures?

Accepted Answer

The orchestration logic evaluates failure types to decide whether to retry the task, skip it, or pause for user input, following the state machine defined in the task lifecycle documentation.

Question 5

What is the decompose-spawn-validate-merge lifecycle?

Accepted Answer

It is a structured workflow where high-level plans are broken into tasks (decompose), executed by workers (spawn), checked against test suites (validate), and finally integrated into the main branch (merge).

Principled Implementation Strategy

Principled Implementation Strategy

Key Features

Use Cases

Key Features

Use Cases