openspec-propose

To generate software design and task documentation from an approved proposal, this skill transforms the confirmed direction into formal artifacts, specifically creating proposal.md, design.md, and tasks.md files.

The best way to formalize alignment decisions into development artifacts is using template-driven generation that converts approved directions into proposal.md, design.md, and tasks.md to streamline handoffs and planning.

You create tasks.md and design.md files from a confirmed project direction by applying this skill after alignment within the SPARK-workflow, which generates the artifacts directly from templates and reference mappings.

Yes, you can map external specs to proposal and design documentation for traceability, as the skill provides optional mapping of external specifications to their corresponding generated artifacts.

Yes, you need user approval before moving from draft documentation to implementation, because the skill enforces guardrails that require explicit approval before proceeding to the implementation phase.

You need to escalate issues during software proposal and design generation when the alignment direction is ambiguous or blocked, as the skill provides explicit steps for escalation if approval cannot be reached.