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

boot

Validate Spec-Driver boot context presence before agent work begins.

26|3|Updated Oct 9, 2025
Search Tags:#TUI#agent onboarding#spec-driver#context validation#workflow gating#preboot
One-click install
npx skills add https://github.com/davidlee/spec-driver --skill boot-davidlee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: boot
Source: https://github.com/davidlee/spec-driver/tree/main/.spec-driver/skills/boot
Command: npx skills add https://github.com/davidlee/spec-driver --skill boot-davidlee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures an agent has the required Spec-Driver boot context before doing any substantive work, preventing missing-state failures and unsafe routing.

Core Features & Use Cases

  • Mandatory onboarding enforcement: Guides you to verify the boot context is present in your context before proceeding.
  • Self-diagnosis and recovery: Detects when the preboot context is missing and tells you exactly how to generate it.
  • Correct work routing: After boot, instructs you to use /using-spec-driver for any substantive tasks to avoid acting without the proper framework state.

Quick Start

Verify you see the "Spec-Driver Boot Context" heading in context, and if not, run uv run spec-driver admin preboot so the required .agents/spec-driver-boot.md is available.

Frequently Asked Questions about boot

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

FAQPage Schema
How do I validate agent boot context before starting onboarding workflows?▼

To validate agent boot context, check for the Spec-Driver Boot Context heading in your context; if missing, run uv run spec-driver admin preboot to generate the required .agents/spec-driver-boot.md file before proceeding.

Why does my agent startup fail with a missing preboot artifact error?▼

Agent startup fails when the preboot artifact is missing because the boot context validation gates all substantive work; you must generate the .agents/spec-driver-boot.md file to resolve the BOOT ERROR and enable correct downstream behavior.

What is workflow gating in agent onboarding and when do I need it?▼

Workflow gating in agent onboarding ensures no substantive work begins until the Spec-Driver boot context is present, preventing missing-state failures and unsafe routing; it is needed whenever an agent requires preloaded framework state for correct operation.

How do I fix a BOOT ERROR when the Spec-Driver Boot Context heading is not found?▼

To fix a BOOT ERROR when the Spec-Driver Boot Context heading is missing, run uv run spec-driver admin preboot to generate the required preboot artifact, then verify the heading appears in context before routing work to /using-spec-driver.

Can I route substantive agent tasks without completing the preboot context check?▼

No, you cannot route substantive agent tasks without the preboot context check; the boot validation gates all subsequent work behind /using-spec-driver to ensure the agent operates with the proper Spec-Driver framework state loaded.

Does the boot context validator work without any external dependencies?▼

Yes, the boot context validator works without external dependencies; it performs context validation by checking for the Spec-Driver Boot Context heading and emitting remediation instructions, requiring only the spec-driver CLI to generate the preboot artifact.

Related Skills

Explore More Software Engineering Skills→
connor-git-yamlconnor-git-yaml
15

spec-driver-sync

Wrap Spec Driver mode in Codex to preserve artifacts and gates.

Community
Intermediate
davidleedavidlee
26

using-spec-driver

Route spec-driver tasks to the governing workflow skill before inspection or implementation.

Community
Basic
connor-git-yamlconnor-git-yaml
15

spec-driver-feature

Run the Spec Driver workflow inside Codex with preserved artifacts and gates.

Community
Advanced
limit5limit5

SKILL_HD_BRINGUP_LIVE_PARSE

Parse live boot console output to identify critical deployment blockers.

Community
Intermediate