A basic-design phase for deciding how a confirmed requirement should be built before implementation. It covers the system structure, data relationships, step-by-step behavior, and division of responsibilities through discussion.
A requirements-definition step used before designing or building a requested change. It clarifies the underlying reason, desired outcome, boundaries, and affected parts of the project.
A set of rules for working with the requester as a thinking partner while reaching a decision. It favors shared understanding and clear, complete wording over silently guessing what the requester means.
A guide for running end-to-end tests, which check a complete user journey through the application. It covers finding the project's instructions for setup, commands, continuous integration, and handling failures.
A guide for writing, editing, and reviewing end-to-end tests, which test a complete user journey through the application. It finds and follows the existing testing style for the part of the project being changed.
A Git workflow skill defines how coding work is branched, synchronized, committed, merged, and pushed. Git is a system for tracking code changes, while a worktree is a separate working copy of a repository.
A set of rules for writing documents that another agent can use without access to the original conversation. It requires the document to include the reasons, decisions, assumptions, limits, rejected options, completed checks, and likely next steps.
An implementation skill helps an agent follow the coding rules and architecture of the part of a project it changes. Architecture means the way a codebase is divided into parts and responsibilities.
An options skill compares several possible approaches to a design or implementation decision, showing their advantages, drawbacks, and one recommendation.
A structured research and experiment process for answering questions that block an important decision. It starts by agreeing on the decision to support, tests possible explanations including counterevidence, and reports a conclusion that can guide the next step.
A retrospective skill guides a review of completed work to identify improvements and record them in project rules or procedures. A retrospective is a structured look back at what happened and what should change next time.
A TDD implementation skill breaks coding work into small cycles: write a failing test, make it pass, review and improve the code, then commit it. TDD means test-driven development, where tests guide the implementation.
A user-story review skill checks whether each requirement is independent, valuable, small enough, and testable. A user story is a short description of something a user needs from a product.
A skill for turning software release notes into short announcements for a team. A release is a published version of software, usually identified by a tag or version number.
A pre-publication review step for material based on internal projects or experience. It checks for organization-specific names, identifiers, paths, and similar details before they enter a public Git repository.
A verification method for coding-agent skills, subagents, and instructions. It checks whether they start when expected and behave as intended by examining recorded sessions.
A project-specific guide for writing browser end-to-end tests with Playwright, a tool that controls a web browser. It encourages tests that read like plain-language specifications and use selectors based on what users see and do.
A set of rules for writing and changing React code in a project’s front-end, meaning the part users see and interact with. It covers component structure, types, exports, state, and where API requests belong.
A project-specific guide for writing API end-to-end tests: tests that run an API and check its behavior while WireMock, a tool that pretends to be an external API, supplies the outside responses.
A project-specific guide for managing a Kanban board, a view of work items grouped by status, in the xp-harness repository. Each independent piece of planned work is represented by a file in the kanban directory.
A set of principles for an XP development process, where XP means Extreme Programming, a method built around short work cycles, tests, reviews, and clear completion checks.
A release procedure for publishing a new version tag and GitHub Release for the xp-harness project. It uses semantic versioning, a numbering system where patch, minor, and major changes communicate the size and compatibility impact of a release.
A review mode that records each observation as a separate work item without debating it or assigning importance unless the reviewer explicitly does so.