executing-plans-extras

Verify CLI command execution against output, state changes, and exit codes.

1|Updated Dec 13, 2025

Search Tags:#CI/CD #automated testing #execution plan #state transition #CLI verification

Ready to run

npx skills add https://github.com/stephendor/TDL --skill executing-plans-extras-stephendor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: executing-plans-extras
Source: https://github.com/stephendor/TDL/tree/main/.agents/skills/executing-plans-extras
Command: npx skills add https://github.com/stephendor/TDL --skill executing-plans-extras-stephendor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the issue of verifying that CLI commands specified in an implementation plan are executed correctly, even when exit status alone might not be sufficient to confirm successful execution or state transition.

Core Features & Use Cases

Exact-Command Verification: Ensures that every command named in a plan is executed as specified, checking for required output, state changes, and exit codes.
Pre-Delivery Check: Re-runs commands and verifies their declared evidence, ensuring that tasks are not marked complete based on internal function tests alone.
Use Case: When implementing a plan that includes exact CLI commands, this Skill can be used to confirm that the commands executed as intended, providing a safety net against silent failures.

Quick Start

Run the executing-plans-extras skill to verify that the specified CLI commands have executed correctly and have produced the expected results.

Frequently Asked Questions about executing-plans-extras

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

FAQPage Schema

How do I verify CLI commands and state transitions in an execution plan?▼

To verify CLI commands and state transitions in an execution plan, you can run this Skill to check that exact commands executed as specified. It validates required output, state changes, and exit codes to ensure successful execution.

How can I prevent silent failures when running automated testing CLI commands?▼

To prevent silent failures during automated testing, this Skill re-runs commands and verifies their declared evidence. It ensures tasks are not marked complete based solely on exit status or internal function tests, guarding against undetected execution errors.

Does CI/CD pipeline verification require checking command output beyond exit codes?▼

Yes, CI/CD pipeline verification often requires checking command output beyond exit codes. This Skill confirms successful execution by asserting specified output, state changes, and exit codes together, preventing false positives from zero-exit silent failures.

What is the best way to confirm exact CLI command execution before delivery?▼

The best way to confirm exact CLI command execution before delivery is to use this Skill as a pre-delivery check. It re-runs the specified commands and verifies their declared evidence, ensuring tasks are not prematurely marked complete.

Do I need a specific command execution environment to assert command outcomes?▼

Yes, you need access to a command execution environment to assert command outcomes. This Skill requires the ability to execute commands and verify their results, making it suitable for CI/CD pipelines, automated testing, and deployment workflows.

Why does my deployment workflow show success when state changes failed to apply?▼

Your deployment workflow might show success when state changes failed because exit status alone is insufficient to confirm execution. This Skill checks for specified output and state changes, providing a safety net against silent failures in deployment workflows.