spectra-propose

Automate OpenSpec change proposal creation with YAML-frontmatter metadata and validation.

45|3|Updated Jan 20, 2026

Search Tags:#automation #workflow #openspec #change #spectra #propose

Ready to run

npx skills add https://github.com/YuDefine/nuxt-supabase-starter --skill spectra-propose-yudefine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spectra-propose
Source: https://github.com/YuDefine/nuxt-supabase-starter/tree/main/.claude/skills/spectra-propose
Command: npx skills add https://github.com/YuDefine/nuxt-supabase-starter --skill spectra-propose-yudefine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec change proposals are often complex, error-prone, and time-consuming to assemble manually. spectra-propose automates the creation of a complete proposal workflow, ensuring consistency and speed across planning, scoping, and validation.

Core Features & Use Cases

Generate a full set of artifacts and metadata from a user-provided requirement description.
Derive a kebab-case change name, classify the change type, and scan existing specs for relevance.
Manage dependencies, scaffolding, and validation steps to streamline OpenSpec workflows.

Quick Start

Provide a clear change description and let the tool generate all artifacts automatically.

Frequently Asked Questions about spectra-propose

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

FAQPage Schema

How do I automate OpenSpec change proposal generation end-to-end?▼

OpenSpec change proposals are often complex, error-prone, and time-consuming to assemble manually. Automating the workflow ensures consistency and speed across planning, scoping, and validation by applying structured artifacts and guardrails throughout the proposal lifecycle.

How do I automate OpenSpec change proposal generation end-to-end?▼

Automating OpenSpec change proposal generation requires providing a clear change description. The tool then derives a kebab-case change name, classifies the change type, scans existing specs, scaffolds artifacts, and validates metadata automatically to streamline the workflow.

What is the best way to scaffold OpenSpec change artifacts from requirements?▼

The best way to scaffold OpenSpec change artifacts is providing a clear change description to automate generation. The tool derives a kebab-case name, classifies the change type, scans existing specs, and manages dependencies to streamline the workflow.

Can I scaffold OpenSpec artifacts automatically from a requirement description?▼

Yes, you can generate a full set of OpenSpec artifacts and metadata automatically from a user-provided requirement description. The tool scans existing specs for relevance and manages dependencies to streamline the end-to-end workflow.

Does automated OpenSpec proposal generation enforce YAML-frontmatter and structured artifacts?▼

Yes, automated OpenSpec proposal generation enforces YAML-frontmatter metadata, structured artifacts, and guardrails throughout the proposal lifecycle. This ensures consistency and reduces manual errors during requirements capture, plan extraction, and validation.

Why does my manual OpenSpec workflow require dependency management and validation?▼

Manual OpenSpec workflows require dependency management and validation because they lack automated guardrails. Automating the proposal lifecycle manages dependencies, scaffolding, and validation steps to streamline OpenSpec workflows and reduce manual errors.