openspec-propose

Generate proposal, design, and task artifacts for OpenSpec changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mohdakil2426/Device-Masker --skill openspec-propose-mohdakil2426
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/mohdakil2426/Device-Masker/tree/main/.agents/skills/openspec-propose
Command: npx skills add https://github.com/mohdakil2426/Device-Masker --skill openspec-propose-mohdakil2426

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Propose a new change by generating all required artifacts in one streamlined step, reducing manual planning and ensuring a consistent starting point for implementation.

Core Features & Use Cases

  • Single-shot proposal: Create a complete change proposal including a proposal, design, and task breakdown.
  • CLI-driven workflow: Orchestrates artifact generation via a single command, with dependency-aware sequencing.
  • Use Case: Teams can rapidly initialize a new feature or fix request by producing ready-to-edit artifacts for planning and execution.

Quick Start

Run the openspec propose flow to generate all required artifacts for a new change.

Frequently Asked Questions about openspec-propose

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

FAQPage Schema
How do I generate a complete change proposal for a new software feature in one step?

Change proposal generation is an automated workflow that produces proposal, design, and task artifacts in a single command. It enforces CLI-driven rules and dependency sequencing to ensure the generated proposal files are ready for development planning.

What artifacts are generated when initializing an OpenSpec change proposal?

OpenSpec change proposal generation creates proposal.md, design.md, and tasks.md artifacts automatically. These files establish a consistent, ready-for-implementation starting point for software project planning and execution.

Can I use a CLI workflow to automate project scaffolding for software changes?

CLI-driven workflows support automated project scaffolding by orchestrating artifact generation through a single command. This enforces dependency-aware sequencing to produce ready-to-implement proposal, design, and task files for software projects.

Do I need any dependencies to use the OpenSpec approach for change proposals?

The OpenSpec change proposal workflow requires no external dependencies to generate artifacts. It internally enforces CLI-driven rules and dependency-aware sequencing to produce ready-to-implement proposal, design, and task files.

What is the best way to create ready-to-edit design and task breakdowns for a new feature?

Creating ready-to-edit design and task breakdowns is best achieved through a single-shot proposal workflow that generates design.md and tasks.md files. This ensures a consistent, dependency-aware starting point for feature implementation and execution.