Skip to content
Back to skills

Extreme Programming

ASecurity

Apply XP principles through simple evolving design, short feedback loops, and shared engineering responsibility.

  • 107 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 1, 2026
businessgorefactoring

Security analysis

A100/100

Scanned October 1, 2026

npx -y skills add smartfrog/opencode-froggy --skill extreme-programming --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Extreme Programming?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Extreme Programming
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/smartfrog-extreme-programming/badge)](https://www.skillsdirectory.com/skills/smartfrog-extreme-programming)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: extreme-programming
description: Apply XP principles through simple evolving design, short feedback loops, and shared engineering responsibility.
---

# Extreme Programming

- **Communication:** share objectives, acceptance examples, relevant context, and evidence so another agent can resume the work.
- **Simplicity:** apply KISS and YAGNI; reuse existing capabilities and evolve the simplest design meeting current needs.
- **Feedback:** verify assumptions early, integrate validated changes frequently, and adjust product decisions using actual user feedback. Use `tdd` for implementation and `backlog-management` for ticket workflow.
- **Courage:** report failed checks and uncertainty honestly; revise decisions when evidence changes.
- **Respect:** give specific, evidence-based feedback, preserve others' work, and bound investigation and correction costs.

Implementers own tests and ongoing refactoring. Reviewers and simplifiers provide targeted help. Follow shared project conventions; temporary scopes coordinate edits rather than establish permanent code ownership. A passing isolated branch is not proof of successful integration. Prefer reversible design decisions and distinguish production-ready changes from experimental findings.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.