spectra-ingest

Update an existing OpenSpec change from a Claude Code plan file or conversation context.

45|3|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/YuDefine/nuxt-supabase-starter --skill spectra-ingest-yudefine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-ingest
Source: https://github.com/YuDefine/nuxt-supabase-starter/tree/main/.claude/skills/spectra-ingest
Command: npx skills add https://github.com/YuDefine/nuxt-supabase-starter --skill spectra-ingest-yudefine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingest and update an OpenSpec change without recreating artifacts, by consuming updates from a Claude Code plan file or from conversation context.

Core Features & Use Cases

  • Read Claude Code plan files from ~/.claude/plans/ and extract the change structure for updates.
  • Merge new context into an existing change, preserving completed tasks and markers while adding new work items.
  • Apply updates to artifacts (proposal, tasks) with status tracking and verification, based on plan stages or discussion.

Quick Start

Provide a plan file path under ~/.claude/plans/ or use your current conversation context to update an existing OpenSpec 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 an existing OpenSpec change from a Claude Code plan file?

You can update an existing OpenSpec change by ingesting a Claude Code plan file located in ~/.claude/plans/. The workflow locates the source, parses the plan structure, applies updates to artifacts, and validates the results without recreating them.

How does merging new context into an existing OpenSpec change work?

Merging new context preserves completed tasks and markers within the existing change while adding new work items. It reads the plan stages or discussion to apply updates to artifacts with status tracking and verification.

Can I use conversation context to update OpenSpec artifacts without a plan file?

Yes, you can update OpenSpec changes directly from conversation context. Instead of reading a plan file, the workflow parses the ongoing discussion to merge new context, add work items, and apply updates to artifacts based on the conversation.

What is the best way to apply plan file updates to OpenSpec tasks?

The best way is to ingest updates from a Claude Code plan file to apply changes to proposal and task artifacts. This method includes status tracking and verification, summarizing progress after validating the applied results.

Does updating OpenSpec changes from Claude Code plans overwrite completed tasks?

No, updating OpenSpec changes from Claude Code plans preserves completed tasks and markers. The ingestion process merges new context to add new work items while maintaining the integrity of previously finished work.

When should I use conversation context instead of a plan file to ingest OpenSpec changes?

Use conversation context when you want to apply updates based on an ongoing discussion rather than a structured plan file. It parses the conversation to merge new context and update artifacts without needing a file in ~/.claude/plans/.