execute

Execute implementation plans with precondition validation, TDD, and Git commits.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/usorama/engg-support-system --skill execute-usorama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: execute
Source: https://github.com/usorama/engg-support-system/tree/main/.claude/skills/execute
Command: npx skills add https://github.com/usorama/engg-support-system --skill execute-usorama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides deterministic execution of implementation plans with verifiable outcomes, reducing drift and human error across engineering tasks.

Core Features & Use Cases

  • Deterministic Execution: ensures identical inputs produce identical outputs with full traceability.
  • Precondition Validation & TDD Workflow: validates prerequisites, creates and runs tests before implementation.
  • Postcondition Verification & Evidence Capture: typechecks, tests, and evidence are captured and persisted; progress is updated across sessions.
  • Cross-Project Context Sharing: supports memory-keeper based cross-session state sharing and Git-based progress.
  • Use Case: used to implement IMPLEMENTATION-PLAN.md files with triple verification and rigorous git workflows in rad-engineer-v2 and engg-support-system.

Quick Start

To begin, run the execute skill to automatically determine and execute the next task, validating preconditions, running tests, and updating progress. For example: /execute would identify the next pending task and perform the full verification loop. After completion, check the progress log and memory-keeper for the updated state.

Frequently Asked Questions about execute

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

FAQPage Schema
How do I execute an implementation plan deterministically to guarantee repeatable outcomes?▼

Deterministic plan execution validates preconditions, creates tests before implementation, verifies postconditions via typecheck, and captures evidence to guarantee identical inputs produce identical outputs with full traceability.

How does test-driven development workflow integrate with git commits for engineering tasks?▼

The test-driven development workflow enforces creating and running tests before implementation, validates postconditions, and persists progress using rigorous git-based commits after each task completion.

What is the best way to maintain engineering progress across multiple sessions and projects?▼

Cross-project context sharing uses a memory-keeper to maintain cross-session state and git-based progress, ensuring multi-project engineering environments stay synchronized without drift.

Do I need an IMPLEMENTATION-PLAN.md file to start automated plan execution?▼

Yes, automated plan execution processes IMPLEMENTATION-PLAN.md files by identifying the next pending task, validating prerequisites, running tests, and updating the progress log upon completion.

How does precondition validation reduce human error in software engineering workflows?▼

Precondition validation reduces human error by verifying prerequisites before implementation, enforcing test-driven development, and capturing verifiable evidence to prevent drift across engineering tasks.