spectra-propose

Automating change proposals involves deriving a complete proposal, roles, and artifact set from planning contexts. This workflow manages change directories, writes proposal files, determines dependencies, and validates status.

Dependency-aware artifact creation reads existing dependency artifacts and respects their constraints before producing outputs. This ensures generated files follow the correct dependency order and pass validation loops during the workflow.

Yes, creating change proposals and managing change directories requires the spectra CLI. The CLI drives the guided workflow to classify change types, scan specs, and validate the final proposal status.

The best way to structure a change proposal is providing a clear change requirement to the CLI. The workflow then determines the requirement source, classifies the change type, scans specs, and generates artifacts in dependency order.

Yes, the workflow supports per-artifact guidance and constraints from instructions without executing code. It is locale-aware and policy-driven, ensuring artifact creation respects defined constraints throughout the process.

Change proposal validation may fail if dependency constraints are not met before producing outputs. The workflow runs validation and analysis loops to surface final status, requiring dependencies to be resolved in correct order.