execute

Execute bounded tasks or plan slices and hand off to verify.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/scripness/skills --skill execute-scripness
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: execute
Source: https://github.com/scripness/skills/tree/main/src/execute
Command: npx skills add https://github.com/scripness/skills --skill execute-scripness

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables you to either implement a bounded task directly or execute the next bounded slice described in an explicit plan file, then run mechanical checks and hand off to verify.

Core Features & Use Cases

  • Direct-mode Execution: implement a bounded task quickly when the path is locally clear.
  • Plan-driven Execution: run one explicit milestone from plans/*.md, then update the plan state for later verify.
  • Verification Handoff: perform bounded mechanical checks and hand off results to the verify skill with explicit plan updates and blockers handling.

Quick Start

Provide one bounded task directly or run the next bounded plan slice, then perform mechanical checks and hand off to verify.

Frequently Asked Questions about execute

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

FAQPage Schema
How do I execute a bounded task slice from a plan file with automated checks?ā–¼

To execute a bounded task slice, the skill reads repo truth and the current plan context, implements one explicit milestone, runs mechanical checks, and updates the plan file with progress and blockers for downstream verification.

What is plan-driven workflow automation for bounded tasks?ā–¼

Plan-driven workflow automation processes one bounded slice from an explicit plan file at a time, ensuring mechanical checks run before handing off to verification, preventing guesswork when the next slice is under-specified.

How do I implement a bounded task directly when the path is locally clear?ā–¼

You can use direct-mode execution to implement a bounded task quickly when the path is locally clear, bypassing explicit plan files while still running mechanical checks and handing off to the verify skill.

Does workflow automation handle blockers and under-specified plan slices?ā–¼

Plan-driven execution explicitly avoids guessing when the next slice is under-specified, instead updating the plan file with encountered blockers and current progress to maintain accurate state for the verify skill.

What's the best way to track progress when executing milestones from a plan?ā–¼

Tracking progress during plan-driven execution involves updating the explicit plan file with completed milestones and blockers after running mechanical checks, ensuring the verify skill receives accurate context for validation.

Can I run mechanical checks after implementing a bounded slice without a full plan file?ā–¼

Yes, direct-mode execution allows you to implement a bounded task without a full plan file, performing bounded mechanical checks and handing off results directly to the verify skill for validation.