xp-practices

The xp-practices skill provides a structured framework for adopting Agile development methodologies within software engineering teams. It focuses on the core tenets of Extreme Programming (XP), such as Test-Driven Development (TDD), pair programming, ensemble programming, continuous integration, and sustainable pace. By integrating these human-centric workflows with automated quality engineering agents, teams can improve code quality, reduce technical debt, and ensure consistent delivery schedules. This skill is designed for engineering leads, scrum masters, and developers who aim to optimize their development lifecycle through disciplined, collaborative, and feedback-oriented processes. It bridges the gap between high-level Agile theory and daily implementation by providing actionable protocols for pairing, test-first development, and fleet-wide agent coordination.

• Facilitates TDD workflows, including Red-Green-Refactor cycles and automated test generation to ensure foundational code reliability.

• Orchestrates pair and ensemble programming sessions to maximize knowledge sharing, reduce knowledge silos, and improve overall system design quality.

• Integrates Continuous Integration (CI) and Small Releases strategies to provide rapid feedback loops and maintain system stability during frequent deployments.

• Coordinates specialized QE agent fleets, such as qe-test-generator, qe-test-executor, and qe-code-reviewer, to automate repetitive quality tasks and enforce collective ownership.

• Implements sustainable pace monitoring to track team velocity and retrospective data, preventing burnout while maintaining high technical standards.

• Begin with practices providing immediate value, such as TDD and CI, before expanding to collective ownership or small releases.

• Follow specific pairing patterns like Driver-Navigator or Ping-Pong to maintain focus and productive collaboration.

• Use the Memory Namespace feature to log pairing sessions, maintain CI health metrics, and store retrospective insights for continuous improvement.

• Always pair human judgment with agentic grunt work (e.g., data generation, coverage analysis, regression testing) to leverage both creativity and scalability.

• Context is critical: skip pairing for simple tasks or research spikes where deep individual focus is required, but mandate it for critical bugs, onboarding, and risky code refactors.