spae-inspect

Performs gap analysis on PLAN.md against SPEC.md and codebase constraints before task execution.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/mystilleef/spae-framework --skill spae-inspect-mystilleef
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spae-inspect
Source: https://github.com/mystilleef/spae-framework/tree/main/skills/spae-inspect
Command: npx skills add https://github.com/mystilleef/spae-framework --skill spae-inspect-mystilleef

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Plans written for AI-driven development often contain gaps: missing requirements, broken task dependencies, dangling task IDs, or vague acceptance criteria. This Skill inspects and refines a task plan before any code is written, catching structural and coverage problems early so execution phases run without rework. ## Core Features & Use Cases - Gap Analysis: Compares PLAN.md against SPEC.md and codebase patterns, classifying findings as Must fix, Should fix, or Observations. - Dependency Validation: Detects topological violations, dependency cycles, dangling T-NNN references, and mermaid graph mismatches, then renumbers tasks atomically. - State Management: Advances the SPAE workstream state from inspect to build, rebuilding the task registry in STATE.json with verified write-then-read persistence. - Use Case: After generating a plan from a specification, run this Skill to verify every requirement maps to a task, every task has testable acceptance criteria and an actionable intent, and the task graph is topologically ordered before build begins. ## Quick Start Run the inspect phase on the current SPAE workstream to validate and refine PLAN.md against SPEC.md before starting the build phase.

Frequently Asked Questions about spae-inspect

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

FAQPage Schema
How do I validate a task plan against a specification before implementation?▼

Run the inspect phase, which reads SPEC.md and PLAN.md, classifies every gap as Must fix, Should fix, or Observations, and refines the plan in place. It flags uncovered requirements, vague task intents, and missing test commands before any code is written.

How to detect dependency cycles and ordering violations in a task graph?▼

The inspection flags any dependency ID greater than or equal to the declaring task's own ID as a topological violation, and any task transitively depending on itself as a cycle. Fixes reorder tasks so every dependency precedes its dependent, then renumber all T-NNN references atomically.

What files does the SPAE inspect phase read and write?▼

It reads SPEC.md, PLAN.md, STATE.json, and relevant source files for context only. It writes only PLAN.md and STATE.json, never touching source code, tests, SPEC.md, or VERIFY.md.

Can the inspect phase modify the specification or source code?▼

No. The specification and all source files remain read-only during inspection. The Skill edits only PLAN.md and STATE.json, and any change must be grounded in a classified finding tied to SPEC.md or concrete codebase constraints.

What happens after the inspect phase completes?▼

STATE.json is updated atomically with phase set to build, the cursor set to task T-001, and the task registry rebuilt to mirror the refined plan. The write is confirmed by a fresh read before the result is reported.