spec-kitty-status

Track and verify Spec-Kitty workflow states with provenance-aware checks.

5|3|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/richfrem/agent-plugins-skills --skill spec-kitty-status
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-kitty-status
Source: https://github.com/richfrem/agent-plugins-skills/tree/main/plugins/spec-kitty-plugin/skills/spec-kitty-status
Command: npx skills add https://github.com/richfrem/agent-plugins-skills --skill spec-kitty-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables teams to monitor and keep Spec-Kitty workflow status accurate without manual checks, ensuring alignment with the baseline workflow.

Core Features & Use Cases

  • Status retrieval and provenance-aware reporting for SPEC-KITTY workflows.
  • Wrapper around the spec-kitty agent shim to consistently surface current state.
  • Scenarios: routine status reviews, debugging workshops, and automated health checks.

Quick Start

Ask the Spec-Kitty status checker to report the current workflow state.

Frequently Asked Questions about spec-kitty-status

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

FAQPage Schema
How do I track workflow status across multiple agents and prompts?▼

Retrieve workflow state using a status wrapper around the agent shim to consistently surface current state. It accepts agent shim results as authoritative, non-recomposed context for accurate reporting.

How do I verify workflow outputs match the latest baseline?▼

Automated health checks use provenance-aware reporting to verify workflow outputs against the latest baseline. This replaces manual status reviews with consistent, automated state tracking across agents.

What is provenance-aware reporting for workflow orchestration?▼

Provenance-aware reporting for workflow orchestration validates that current state outputs originate from the latest baseline. It tracks and verifies status across agents to prevent stale or misaligned results.

Can I use agent shim results as authoritative workflow context?▼

Agent shim results can be accepted as authoritative and non-recomposed context. The status wrapper treats these results as the definitive source for tracking and reporting current workflow state.

Why does my workflow status show outdated outputs during debugging?▼

Workflow status shows outdated outputs during debugging when provenance checks are not applied. Tracking state across agents requires validating that results reflect the latest baseline workflow rather than stale context.