openspec-propose

Automate creation of OpenSpec change proposals and required artifacts.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/zxyycom/docnav --skill openspec-propose-zxyycom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/zxyycom/docnav/tree/main/.codex/skills/openspec-propose
Command: npx skills add https://github.com/zxyycom/docnav --skill openspec-propose-zxyycom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec proposals are currently manual and multi-step. This skill automates the creation of a new change and all its required artifacts inside openspec/changes/<name>/, anchors the objective with a one-line goal, and enforces blocking audit tasks before any implementation tasks.

Core Features & Use Cases

  • Automatically derive a kebab-case change name from user input when given a description.
  • Scaffold a new change directory with the required .openspec.yaml and organize proposal, design, specs, and tasks artifacts.
  • Manage artifact dependencies and gating via 'applyRequires', ensuring a change cannot transition to implementation until audits complete.

Quick Start

Provide a kebab-case change name or a natural-language description of the desired change to start generating a complete OpenSpec proposal and required artifacts.

Frequently Asked Questions about openspec-propose

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

FAQPage Schema
How do I automate OpenSpec change proposals and artifact scaffolding?▼

Automating OpenSpec change proposals involves deriving a kebab-case name from a description, scaffolding a change directory with .openspec.yaml, and organizing proposal, design, specs, and tasks artifacts automatically. This enforces policy and structure while preserving unreviewed artifacts in openspec/changes/<name>/.

What is the applyRequires gating mechanism for OpenSpec proposal artifacts?▼

The applyRequires gating mechanism manages artifact dependencies to ensure a change cannot transition to implementation until blocking audit tasks complete. It enforces blocking audit tasks before any implementation tasks within the OpenSpec workflow.

How do I scaffold a new OpenSpec change directory from a natural language description?▼

Scaffolding a new OpenSpec change directory starts by providing a natural-language description of the desired change. The system derives a kebab-case name, creates the directory, and generates required proposal, design, specs, and tasks artifacts.

Can I use a custom kebab-case name instead of a description for OpenSpec changes?▼

You can use a custom kebab-case change name instead of a natural-language description to start generating a complete OpenSpec proposal. Providing either input triggers the creation of required artifacts and the change directory structure.

Why does my OpenSpec proposal not transition to implementation tasks?▼

An OpenSpec proposal cannot transition to implementation when blocking audit tasks are incomplete. The applyRequires mechanism enforces these gating dependencies, ensuring audits complete before any implementation tasks proceed.