openspec-propose

Generate a complete change proposal by providing a brief description of your intended build or fix, which scaffolds proposal.md, design.md, and tasks.md files together in a single step to rapidly kick off implementation planning.

An end-to-end software change proposal package includes proposal.md, design.md, and tasks.md artifacts, all following the openspec schema and wired into a coherent planning directory with managed dependencies for immediate execution.

When your project description is vague, the planning process supports interactive prompts to gather context, ensuring the generated design specs and task tracking files accurately reflect your proposed change before implementation begins.

Change proposal generation applies to rapid planning of new changes across software projects, resolving artifact dependencies and outputting ready-to-use planning content tailored to your specific implementation context.

The best way to scaffold design specs and task tracking files is using an automated change proposal generator that creates proposal.md, design.md, and tasks.md simultaneously, ensuring dependency resolution and structural coherence across all artifacts.

Dependency resolution is needed when scaffolding planning artifacts to ensure the generated proposal.md, design.md, and tasks.md files form a coherent planning package, preventing misaligned tasks and structural gaps during early implementation.