spectra-ingest

To update a Spectra change, parse a plan file or extract new requirements from conversational context. The skill automatically selects the appropriate active or parked change, merges new information into proposals and tasks, and runs Spectra CLI validation to ensure consistency.

Yes, merging new information into Spectra artifacts preserves completed tasks marked with `[x]` and parallel markers marked with `[P]`. The merge process respects locale rules to maintain artifact consistency across different regions.

You need to unpark a parked Spectra change when new requirements appear and must be incorporated into existing artifacts. The skill automatically unparks the appropriate change to merge new proposals, tasks, and impact assessments before validating the update.

Yes, Spectra CLI validation and analysis run after merging to ensure the updated change meets all requirements. This validation confirms that artifact merging respects locale rules and that the overall change remains structurally consistent.

The best way to incorporate conversational context is to let the skill extract requirements directly from the ongoing chat. It then merges this information into proposals, tasks, and impact artifacts just as it would with a structured plan file.

Respecting locale rules during artifact merging ensures that text formatting, sorting, and regional variations remain correct across different environments. This prevents data corruption and maintains consistency when new requirements are added to existing changes.