SkillSpec Visual Explainers

July 1, 2026 ยท View on GitHub

This folder is the visual, narrative layer for SkillSpec. The design docs under docs/design/ explain the contract in detail; these explainers show the same ideas as small workflow diagrams that can be read independently.

Use this folder when someone needs to understand the shape of the system before reading the full design docs.

One-Screen Map

flowchart LR
    A[Import to release] --> B[Runtime trampoline]
    B --> C[Router mode]
    B --> D[Durable executor]
    C --> E[less skill context in prompt]
    D --> F[less execution evidence in prompt]

The first two explain the lifecycle of one SkillSpec-backed skill. The last two explain how SkillSpec scales when many skills or tool-backed executions enter the picture.

Reading Order

OrderExplainerUse It To Explain
01Import To ReleaseHow a prose skill becomes a reviewed, tested, releasable SkillSpec-backed skill without loading the entire source or spec into context.
02Runtime Trampoline And AlignmentHow the thin SKILL.md loader keeps the agent inside skill.spec.yml, then uses plan, act, progress evidence, quiet trace alignment, and proof-digest batching as an OODA loop.
03Router ModeHow router mode controls skill explosion with an implicit router, explicit-only routed skills, read-only status, reversible enable/disable switches, and a rebuilt index.
04Durable ExecutorHow durable-executor acts as the optional first-hop for tool-backed work, preserving evidence, token stats, reusable workspace history, and local capability seeds.

How These Fit The Main Docs

Start here for quick explanation, then read the deeper design doc:

Visual TopicDeeper Design Docs
Import, source maps, scaffolding, release gatesSkill Authoring Lifecycle, Source Map Progressive Reader, Imports, Resources, Code, And Recipes, Design Documentation QA Process
Trampoline loader, OODA loop, progress, alignmentPackage Anatomy, Runtime Plan Act Progress Loop, Execution Progress Ledger, Traces And Alignment, Completion Alignment And Token Reporting
Router mode and skill catalog controlSkill Router, Command Log
Durable execution, capability seeds, and fallbackCapability Bootstrap, Command Log, Traces And Alignment, Completion Alignment And Token Reporting

Visual Style

Each explainer uses several small diagrams instead of one large architecture diagram. The intended review loop is:

author one small diagram
-> check whether each box maps to an implemented command or contract
-> fix wording and missing gates
-> move to the next diagram

If a diagram cannot be tied back to implementation, reference docs, or tests, it does not belong here.

Naming Rule

The file names describe the user-visible workflow, not internal modules:

  • import-to-release: the authoring path from prose to a reviewed skill.
  • runtime-trampoline-and-alignment: the installed-skill execution path.
  • router-mode: catalog and visibility control for many skills.
  • durable-executor: evidence-preserving first-hop execution and capability seed fallback.