openspec-plan

You can create structured change proposals by analyzing your repository to produce proposal.md, tasks.md, and specification files. The workflow assumes a decision has already been made and focuses on generating the rationale, scope, and implementation guidance for the proposed changes.

The best way to document rationale and impact is by generating formal OpenSpec proposal artifacts. This Skill creates proposal.md and tasks.md files that capture the reasoning, scope, and implementation steps required for multi-file software modifications.

Yes, this Skill applies directly to software projects needing formalized change proposals across multiple files. It analyzes the codebase to generate scope-defining specs and tasks.md files that guide the implementation process.

The workflow generates specification artifacts by applying an Analyze, Reason, and Generate engine to your codebase. It outputs structured files including proposal.md and tasks.md to the openspec/changes directory to guide implementation and testing.

Yes, you need a prior decision via brainstorming or a direct request because this Skill assumes a decision has already been made. It focuses on analyzing the codebase and producing the formal proposal, rationale, and scope rather than initial ideation.