openspec-propose

A change proposal documents the feature's goals, impact, and implementation tasks before development begins. Generate a proposal by defining the project scope, assigning a kebab-case change ID, drafting specifications, and listing required tasks. This enforces approval-first workflows and produces proposal.md, tasks.md, and design.md outputs for review.

A spec delta captures modified or added specifications for each capability affected by your change. It documents what changes in the existing design or behavior, enabling reviewers to assess impact quickly and maintain accurate system documentation as features evolve.

Structure your change process in phases: proposal, review, and approval before coding starts. This Skill guides you through generating phase-based outputs that block implementation until explicit user approval is granted, preventing unvetted changes from reaching production.

Yes. This Skill handles both new features and architectural changes during product evolution cycles. The same proposal, task, and spec delta process applies to any significant behavioral or structural change requiring stakeholder review.

You receive proposal.md describing the feature and goals, tasks.md listing implementation work, design.md capturing architectural decisions when needed, and spec deltas documenting all modified or new specifications. These artifacts are ready for team review and approval.