Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
proffesor-for-testing avatar

Qe Xp Practices

  • 64 installs
  • 433 repo stars
  • Updated August 4, 2026
  • proffesor-for-testing/agentic-qe

qe-xp-practices is a Claude Code skill for ai & agent building.

About

qe-xp-practices is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • qe-xp-practices
  • AI & Agent Building
  • AI-coding skill

Qe Xp Practices by the numbers

  • 64 all-time installs (skills.sh)
  • +3 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #6,110 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill qe-xp-practices

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs64
repo stars433
Last updatedAugust 4, 2026
Repositoryproffesor-for-testing/agentic-qe

How do I helps with ai & agent building tasks.?

Helps with ai & agent building tasks.

Who is it for?

Best when you're working on ai & agent building and need structured help with qe xp practices.

Skip if: Teams with no ai & agent building needs, or anyone wanting a generic chat assistant without this specific workflow.

When should I use this skill?

When you need to helps with ai & agent building tasks., or when qe-xp-practices is a claude code skill for ai & agent building.

What you get

Structured output aligned to qe-xp-practices: qe-xp-practices, AI & Agent Building.

Files

SKILL.mdMarkdownGitHub ↗

Extreme Programming (XP) Practices

<default_to_action> When applying XP practices: 1. START with practices that give immediate value 2. BUILD supporting practices gradually 3. ADAPT to your context 4. MEASURE results

Core XP Practices (Prioritized):

PracticeStart HereWhy First
TDD✅ YesFoundation for everything
Continuous Integration✅ YesFast feedback
Pair Programming✅ YesKnowledge sharing
Collective OwnershipAfter CI+TDDNeeds safety net
Small ReleasesAfter CIInfrastructure dependent

Pairing Quick Start:

Driver-Navigator (Classic):
- Driver: Writes code
- Navigator: Reviews, thinks ahead
- Rotate every 20-30 min

Ping-Pong (with TDD):
A: Write failing test
B: Make test pass + refactor
B: Write next failing test
A: Make test pass + refactor

</default_to_action>

Quick Reference Card

The Five XP Values

ValueMeaningPractice
CommunicationEveryone knows what everyone doesDaily standups, pairing
SimplicitySimplest thing that worksYAGNI, small design
FeedbackGet feedback early and oftenTDD, CI, short iterations
CourageTell truth, adaptRefactor, admit mistakes
RespectEveryone contributes valueSustainable pace, pairing

Core Practices

PracticeDescriptionBenefit
Pair ProgrammingTwo devs, one workstationQuality + knowledge sharing
TDDRed-Green-RefactorConfidence + design
CIIntegrate multiple times/dayFast feedback
Collective OwnershipAnyone can change anythingNo bottlenecks
Sustainable Pace40-hour weeksLong-term productivity
Small ReleasesShip frequentlyRisk reduction

---

Pair Programming

When to Pair

ContextPair?Why
Complex/risky code✅ AlwaysNeeds multiple perspectives
New technology✅ AlwaysLearning accelerator
Onboarding✅ AlwaysKnowledge transfer
Critical bugs✅ AlwaysTwo heads better
Simple tasks❌ SkipNot worth overhead
Research spikes❌ SkipPair to discuss findings

Pairing Dos and Don'ts

Do:

  • ✅ Switch roles every 20-30 min
  • ✅ Take breaks together
  • ✅ Think out loud
  • ✅ Ask questions
  • ✅ Keep sessions 2-4 hours max

Don't:

  • ❌ Grab keyboard without asking
  • ❌ Check phone while pairing
  • ❌ Dominate conversation
  • ❌ Pair all day (exhausting)

---

Ensemble (Mob) Programming

Setup: 3+ developers, one screen, rotating driver

[Screen]
   ↓
[Driver] ← Directions from navigators
   ↑
[Navigator 1] [Navigator 2] [Navigator 3]

Rotation: Driver switches every 5-10 min

Best for:

  • Complex problem solving
  • Architectural decisions
  • Learning new frameworks
  • Resolving blockers

---

Continuous Integration

CI Workflow:

1. Pull latest from main
2. Make small change (<2 hrs work)
3. Run tests locally (all pass)
4. Commit and push
5. CI runs tests automatically
6. If fail → fix immediately

Best Practices:

  • Commit frequently (small changes)
  • Keep build fast (<10 min)
  • Fix broken builds immediately
  • Never commit to broken build

---

Four Rules of Simple Design

(In priority order) 1. Passes all tests - Works correctly 2. Reveals intention - Clear, expressive code 3. No duplication - DRY principle 4. Fewest elements - No speculative code

---

Agent Integration

// Agent-human pair testing
const charter = "Test payment edge cases";
const tests = await Task("Generate Tests", { charter }, "qe-test-generator");
const reviewed = await human.review(tests);
await Task("Implement", { tests: reviewed }, "qe-test-generator");

// Continuous integration with agents
await Task("Risk Analysis", { prDiff }, "qe-regression-risk-analyzer");
await Task("Generate Tests", { changes: prDiff }, "qe-test-generator");
await Task("Execute Tests", { scope: 'affected' }, "qe-test-executor");

// Sustainable pace: agents handle grunt work
const agentWork = ['regression', 'data-generation', 'coverage-analysis'];
const humanWork = ['exploratory', 'risk-assessment', 'strategy'];

---

Agent Coordination Hints

Memory Namespace

aqe/xp-practices/
├── pairing-sessions/*   - Pair/ensemble session logs
├── ci-metrics/*         - CI health metrics
├── velocity/*           - Team velocity data
└── retrospectives/*     - XP retrospective notes

Fleet Coordination

const xpFleet = await FleetManager.coordinate({
  strategy: 'xp-workflow',
  agents: [
    'qe-test-generator',   // TDD support
    'qe-test-executor',    // CI integration
    'qe-code-reviewer'     // Collective ownership
  ],
  topology: 'parallel'
});

---

Common Objections

ObjectionResponse
"Pairing is 2x slower"15% slower writing, 15% fewer bugs, net positive
"No time for TDD"Debugging takes longer than testing
"CI is hard to setup"Start simple: one action, one test
"Collective ownership = chaos"Only without tests + CI

---

Related Skills

  • tdd-london-chicago - TDD deep dive
  • refactoring-patterns - Safe refactoring
  • pair-programming - AI-assisted pairing

---

Remember

XP practices work as a system. Don't cherry-pick randomly:

  • TDD enables collective ownership
  • CI enables small releases
  • Pairing enables collective ownership
  • Sustainable pace enables everything

With Agents: Agents amplify XP. Pair humans with agents. Agents handle repetitive work, humans provide judgment and creativity.

Related skills

FAQ

What does qe-xp-practices do?

qe-xp-practices is a Claude Code skill for ai & agent building.

When should I use qe-xp-practices?

When you need to helps with ai & agent building tasks., or when qe-xp-practices is a claude code skill for ai & agent building.

What are the main capabilities?

qe-xp-practices; AI & Agent Building; AI-coding skill.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.