openspec-propose

Organize a software change request into an OpenSpec proposal, design, and task plan.

4|9|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/DataDave-Dev/weftmap --skill openspec-propose-datadave-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/DataDave-Dev/weftmap/tree/main/.codex/skills/openspec-propose
Command: npx skills add https://github.com/DataDave-Dev/weftmap --skill openspec-propose-datadave-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the overhead of manually organizing a software change into a complete, implementation-ready plan with consistent proposal, design, and task artifacts.

Core Features & Use Cases

  • Change Scaffolding: Creates a new OpenSpec change directory from a kebab-case name or natural-language request.
  • Artifact Generation: Produces proposal, design, and task documents in dependency order using the project's OpenSpec schema.
  • Workflow Validation: Checks artifact status, reads dependencies, verifies generated files, and confirms when the change is ready for implementation.
  • Use Case: When a user describes a feature such as adding authentication, use this Skill to create the complete planning package and prepare it for implementation with OpenSpec.

Quick Start

Use the openspec-propose skill to turn my request for a new user authentication feature into a complete proposal, design, and task plan.

Frequently Asked Questions about openspec-propose

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

FAQPage Schema
How do I generate implementation-ready software change plans from feature ideas?

To generate implementation-ready software change plans, you can use OpenSpec to organize requests into complete proposal, design, and task artifacts. This scaffolding process validates dependencies and prepares the package for implementation.

What is the best way to structure software requirements for architectural changes?

The best way to structure software requirements for architectural changes is to generate design documents and proposal artifacts in dependency order. This approach ensures workflow validation and confirms implementation readiness before development starts.

Do I need the OpenSpec CLI to create design documentation and task plans?

Yes, you need the OpenSpec CLI to create design documentation and task plans. The CLI is required to validate artifact dependencies, verify generated file output paths, and confirm when the change package is fully ready for implementation.

Can I use automated proposal generation for bug fixes and repository work?

Yes, you can use automated proposal generation for bug fixes and repository work. The process applies to feature development and architectural changes by reading dependencies and producing structured planning artifacts within a dedicated change directory.

How does workflow validation check implementation readiness for software requirements?

Workflow validation checks implementation readiness by verifying artifact status, reading dependencies, and confirming generated file output paths. It ensures all design and task documents are complete and correctly structured before implementation begins.