skills.rest
davidlee
davidleeCOMMUNITY
Explore all skills by this author →
GitHub

sub-driver

Query and create spec-driver project memories with a minimal operational vocabulary.

26|3|Updated Oct 9, 2025
Search Tags:#memory management#glossary#spec-driver#agent tooling#dispatch workers#governance boundaries#tui workflow
One-click install
npx skills add https://github.com/davidlee/spec-driver --skill sub-driver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sub-driver
Source: https://github.com/davidlee/spec-driver/tree/main/.spec-driver/skills/sub-driver
Command: npx skills add https://github.com/davidlee/spec-driver --skill sub-driver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps dispatch workers quickly understand and operate within a spec-driver project by providing the minimum vocabulary, commands, and boundaries needed to navigate artifacts safely and consistently.

Core Features & Use Cases

  • Operational fluency for dispatch workers: Defines a small, practical command set focused on memory operations rather than full workflow boot ceremony.
  • Shared spec-driver glossary: Aligns terminology across teams and agents (e.g., Delta, Design revision, Implementation plan, verification types) to reduce ambiguity.
  • Clear safety boundaries: Explicitly constrains what the worker can and cannot do, preventing unauthorized artifact writes and scope creep.

Quick Start

Ask the AI to use the sub-driver skill to create or query a memory for a specific file path inside your spec-driver workspace.

Frequently Asked Questions about sub-driver

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

FAQPage Schema
How do dispatch workers navigate spec-driver projects without full workflow ceremony?▼

Dispatch workers navigate spec-driver projects using a minimal, safe operational vocabulary centered on memory management to read governance context and determine next steps within an assigned scope.

What glossary terms do agents use for spec-driver revisions and verification artifacts?▼

Agents use a shared spec-driver glossary with consistent terminology for delta, design revisions, implementation plans, and verification artifacts to reduce ambiguity across teams.

Can a dispatch worker write artifacts or perform commits in a spec-driver workspace?▼

No, dispatch workers face explicit governance boundaries that prevent unauthorized artifact writes, commits, and scope creep, constraining them to safe memory queries and creation commands.

How do I create or query memory for a specific file path inside a spec-driver workspace?▼

You create or query memory for a specific file path by asking the AI to use the sub-driver skill, which executes memory operations without full orchestration boot ceremony.

What are the limitations of using a minimal operational vocabulary for agent tooling?▼

The minimal operational vocabulary is limited to memory management and queries, restricting agents from performing full orchestration, workflow ceremony, or writing artifacts outside their assigned scope.

Related Skills

Explore More Software Engineering Skills→
maestria-comaestria-co

initialize-workspace

Bootstrap per-project agent context across a VS Code multi-root workspace.

Official
Advanced
kunishkunish

openspec-continue-change

Guide creation of the next OpenSpec workflow artifact via CLI steps.

Community
Advanced
gtpgg1013gtpgg1013

team-tui

Run parallel TUI component, hook, and integration tests during team verify.

Community
Advanced
fusebase-devfusebase-dev
6

find-wasted-effort

Audit FuseBase Flow artifacts for outcome-neutral process ceremony waste.

Official
Advanced