openspec-proposal

Scaffold and validate OpenSpec proposal files before implementation.

1|Updated Jan 31, 2026

Search Tags:#documentation #validation #scaffolding #change management #openspec #proposal

Ready to run

npx skills add https://github.com/charly-vibes/wai --skill openspec-proposal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-proposal
Source: https://github.com/charly-vibes/wai/tree/main/.agents/skills/openspec-proposal
Command: npx skills add https://github.com/charly-vibes/wai --skill openspec-proposal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating and validating new proposals or changes to the OpenSpec documentation, ensuring adherence to established conventions and clarity.

Core Features & Use Cases

Scaffolds New Proposals: Generates necessary files (proposal.md, tasks.md, design.md) for OpenSpec changes.
Strict Validation: Enforces adherence to OpenSpec conventions and requirements before approval.
Use Case: When proposing a new feature for the AI system, use this Skill to create the initial documentation, define tasks, and ensure the design aligns with existing architecture before implementation.

Quick Start

Use the openspec-proposal skill to scaffold a new change for the 'add-user-authentication' feature.

Frequently Asked Questions about openspec-proposal

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

FAQPage Schema

How do I scaffold documentation for a new OpenSpec proposal?▼

OpenSpec proposal scaffolding generates the required `proposal.md`, `tasks.md`, and `design.md` files to document your change. This ensures all design aspects and tasks are covered before writing implementation code.

What is the best way to validate OpenSpec changes before implementation?▼

Validating OpenSpec changes requires strict adherence to established conventions and guardrails. The validation process enforces minimal implementation, tight scoping, and clear communication before approving the proposal for development.

Do I need to define tasks and design before proposing an OpenSpec change?▼

Yes, defining tasks and design is required before proposing an OpenSpec change. Scaffolding generates a `tasks.md` and `design.md` file to ensure the proposed architecture aligns with existing systems prior to implementation.

How does OpenSpec proposal validation enforce tight scoping for new features?▼

OpenSpec proposal validation enforces tight scoping by applying defined guardrails during the creation process. It requires minimal implementation boundaries and clear communication to be documented before any development begins.

Can I use OpenSpec scaffolding for modifying existing documentation?▼

Yes, you can use OpenSpec scaffolding for modifications to existing documentation. The process applies to both the creation of new proposals and changes, ensuring all updated design aspects meet strict validation conventions.