spectra-propose

Automating change proposal generation involves resolving requirements from arguments or plan files, orchestrating artifact creation in dependency order, and validating outputs before delivery. This structured workflow enforces spec scanning and status tracking to yield unpark-ready artifacts.

Deriving a kebab-case name and change description from conversation context requires applying a structured proposal workflow that scans specs for relevance and tracks artifact status. This process extracts the core requirement and translates it into the required naming convention.

Yes, argument-based inputs, plan files, or conversation context can start the proposal workflow. The system applies source resolution to derive the requirement automatically, avoiding manual guessing and initiating the end-to-end artifact generation process.

Artifact orchestration ensures proper dependency order by creating the change directory, generating the proposal, and building related artifacts sequentially. It tracks progress throughout the workflow, conducting inline self-reviews and validating compliance before final park delivery.

The change proposal workflow operates with no external dependencies or components required. It self-contains the spec scanning, artifact creation, and validation processes internally to deliver complete change proposals ready for implementation.

Enforce inline self-review and spec scanning before parking a change proposal to ensure quality and governance compliance. These validation steps verify all artifacts meet process standards and the generated change description accurately reflects the resolved requirement.