Compose spec-kit, ooo, and cli-anything into a repeatable spec-driven delivery workflow.
npx skills add https://github.com/akillness/jeo-skills --skill spec-stack
Please help me install this Agent Skill. Skill: spec-stack Source: https://github.com/akillness/jeo-skills/tree/main/.agent-skills/spec-stack Command: npx skills add https://github.com/akillness/jeo-skills --skill spec-stack
Spec-stack unites spec-kit, ouroboros, and cli-anything into a single repeatable workflow that streamlines spec-driven delivery across documentation, verification, and harness execution.
Install the stack using the installer script and bootstrap a full-stack workflow by writing a spec, freezing the seed, and arming the CLI harnesses.
High-intent search queries and answers about installing and using this skill.
Spec-driven delivery automation unites spec-kit, ouroboros, and cli-anything into a single workflow. It enforces a one-way flow where spec-kit writes documentation, ooo freezes the seed, and cli-anything executes harnesses to yield verifiable software artifacts.
The write freeze run loop is a repeatable spec-driven workflow. spec-kit writes the initial specification, ooo freezes the seed for immutable verification, and cli-anything executes the harnesses, ensuring machine-checkable acceptance criteria across real software.
Yes, spec-stack explicitly requires a registry-backed tool chain to operate. This infrastructure provides the registry-backed tools, explicit handoffs, and documented patterns necessary to enforce the one-way flow across the documentation, freezing, and execution layers.
Yes, spec-stack supports three patterns to match project maturity: full-stack, loop-only, and docs-only. The docs-only pattern allows teams to leverage spec-kit for documentation without arming the cli-anything execution harnesses or running the ooo seed loop.
Seed-based verification is best handled by freezing specifications with ooo before execution. This creates an immutable seed loop that enforces machine-checkable acceptance criteria and generates artifact-level evidence when cli-anything runs the execution harnesses.
You should avoid a one-way spec-driven flow if your project requires iterative, bidirectional updates between execution and documentation. spec-stack enforces a strict one-way flow where spec-kit writes, ooo freezes, and cli-anything executes without reverse handoffs.
dawsonblockDiscover and install agent-native CLI tools from a centralized catalog.
ql-linkConverts frozen brief.md files into Gherkin-based acceptance.feature for pytest-bdd.
SorinSAutomate Spec-Driven Development planning phases and generate design artifacts.
amadeus-dlcExecute the observability-setup stage as a standalone workflow run.
