spectra-propose

To generate a complete change proposal, provide a requirement description and the skill derives a change name, classifies it as Feature or Bug Fix, scans specs, writes the proposal, and creates dependent artifacts. It then runs validation checks and parks the change for implementation.

Automating Spectra artifact generation and spec scanning is handled by parsing conversation context or plan files to fetch artifact instructions, creating a change directory, and generating required artifacts in sequential order with automated analyze-fix loops.

Yes, you need the spectra CLI installed and available in your system PATH to create and validate change proposals. The skill relies on the CLI to execute spectra validate and spectra park commands during the workflow.

Yes, you can use a plan file to draft a Spectra change proposal instead of typing requirements. The skill supports plan-file extraction to automatically derive the change name and requirement context for proposal generation.

Automated validation for Spectra change proposals works by running analyze-fix iterations after artifact creation, executing the spectra validate command to ensure correctness, and optionally parking the validated change using the spectra park command.

Limitations of automating repository change workflows include a strict dependency on the spectra CLI being in PATH, requiring valid plan files or conversation context for extraction, and being confined to the Spectra proposal structure rather than generic repository commits.