openspec-propose

Generate structured OpenSpec proposal, design, and task artifacts from feature descriptions.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/hellyaxs/case-cell-shop --skill openspec-propose-hellyaxs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/hellyaxs/case-cell-shop/tree/main/.cursor/skills/openspec-propose
Command: npx skills add https://github.com/hellyaxs/case-cell-shop --skill openspec-propose-hellyaxs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of planning software changes by generating structured OpenSpec proposal artifacts from a user's feature or fix description.

Core Features & Use Cases

  • Change Proposal Generation: Creates proposal.md, design.md, and tasks.md artifacts required for implementation planning.
  • OpenSpec Workflow Automation: Guides artifact creation order, checks dependencies, and prepares changes for implementation with openspec CLI.
  • Use Case: When a developer describes a new feature request, use this Skill to produce a complete implementation-ready change proposal with design decisions and task breakdown.

Quick Start

Use the openspec-propose skill to create a complete change proposal for the feature I want to build.

Frequently Asked Questions about openspec-propose

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

FAQPage Schema
How do I generate structured software change proposals from a feature description?

Generate structured software change proposals by processing feature descriptions to produce implementation-ready artifacts. This automatically creates the proposal, design, and tasks markdown files required for structured engineering workflows.

What is the best way to automate OpenSpec proposal artifact generation for development requests?

Automate OpenSpec proposal artifact generation by submitting development requests to produce complete change documentation. It guides artifact creation order and checks dependencies to prepare changes for CLI execution.

How do I create implementation-ready design and task breakdown documents for new features?

Create implementation-ready design and task breakdown documents by transforming new feature requests into structured artifacts. It generates design decisions and task lists alongside the main proposal to streamline planning.

Do I need the openspec CLI to use generated change proposal artifacts?

You need the openspec CLI to execute and apply the generated change proposal artifacts. The process prepares implementation-ready documentation specifically for OpenSpec-based engineering workflows requiring CLI dependency handling.

Can I use this to plan software design for fixes as well as new feature requests?

You can use this to plan software design for both new feature requests and fixes. It accepts generic development requests to produce the proposal, design, and task artifacts required before implementation.

What artifacts are required for OpenSpec-based engineering workflows before implementation?

The artifacts required for OpenSpec-based engineering workflows are proposal, design, and tasks markdown files. Generating these structured artifacts ensures implementation planning is complete with design decisions and task breakdowns.