pr-run

Bind an issue's execution branch and worktree, then perform bounded implementation and validation.

4|1|Updated Feb 3, 2026

Search Tags:#validation #worktree #execution #traceability #branch #bind

Ready to run

npx skills add https://github.com/danielbaustin/agent-design-language --skill pr-run

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-run
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/pr-run
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill pr-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute a prepared issue after doctor review by binding its execution context and performing bounded work with truthful output recording, avoiding premature completion or janitoring.

Core Features & Use Cases

Bind or confirm the issue's execution branch and worktree just-in-time for execution.
Perform bounded implementation work and focused validations, then truthfully update the execution record.
Coordinate with doctor readiness results and maintain traceability for follow-up work.

Quick Start

Bind or confirm the issue's execution branch and worktree, perform the bounded implementation and validations, and truthfully update the execution record.

Frequently Asked Questions about pr-run

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

FAQPage Schema

How do I bind an execution branch and worktree to a prepared issue?▼

To bind an execution branch and worktree, the system establishes the execution context just-in-time, ensuring worktree surfaces like stp.md, sip.md, and sor.md are present before performing bounded implementation work.

What is bounded implementation work for issue execution?▼

Bounded implementation work confines development scope to the prepared issue's requirements, performing focused validations and truthfully updating the execution record to avoid premature completion or janitoring.

How do I maintain traceability when executing issues across branches?▼

Traceability is maintained by coordinating with doctor readiness results and updating the execution record per the run contract, ensuring all bounded work and validation outputs are tracked for follow-up tasks.

When do I need worktree validation before finishing an issue execution?▼

Worktree validation is required when a prepared issue has passed doctor readiness and needs branch binding, bounded implementation, and validation checks before finish to ensure truthful output recording.

Can I reuse existing execution bindings instead of creating new ones?▼

Yes, the execution process satisfies requirements for creating or reusing execution bindings, allowing you to confirm an existing issue's execution branch and worktree just-in-time for execution.

Why does issue execution require doctor readiness before binding?▼

Doctor readiness ensures the prepared issue is validated before binding its execution context, preventing premature completion and ensuring worktree surfaces are present for truthful output recording.