design

You design and validate new software features by running an OpenSpec-driven workflow that interactively clarifies scope, explores possibilities, proposes solutions, and commits finalized OpenSpec changes to main.

Yes, generating architecture documentation and task lists is a core output of the feature design workflow, produced after exploring and proposing the design interactively.

Product-context.yaml provides project-wide context that the feature design workflow reads when available, using it to tailor architecture documents and OpenSpec proposals to your specific project environment.

The best way to run these phases interactively is to provide your feature idea, which triggers a guided conversational workflow through exploration, proposal generation, and design review before committing changes.

No, a product-context.yaml file is not required to start an OpenSpec feature proposal, though the workflow reads it when available to better tailor the generated design and architecture outputs.

You should avoid interactive feature design when your OpenSpec changes are fully defined and require no scope clarification, exploration, or design review, as the workflow commits finalized artifacts directly to main.