OpenSpec Proposal Generator FAQs

Question 1

What is the purpose of OpenSpec proposals in this skill?

Accepted Answer

OpenSpec proposals provide a standardized format for defining technical changes, including test strategies and acceptance criteria, ensuring Claude has a clear roadmap before writing code.

Question 2

What is worktree isolation?

Accepted Answer

Worktree isolation creates a separate git directory for each task batch, allowing Claude to work on multiple technical specifications simultaneously without file system conflicts or contamination.

Question 3

Does this skill require manual intervention?

Accepted Answer

No, it is designed for fully autonomous operation within a development pipeline, automatically triggering the next phase (Test Strategy generation) once all proposals are created.

Question 4

Why does the skill use sequential batching?

Accepted Answer

Sequential batching limits the number of parallel subagents to prevent context exhaustion, ensuring that even large projects with 50+ subtasks can be processed reliably without losing focus.

Question 5

What file format does the task input need to be in?

Accepted Answer

The skill expects a tasks.json file in the .taskmaster directory, which should follow the hierarchical master/subtask format generated during the decomposition phase.

OpenSpec Proposal Generator

Key Features

Use Cases

OpenSpec Proposal Generator

Key Features

Use Cases