workflow-execute

Implements approved GitHub issue plans and publishes verification evidence for review.

Updated Dec 18, 2025
One-click install
npx skills add https://github.com/l0lxl0lw/dotfiles --skill workflow-execute-l0lxl0lw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-execute
Source: https://github.com/l0lxl0lw/dotfiles/tree/main/opencode/skills/workflow/workflow-execute
Command: npx skills add https://github.com/l0lxl0lw/dotfiles --skill workflow-execute-l0lxl0lw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns an approved plan for a GitHub issue into verified, reviewable code changes without scope drift, ensuring every implementation claim is backed by recorded check results rather than prose assertions. ## Core Features & Use Cases - Contract-bound implementation: Loads the exact approved plan and any supplied review via handoff packets, implements a coherent vertical slice, and refuses to infer scope from prior conversation. - Review-fix repair passes: Treats a supplied Review URL as a scoped repair against the same contract, recording each finding as fixed, disputed, or unresolved with evidence. - Evidence-based verification: Initializes a check manifest from the plan, runs recorded checks with fingerprints and logs, and publishes a Verification artifact that feeds directly into the review stage. - Use Case: After a plan for issue #42 is approved, run /execute to implement the changes in an isolated worktree, run the required checks, and publish a Verification URL ready for /review. ## Quick Start Ask the agent to execute the approved plan for a specific GitHub issue by providing the issue URL and plan URL, optionally with a review URL to fix.

Frequently Asked Questions about workflow-execute

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

FAQPage Schema
How do I execute an approved plan for a GitHub issue?

Invoke /execute with the issue URL and the approved plan URL. The skill loads the exact plan via a handoff packet, implements the changes in an isolated worktree, runs required checks, and publishes a Verification artifact for review.

How do I fix findings from a code review on GitHub?

Supply the changes-requested Review URL alongside the issue and plan. The skill treats it as a scoped repair pass, addressing actionable findings, adding regression tests, and recording each finding ID as fixed, disputed, or unresolved with evidence.

Does the execute step commit or push changes automatically?

No. The /execute stage authorizes only implementation and verification of the identified plan or fix. It stops before any commit, and a Needs sync indication is not permission to rebase without asking first.

Why is a verification run required instead of a summary of test results?

Prose claims cannot prove behavior. The skill records actual command exits, test and skip details, and environment fingerprints in a check manifest, producing a fetchable receipt that reviewers can trust or audit.

What happens if implementation reveals the plan's design is wrong?

The skill asks and records the deviation rather than silently changing the API contract. Material design changes require explicit confirmation, and a disputed material review finding returns to the review stage.