skills.rest
Auto-one-Family
Auto-one-FamilyCOMMUNITY
Explore all skills by this author →
GitHub

verify-plan

Validate TM plans against repository and runtime configuration for mismatches.

Updated Aug 23, 2026
Search Tags:#docker#config-validation#plan-validation#api-endpoints#agent-validation#tm-plan
One-click install
npx skills add https://github.com/Auto-one-Family/Automation-One --skill verify-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-plan
Source: https://github.com/Auto-one-Family/Automation-One/tree/main/.claude/skills/verify-plan
Command: npx skills add https://github.com/Auto-one-Family/Automation-One --skill verify-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a final technical sanity check for Technical Manager (TM) plans by comparing plan assertions to the real repository layout, runtime configuration, and available agents and services to prevent failed or dangerous executions.

Core Features & Use Cases

  • Path validation: Verifies referenced files and directories, suggests nearest matches, and reads sample file contents when available.
  • Agent & Skill validation: Confirms referenced agents and skills exist, checks tool capabilities and registration.
  • Docker & config checks: Cross-checks docker-compose overlays, service names, ports, environment variables, and health endpoints.
  • API and MQTT validation: Validates referenced REST endpoints, WebSocket events, and MQTT topic patterns against repository reference docs.
  • Inline corrections: Produces precise, minimal edits in plan files or a structured chat report listing confirmations, required fixes, missing prerequisites, and recommendations.

Quick Start

Run verify-plan on a TM plan or provide the plan file path and receive a prioritized, precise reality-check with inline corrections or a chat report.

Frequently Asked Questions about verify-plan

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

FAQPage Schema
How do I validate a technical plan against my actual repository configuration?▼

Plan validation compares referenced file paths, docker-compose services, and environment variables against the actual codebase layout and runtime configuration. This reality-check process detects mismatches in paths, agents, services, and configs, returning precise inline corrections or a structured report of required fixes.

How do I check if my docker-compose services and environment variables match my deployment plan?▼

Checking docker-compose services and environment variables against a deployment plan requires cross-referencing service names, ports, and .env values. Config validation confirms alignment between the plan and docker-compose overlays, verifying health endpoints and returning exact corrections for any misaligned environment variables or service definitions.

Can I verify MQTT topics and REST API endpoints referenced in my execution plan?▼

You can verify MQTT topics and REST API endpoints by validating referenced patterns against repository reference docs. API validation checks WebSocket events, REST endpoints, and MQTT topic patterns to ensure existence and correctness, returning a prioritized report listing confirmations, missing prerequisites, and required fixes for the referenced resources.

What's the best way to confirm agent and skill registration before executing a TM plan?▼

Confirming agent and skill registration before execution involves checking tool capabilities and verifying that referenced agents exist in the repository. Agent validation confirms registration and checks tool capabilities, returning a structured chat report listing confirmations, required fixes, and missing prerequisites to prevent failed or dangerous executions.

Does plan validation work for pre-execution reviews of operator instructions and TM briefings?▼

Plan validation works for pre-execution reviews of operator instructions, TM briefings, and any plan referencing file paths, agents, docker services, or MQTT topics. It ensures the existence and correctness of referenced resources, providing a final technical sanity check to prevent failed executions by comparing plan assertions to the real repository.

Why does my TM plan execution fail when it references non-existent file paths and configs?▼

TM plan execution fails when file paths and configs do not exist in the actual repository layout. Path validation verifies referenced files and directories, suggests nearest matches, and reads sample file contents when available, returning exact corrections or inline edits for plan files to prevent these execution failures.

Related Skills

Explore More Software Engineering Skills→
podversepodverse
6

lighthouse-docker-sync

Align Lighthouse Docker services with infra docker-compose and env file changes.

Official
Intermediate
tae2089tae2089
2

agent-team-ops

Inspect runs, messages, and events and finalize runs without executing agents.

Community
Intermediate
almazomalmazom

contabo-skill

Automate project deployment to Contabo VPS via SSH and docker-compose.

Community
Intermediate
CaptainPhantasyCaptainPhantasy

env-validate

Scan code for getenv calls and flag undocumented environment variables.

Community
Intermediate