spectra-apply

Apply Spectra change tasks to a codebase using Spectra CLI JSON output.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/howie/MiniShell --skill spectra-apply-howie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-apply
Source: https://github.com/howie/MiniShell/tree/main/.claude/skills/spectra-apply
Command: npx skills add https://github.com/howie/MiniShell --skill spectra-apply-howie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers need a reliable way to implement and track tasks defined in a Spectra change, handling parked changes, preflight warnings, and project‑specific preferences without using external task managers.

Core Features & Use Cases

  • Change selection: Automatically infer or prompt for the target change, including handling parked changes.
  • Status & preflight checks: Run Spectra CLI commands to fetch status, detect warnings or critical issues, and request user confirmation when needed.
  • Context loading: Reads all required context files (proposal, specs, design, tasks) based on the change schema.
  • Project preferences: Honors .spectra.yaml settings for TDD, audit discipline, and parallel task execution.
  • Task tracking: Updates markdown checkboxes in the tasks file as the sole source of truth.
  • Guardrails: Provides detailed prompts on ambiguous tasks, design gaps, or errors, and pauses execution for clarification.

Quick Start

Run /spectra-apply <change-name> to implement the tasks for a Spectra change.

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 change tasks to my codebase?

To apply Spectra change tasks, use the Skill to process active or parked changes via Spectra CLI JSON output. It loads context files, respects `.spectra.yaml` preferences, and updates markdown task checkboxes as tasks are completed.

How does Spectra handle project preferences like TDD during task application?

Spectra handles project preferences by reading the `.spectra.yaml` configuration file. It honors settings for TDD, audit discipline, and parallel task execution when applying change tasks to ensure compliance with project rules.

Do I need the Spectra CLI installed to apply change tasks?

Yes, the Spectra CLI with JSON support is required to apply change tasks. The Skill optionally uses the AskUserQuestion tool for interactive selections when handling ambiguous tasks or parked changes.

Can I apply Spectra changes that are currently parked?

Yes, you can apply parked Spectra changes. The Skill automatically infers or prompts for the target change, including those parked, and reads the required proposal, specs, design, and tasks files to proceed with implementation.

What happens if there are preflight warnings or design gaps when applying tasks?

When preflight warnings or design gaps occur, the Skill pauses execution and provides detailed prompts for clarification. It acts as a guardrail against ambiguous tasks or errors, requesting user confirmation before continuing.

What is the source of truth for tracking Spectra task progress?

The markdown tasks file is the sole source of truth for tracking Spectra task progress. The Skill updates markdown checkboxes directly in this file as implementation steps are completed, avoiding external task managers.