spae-prepare

Orchestrates spec, plan, and inspect subagents sequentially through the SPAE workflow phases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running the preparatory phases of the SPAE structured workflow (spec, plan, inspect) requires manually invoking each agent in the correct order and tracking state transitions. This Skill automates that orchestration by reading STATE.json and dispatching the right subagent at each phase until the workstream is ready for build. ## Core Features & Use Cases - State-driven dispatch: Reads .spae/current/STATE.json to determine the current phase and spawns the matching subagent (spec, plan, or inspect) with no arguments. - Bootstrap support: Accepts an optional proposal argument to initialize a new workstream by spawning the spec agent when no state file exists. - Stall and failure detection: Halts immediately on subagent failures, timeouts, unknown phases, or when the phase does not advance between iterations. - Use Case: You have a feature proposal and want the requirements distilled into SPEC.md, decomposed into PLAN.md, and gap-analyzed automatically. Invoke this Skill with your proposal and it drives the workstream to phase: build without further intervention. ## Quick Start Run the spae-prepare skill with my proposal to orchestrate the spec, plan, and inspect phases until the workstream reaches the build phase.

Frequently Asked Questions about spae-prepare

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

FAQPage Schema
How do I automate the spec, plan, and inspect phases of the SPAE workflow?▼

Invoke the spae-prepare skill with an optional proposal argument. It reads STATE.json, spawns the spec, plan, and inspect subagents in sequence, and halts when the workstream reaches phase build.

What happens if STATE.json is missing when running SPAE prepare?▼

If STATE.json is missing and no proposal argument is provided, the skill halts immediately. If a proposal is provided, it bootstraps the workstream by spawning the spec agent with that proposal verbatim.

Can spae-prepare run subagents in parallel or edit project files?▼

No. The skill operates strictly in read-only mode, spawns subagents sequentially one at a time, and never edits codebase files, tests, or documentation. It only invokes subagents and reads STATE.json.

Why does SPAE prepare halt during orchestration?▼

It halts when a subagent reports Failed status, crashes, or times out, when the phase does not change between iterations, or when the phase is not one of spec, plan, or inspect. This prevents stalled or invalid workflow states.

Which agents is the SPAE prepare skill allowed to invoke?▼

Only spec, plan, and inspect. The skill never invokes agents outside this permitted list, never activates other skills, and passes the proposal argument only to the initial bootstrap spec spawn.