Pair Programming Workflow
An 8-phase, approval-gated pair programming workflow: understand requirements, write a spec, implement in vertical slices, review, then keep spec and code in sync.
Dev & CodingBeginner★ 173⑂ 40AI score 8/10Last updated: Aug 26, 2026
What it does
- Makes the agent behave like an experienced pair programming partner instead of an autonomous code generator.
- Enforces an 8-phase workflow: ①Feature discovery (understanding summary) → ②Written specification in a Markdown file → ③Implementation plan (vertical slices, not layers) → ④Step-by-step implementation → ⑤Code review → ⑥Refinement loop → ⑦Spec/implementation synchronization → ⑧Delivery summary.
- Every phase ends with a numbered choice menu (approve / request changes / ask questions / cancel) and the agent must wait instead of continuing automatically.
- Assumptions must be listed explicitly and confirmed; no silent guessing. Ambiguous requirements trigger questions before any code.
- Also encodes collaboration tone: healthy skepticism, light humor, admitting uncertainty, and balanced code reviews with a checklist (architecture, naming, validation, tests, security...).
Who it's for
- Developers tired of the model dumping large diffs before understanding the requirement.
- Teams that work spec-first and want documentation to stay aligned with code.
- Anyone who wants features broken into small, reviewable increments.
- Leads who want to instill checklist-based review habits.
Examples
- "Let's add social login" → the agent asks about users, happy path, edge cases and constraints, prints an Understanding Summary, then asks whether to write a spec.
- After spec approval → it proposes
auth endpoint → session persistence → frontend login flow → tests → docsand implements only one slice per approval. - When implementation drifts from the spec → phase 7 diffs them and updates the spec file with Added / Changed / Removed sections.
· · · Install guide · · ·
Try it now, no install
Paste this into Claude to use the skill without installing anything.
Read the instructions in this file and follow them to help me: https://raw.githubusercontent.com/sivaprasadreddy/sivalabs-agent-skills/HEAD/skills/pair-programming/SKILL.md What I want: (describe your task here)
If Claude can't open the link, open it yourself and paste the contents instead.
↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the skills/pair-programming folder from the GitHub repo sivaprasadreddy/sivalabs-agent-skills into my ~/.claude/skills/pair-programming/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/sivaprasadreddy/sivalabs-agent-skills.git /tmp/sivalabs-agent-skills && mkdir -p ~/.claude/skills && cp -r /tmp/sivalabs-agent-skills/skills/pair-programming ~/.claude/skills/⚠ This is a third-party skill. Check the source repository before installing.
- Open a terminal.
- Clone the repository:
git clone https://github.com/sivaprasadreddy/sivalabs-agent-skills.git - Create the skills directory:
mkdir -p ~/.claude/skills - Copy just this skill:
cp -r sivalabs-agent-skills/skills/pair-programming ~/.claude/skills/ - Verify that
~/.claude/skills/pair-programming/SKILL.mdexists. - Restart Claude Code.
- The skill sets
disable-model-invocation: true, so it will not auto-trigger — invoke it by name, e.g. "use the pair programming skill for this feature". - For a single project only, copy the folder into that project's
.claude/skills/directory instead.
View source on GitHub ↗License: MIT