mcpField
X
xp-practices

xp-practices

github.com/proffesor-for-testingDevelopment519119 installsUpdated today
Repository

About xp-practices

An Extreme Programming (XP) guide for software teams, describing how to adopt practices such as TDD, continuous integration, and pair programming incrementally. It also covers human-agent collaboration and dependencies among practices.

Key features

  1. 01Prioritize core XP practices
  2. 02Get started with pair programming
  3. 03Understand dependencies between practices
  4. 04Coordinate human-agent work
  5. 05Track sessions and practice metrics

Use cases

  1. 01Introduce XP practices incrementally
  2. 02Pair on complex or high-risk code
  3. 03Structure pairing around TDD
  4. 04Use agents to analyze change risk

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill xp-practices

After installing, type/xp-practicesin Claude Code to confirm it loaded.

Details

From the project README

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

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

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'
});

Related Skills


Remember

XP practices work as a system - TDD enables collective ownership, CI enables small releases, pairing enables collective ownership. Don't cherry-pick randomly.

With Agents: Pair humans with agents. Agents handle repetitive work (regression, data generation, coverage analysis), humans provide judgment and creativity.

Comments

Markdown supported