spectra-ingest

Merge plan file guidance into existing Spectra change artifacts.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/ycs77/gh-aw-todo-app --skill spectra-ingest-ycs77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-ingest
Source: https://github.com/ycs77/gh-aw-todo-app/tree/main/.claude/skills/spectra-ingest
Command: npx skills add https://github.com/ycs77/gh-aw-todo-app --skill spectra-ingest-ycs77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill updates an existing Spectra change by ingesting guidance from a plan file or the conversation context so teams don't have to manually edit Spectra artifacts or merge contextual updates by hand.

Core Features & Use Cases

  • Plan parsing and mapping: Reads Claude-style plan files to extract title, context, stages, file lists, and verification steps and maps them into Spectra artifacts (proposal, tasks.md, etc.).
  • Change selection and preservation: Finds active or parked Spectra changes via the spectra CLI, preserves completed tasks and parallel markers, and merges new context into existing artifacts.
  • Validation and analysis loop: Runs spectra analyze and validate cycles, fixes critical/warning findings up to two iterations, and supports AskUserQuestion prompts when clarification is needed.
  • Use Case: A developer or engineering manager uses a saved plan or chat discussion to update the team's current Spectra change without losing progress or breaking artifact structure.

Quick Start

Use /spectra-ingest with an optional plan file path or name to update an existing Spectra change using a plan file or conversation context.

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 change management artifacts from a plan file?

To update change management artifacts from a plan file, parse the plan to extract context and stages, then merge new requirements into existing proposal and tasks artifacts while preserving completed items and parallel markers.

Can I merge conversation context into Spectra changes without manual editing?

Yes, you can merge conversation context into Spectra changes without manual editing by selecting an active or parked change via the spectra CLI and using the context to modify the proposal and tasks directly.

Does the spectra CLI need to be installed before ingesting plan files?

Yes, the spectra CLI must be installed before ingesting plan files, as it is required to select active or parked changes and to run the necessary analyze and validate cycles during the merge process.

How do plan files map into Spectra proposal and tasks artifacts?

Plan files map into Spectra artifacts by extracting the title, context, stages, file lists, and verification steps from the plan and translating them into the corresponding proposal and tasks.md structures.

What happens when spectra validate returns critical findings after merging changes?

When spectra validate returns critical or warning findings after merging changes, the system automatically fixes them for up to two iterations and can use AskUserQuestion prompts to request clarification if needed.

Will ingesting a new plan overwrite completed tasks in an existing Spectra change?

Ingesting a new plan will not overwrite completed tasks in an existing Spectra change; the process preserves completed tasks and parallel markers while merging new context into the existing artifacts.