spectra-propose

Automate Spectra change proposal creation with dependency-aware artifact generation.

33|8|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/PsychQuant/che-ical-mcp --skill spectra-propose-psychquant
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spectra-propose
Source: https://github.com/PsychQuant/che-ical-mcp/tree/main/.agents/skills/spectra-propose
Command: npx skills add https://github.com/PsychQuant/che-ical-mcp --skill spectra-propose-psychquant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a complete Spectra change proposal — from requirement to validated artifacts — in a single workflow. This tool streamlines how teams propose changes by auto-deriving a change name, classifying the change type, scanning for related specs, and orchestrating artifact generation in the correct order.

Core Features & Use Cases

  • End-to-end proposal workflow: from initial requirement description to a ready-to-implement change package with all required artifacts.
  • Flexible input sources: provide the requirement as an argument, or derive from a plan file or conversation context, with automatic kebab-case name derivation.
  • Spec-aware planning: scans for related specs and surfaces relevant context to keep proposals aligned with existing standards.
  • Artifact orchestration: creates the change, writes a proposal, checks dependencies, and sequences artifact creation following a dependency graph.
  • Guardrails and validation: classifies change type (Feature, Bug Fix, Refactor) and supports validation flows to ensure consistency with specs and project goals.

Quick Start

Invoke spectra-propose with your requirement description to generate all required artifacts in a single workflow.

Frequently Asked Questions about spectra-propose

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

FAQPage Schema
How do I automate software change proposal workflows and artifact generation?▼

Automating software change proposal workflows involves deriving requirements, scanning related specs, and orchestrating artifact generation in a dependency-aware sequence to produce a validated package.

How do I generate a kebab-case change name from conversation context or plan files?▼

Generating a kebab-case change name from conversation context or plan files requires a tool that auto-derives the name while classifying the change type and checking related project specifications.

What is the best way to sequence artifact creation following a dependency graph?▼

Sequencing artifact creation following a dependency graph ensures structured workflow consistency by checking dependencies before writing proposals and validating the final change package.

Can I classify change types like Feature, Bug Fix, or Refactor during proposal generation?▼

Classifying change types like Feature, Bug Fix, or Refactor during proposal generation enforces guardrails and supports validation flows to ensure consistency with existing specs and project goals.

Does spec-aware planning help align new change proposals with existing standards?▼

Spec-aware planning aligns new change proposals with existing standards by scanning for related specs and surfacing relevant context before orchestrating artifact generation.