skills.rest
rjskene
rjskeneCOMMUNITY
Explore all skills by this author →
GitHub

execute-issue-plan

Execute approved GitHub issue implementation plans and open pull requests.

Updated Apr 10, 2026
Search Tags:#tdd#code review#implementation plan#github issues#pull request automation#playwright validation#ci fix
One-click install
npx skills add https://github.com/rjskene/pipeline --skill execute-issue-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: execute-issue-plan
Source: https://github.com/rjskene/pipeline/tree/main/skills/execute-issue-plan
Command: npx skills add https://github.com/rjskene/pipeline --skill execute-issue-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps convert an approved GitHub issue “Implementation Plan” into a complete, validated code change by executing the plan, running the required checks, and opening the corresponding pull request.

Core Features & Use Cases

  • Fetch and follow the approved Implementation Plan: Retrieves the latest plan comment section from the issue and executes only the ordered tasks it specifies.
  • Plan execution with safety guardrails: Supports different execution lanes (including CI-fix and quick-fix modes) while enforcing validation (typecheck, tests, and optional Playwright UI checks).
  • Pre-PR review and compliance loop: Runs author self-check plus an independent review and triages findings into must-fix commits before opening the PR.

Quick Start

Run /pipeline:execute-issue-plan <issue_number> from inside the feature worktree to implement the plan, validate it, and open the PR.

Frequently Asked Questions about execute-issue-plan

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

FAQPage Schema
How do I automate a GitHub issue implementation plan into a pull request?▼

To automate a GitHub issue implementation plan into a pull request, you execute the approved plan by running ordered tasks, enforcing red→green test discipline, validating types and UI, and opening a Conventional-Commits PR.

What is the best way to enforce TDD discipline when automating pull request creation from issues?▼

Enforcing TDD discipline during pull request creation requires gating commits on a strict red→green sequence, running pipeline typecheck and test commands, and performing code review loops before final PR approval and base-branch targeting.

Can I use Playwright validation for browser-predicate-driven GitHub issues before opening a PR?▼

Yes, you can use Playwright validation for browser-predicate-driven GitHub issues by optionally triggering UI checks during plan execution to ensure browser interactions pass before the automated pull request is created.

Does automated PR creation support CI-fix and quick-fix workflows for GitHub issues?▼

Automated PR creation supports CI-fix and quick-fix workflows by fetching the latest implementation plan comment, applying specific execution lanes, and running required pipeline test and typecheck commands before opening the pull request.

How do code review loops work when converting an implementation plan into a shipped PR?▼

Code review loops convert implementation plans into shipped PRs by running an author self-check and an independent review, triaging findings into must-fix commits, and gating PR creation on compliance checks.

Related Skills

Explore More Software Engineering Skills→
Hey-DigaHey-Diga
16

start-working-on-issue

Convert GitHub issues into pull requests using gh and git CLIs.

Official
Intermediate
HomericIntelligenceHomericIntelligence
18

verify-pr-ready

Validate GitHub Pull Requests for CI status, approvals, and merge conflicts.

Official
Intermediate
e-t-y-be-t-y-b
9

tdd-protocol

Enforce red-green-refactor TDD cycles across multi-agent coding environments.

Official
Advanced
renato0307renato0307
1

done

Commit changes, rebase on main, and create a pull request.

Community
Advanced