spectra-apply

Coordinate Spectra change application via a tasks.md file and CLI.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/Bruno-Yu/portfolio --skill spectra-apply-bruno-yu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-apply
Source: https://github.com/Bruno-Yu/portfolio/tree/main/.cursor/skills/spectra-apply
Command: npx skills add https://github.com/Bruno-Yu/portfolio --skill spectra-apply-bruno-yu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spectra changes often require coordinated task tracking and progressive execution. This skill provides a self-contained workflow to select a change, validate state, run preflight checks, analyze artifacts, and iteratively implement tasks recorded in a single tasks.md file.

Core Features & Use Cases

  • Task-based progress: Tracks progress exclusively in a markdown tasks file, ensuring a single source of truth.
  • Parked changes handling: Guides unpark/in-progress state transitions for parked changes.
  • Preflight and artifact checks: Performs preflight checks and artifact analysis to surface issues before execution.
  • Interactive state handling: Prompts user when needed to resolve ambiguity or critical findings.
  • CLI-guided workflow: Integrates with spectra CLI for status, instructions, and task execution.

Quick Start

To begin, specify a change name with /spectra:apply <change-name> to start applying tasks.

Frequently Asked Questions about spectra-apply

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

FAQPage Schema
How do I apply Spectra changes and track task progress in a single file?

To apply Spectra changes, use the spectra-apply workflow to select a change, run preflight checks, and iteratively implement tasks. It tracks all progress exclusively in a markdown tasks file to maintain a single source of truth for development.

What is the best way to manage parked or in-progress Spectra changes?

Managing parked Spectra changes requires handling state transitions. The workflow guides unpark and in-progress state transitions, prompting you to resolve ambiguity before proceeding with preflight checks and artifact analysis.

Do I need the spectra CLI to coordinate change management workflows?

Yes, the spectra CLI is required. The workflow integrates directly with the CLI to query status, retrieve instructions, and execute tasks, enforcing a file-based progress model for disciplined development.

How does the workflow handle preflight checks and artifact analysis?

The workflow performs preflight checks and artifact analysis to surface issues before execution. It interactively prompts you when critical findings or ambiguities arise, ensuring safe task implementation.

Why does my Spectra task tracking require a dedicated tasks file?

A dedicated tasks file enforces a file-based progress model. It serves as the single source of truth for task tracking, ensuring disciplined development workflows and preventing lost state during change application.