execute

Execute GitHub issue implementation plans via atomic commits on a feature branch.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute an implementation plan from a GitHub issue by producing and applying a sequence of commits on a feature branch, enabling disciplined, traceable execution.

Core Features & Use Cases

  • Parse an issue to extract the design narrative, data model, capabilities list, implementation notes, and testing strategy.
  • Translate the plan into atomic commits that implement each capability, with alignment to the original design.
  • Support clarifying questions when design or plan gaps appear, ensuring a reliable handoff from planning to coding.

Quick Start

Provide a GitHub issue URL or number to begin executing the plan.

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 from a GitHub issue and apply commits to a feature branch?

To execute an implementation plan, provide the GitHub issue URL or number. The tool parses the issue's design narrative and data model, then translates the plan into atomic commits applied sequentially to a feature branch.

What does plan-driven development require in a GitHub issue before generating commits?

Plan-driven development requires a clearly defined implementation plan within the GitHub issue, including capabilities, data models, and testing strategies. If design gaps exist, the tool asks clarifying questions before producing commits.

Can I use GitHub issues for atomic commit management without manually writing the code?

Yes, you can use GitHub issues for atomic commit management by providing an issue number containing the design narrative. The tool translates the approved plan into a sequence of traceable commits on a feature branch automatically.

How to parse a GitHub issue to extract data models and testing strategies for code implementation?

Parsing a GitHub issue extracts the design narrative, data model, capabilities list, implementation notes, and testing strategy. This extracted information is then used to align atomic commits with the original design expectations.

What happens if my GitHub implementation plan has ambiguities or missing testing strategies?

If your GitHub implementation plan has ambiguities or missing testing strategies, the tool generates clarifying questions. This ensures a reliable handoff from planning to coding before applying any commits to the feature branch.

Does this approach support traceability between approved plans and feature branch commits?

Yes, this approach supports traceability by aligning each atomic commit with the original design narrative and capabilities list from the GitHub issue. This disciplined execution maintains clear links between the plan and the code.