spectra-ingest

Update existing Spectra change artifacts using plan files or conversation context.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/fhsh-tp/fhsh.py-dojo --skill spectra-ingest-fhsh-tp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-ingest
Source: https://github.com/fhsh-tp/fhsh.py-dojo/tree/main/.gemini/skills/spectra-ingest
Command: npx skills add https://github.com/fhsh-tp/fhsh.py-dojo --skill spectra-ingest-fhsh-tp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables users to efficiently update existing Spectra change artifacts using external plan files or conversation context, reducing manual effort and errors.

Core Features & Use Cases

  • Update existing Spectra changes: Incorporate new information into current change artifacts based on plan files or user discussions.
  • Supports conversation-driven workflows: Adapt updates dynamically from chat context when no plan file is available.
  • Use Case: A team needs to modify an ongoing development change based on evolving project requirements, ensuring documentation is current without creating new change proposals.

Quick Start

Use the spectra-ingest skill to update the current Spectra change with the latest plan or discussion 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 project documentation with new plan files?

To update existing project documentation, you integrate external plan files into current change artifacts. This modifies ongoing development changes dynamically, ensuring documentation remains current without creating entirely new change proposals.

Can I modify change management artifacts using conversation context?

Yes, you can modify change management artifacts using conversation context. When no structured plan file is available, the system adapts updates dynamically from chat discussions to maintain workflow accuracy and consistency.

What is the best way to manage iterative change modifications in Spectra?

The best way to manage iterative change modifications in Spectra is by incorporating evolving project requirements into existing artifacts. This approach reduces manual effort and errors while ensuring your change documentation remains accurate and consistent.

Do I need CLI automation tools to update Spectra change artifacts?

Yes, you need spectra CLI automation tools to update Spectra change artifacts. The workflow depends on these CLI tools alongside structured plan files or chat context to facilitate efficient artifact integration and modification.

When should I avoid updating existing change artifacts?

You should avoid updating existing change artifacts when you need to propose entirely new changes rather than modifying ongoing development. This workflow is specifically designed for iterative modifications to current artifacts, not for creating new change proposals.