spectra-ingest

Ingest plan files or conversation context to update Spectra changes.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/seanmars/ai-coding-setup --skill spectra-ingest-seanmars
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-ingest
Source: https://github.com/seanmars/ai-coding-setup/tree/main/spectra/skills/spectra-ingest
Command: npx skills add https://github.com/seanmars/ai-coding-setup --skill spectra-ingest-seanmars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingests and updates Spectra changes by consuming either a plan file or conversation context to modify an existing change.

Core Features & Use Cases

  • Ingests plan-based changes or context-driven updates to existing changes.
  • Updates artifacts (proposal, tasks, impact) without discarding completed work.
  • Validates changes and guides next steps within an end-to-end ingestion workflow.

Quick Start

Invoke spectra-ingest via the CLI with a plan file or conversation context to update an existing change.

Frequently Asked Questions about spectra-ingest

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

FAQPage Schema
How do I update existing Spectra changes from a plan file?

To update existing Spectra changes from a plan file, you invoke an ingestion workflow that parses the plan structure and modifies artifacts like proposals and tasks while preserving completed work and progress guardrails.

Can I use conversation context to modify a Spectra proposal?

Yes, you can modify a Spectra proposal by ingesting conversation context to drive updates to existing changes, validating the modifications and guiding the next steps within the end-to-end workflow.

Do I need the spectra CLI to ingest and update change artifacts?

Yes, the spectra CLI is required to ingest and update change artifacts, as the workflow operates within the CLI to read current active or parked changes and determine what needs updating.

What is the best way to preserve completed work when updating change management artifacts?

The best way to preserve completed work during change management artifact updates is to use an ingestion workflow that explicitly parses plan structures and updates proposals without discarding previous progress or guardrails.

Why does my context-driven update not modify the active or parked changes?

Context-driven updates fail to modify changes if the ingestion workflow cannot read the current active or parked changes within the spectra CLI environment to determine the correct target for updating artifacts.