spec-propose

Generate software change proposals with Why, What, How, and Risk sections.

9|Updated May 27, 2026
One-click install
npx skills add https://github.com/kamioj/spec-workflow --skill spec-propose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-propose
Source: https://github.com/kamioj/spec-workflow/tree/main/codex/skills/spec-propose
Command: npx skills add https://github.com/kamioj/spec-workflow --skill spec-propose

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The spec-propose skill addresses the challenge of creating comprehensive and detailed proposals for software changes, ensuring that all critical aspects are considered before implementation.

Core Features & Use Cases

  • Draft Proposals: Compose detailed proposals including 'Why', 'What', 'How', and 'Risk' sections.
  • Pre-command Checks: Ensures all necessary research is completed before proposal creation.
  • HARD GATE Approval: Finalizes the proposal with a gate system that requires user approval before proceeding.

Quick Start

Run the $spec-propose command to create a new proposal and follow the prompts.

Frequently Asked Questions about spec-propose

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

FAQPage Schema
How do I draft a software change proposal that covers risks and implementation details?

Drafting a software change proposal requires generating structured sections for 'Why', 'What', 'How', and 'Risk' to ensure all critical aspects are evaluated before implementation begins.

What is the best way to enforce pre-implementation planning for complex cross-stack projects?

Pre-implementation planning for cross-stack projects is enforced by completing all necessary research and generating a tasks.md file to track multiple subtasks before writing any code.

How do I add a hard gate for user approval before a software change is implemented?

Adding a hard gate for user approval involves finalizing the software change proposal with a system that explicitly requires user confirmation before proceeding to the implementation phase.

Do I need research.md and design.md files to create a project governance proposal?

Yes, creating a project governance proposal requires research.md and design.md files to provide context, ensuring all necessary research is completed before proposal creation.

What should be included in a software change proposal for change management?

A software change proposal for change management should include structured sections explaining why the change is needed, what will change, how it will be implemented, and the associated risks.