pair-programming

Structure AI-assisted coding into approval-gated pair-programming with verification gates.

Updated Mar 26, 2026

Search Tags:#debugging #pair programming #architecture planning #scope control #approval workflow #visual explanations #AskUserQuestion

Ready to run

npx skills add https://github.com/leodiegues/skills --skill pair-programming-leodiegues

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pair-programming
Source: https://github.com/leodiegues/skills/tree/main/skills/pair-programming
Command: npx skills add https://github.com/leodiegues/skills --skill pair-programming-leodiegues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a structured, approval-gated pair-programming workflow that prevents accidental edits and reduces iteration chaos during coding, planning, refactoring discussions, debugging, and technical decision-making.

Core Features & Use Cases

Approval is mandatory: requires explicit approval for a concrete plan and stops execution after each approved chunk.
Clarity-first planning: asks for approval only after communicating the why, tradeoffs, and what the user might not know.
Visual-first communication: uses diagrams and concise code snippets to fit an ADHD/visual learning communication style.
Clarifications via tool: uses the AskUserQuestion tool (one question per call) to resolve ambiguity without messy menus.

Quick Start

Tell your AI to use pair-programming and to ask one clarifying question (via AskUserQuestion) if any ambiguity blocks a plan.

Frequently Asked Questions about pair-programming

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

FAQPage Schema

How do I stop AI from making accidental edits and causing scope drift during pair programming?▼

An approval-gated pair programming workflow stops accidental edits by requiring explicit plan approval and pausing execution after each approved chunk, preventing unsafe code changes and scope drift.

What is the best way to structure technical planning and architecture discussions with AI?▼

Structure technical planning by requiring the AI to communicate the why, tradeoffs, and unknowns before asking for approval, ensuring architecture discussions remain clear and bounded before execution begins.

How do I clarify ambiguities during a refactoring or debugging workflow without messy menus?▼

Resolve ambiguities during refactoring or debugging by using the AskUserQuestion tool, which asks a single clarifying question per call to eliminate confusion without messy menus.

Can I use visual explanations and diagrams for technical decisions if I have an ADHD learning style?▼

Yes, visual-first explanations use diagrams and concise code snippets specifically designed to fit ADHD and visual learning styles, making technical decisions and code changes easier to follow.

How do I enforce verification gates before completing code execution chunks?▼

Enforce verification gates by integrating an approval workflow that stops execution after each approved chunk, requiring verification before the AI proceeds to the next step of the coding task.

What are the limitations of using an approval-gated workflow for quick coding tasks?▼

Using an approval-gated workflow for quick coding tasks introduces mandatory pauses for plan approval and verification gates, which may slow down rapid execution for trivial changes.