draft-proposal

Convert exploration analysis into a structured SDD change proposal.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/lleontor705/cortex-ia --skill draft-proposal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: draft-proposal
Source: https://github.com/lleontor705/cortex-ia/tree/main/internal/assets/skills/draft-proposal
Command: npx skills add https://github.com/lleontor705/cortex-ia --skill draft-proposal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft proposals from exploration analyses to provide a structured, reviewable plan with clear intent, scope, risks, and rollback steps for SDD-driven changes.

Core Features & Use Cases

  • Converts exploration artifacts into a formal draft proposal ready for review and approval.
  • Defines IN and OUT scope with concrete deliverables and deferred work.
  • Captures success criteria, risk assessment, rollback plan, and dependencies.
  • Integrates with OpenSpec and Cortex workflows by writing to openspec/changes/{change-name}/proposal.md or persisting artifacts as needed.

Quick Start

Load the exploration artifact for the change and generate a complete proposal in openspec/changes/{change-name}/proposal.md for review.

Frequently Asked Questions about draft-proposal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert exploration analysis into a structured change proposal?▼

To convert exploration analysis into a structured change proposal, you load the exploration artifact and generate a formal draft detailing intent, scope, risks, and rollback steps suitable for SDD workflows.

What is a proposal in SDD workflows?▼

A proposal in SDD workflows is a structured, reviewable plan that defines IN and OUT scope, captures success criteria, risk assessment, rollback plans, and dependencies for discovered changes.

How do I define scope and rollback steps for a software change proposal?▼

To define scope and rollback steps for a software change proposal, you specify concrete deliverables, mark deferred work as OUT scope, and provide a concrete rollback plan with verifiable success criteria.

Can I use this proposal generation process with OpenSpec and Cortex workflows?▼

Yes, this proposal generation process integrates with OpenSpec and Cortex workflows by writing the structured proposal directly to openspec/changes/{change-name}/proposal.md or persisting artifacts as needed.

What is the best way to document risks and success criteria for code changes?▼

The best way to document risks and success criteria for code changes is generating a formal proposal that includes verifiable success criteria, a concrete rollback plan, risk assessment, and concrete file path references.

Do I need concrete file paths to generate a change proposal?▼

Yes, you need concrete file paths because the generated proposal must reference specific files alongside verifiable success criteria and a concrete rollback plan to be reviewable in SDD-driven workflows.