expectations

Enforce TDD, documentation, and communication guidelines for software projects.

21|6|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/mintuz/claude-plugins --skill expectations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expectations
Source: https://github.com/mintuz/claude-plugins/tree/main/plugins/core/skills/expectations
Command: npx skills add https://github.com/mintuz/claude-plugins --skill expectations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies working agreements, TDD expectations, and documentation practices to improve code quality, reduce ambiguity, and streamline team collaboration.

Core Features & Use Cases

  • TDD-first discipline: Ensures changes begin with tests and that production code is not added without a failing test.
  • Documentation framework: Guides maintainers to capture decisions and learnings in project docs and CLAUDE.md.
  • Explicit communication: Encourages explicit rationale, trade-offs, and consistency across changes.

Quick Start

Instruct Claude to enforce the Expectations guidelines on the current task and to update CLAUDE.md with a concise summary of decisions and learnings.

Frequently Asked Questions about expectations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce TDD rules and document project decisions in Claude?

You can enforce TDD rules and document decisions by instructing Claude to apply codified working agreements, ensuring production code follows failing tests and learnings are captured in CLAUDE.md.

What is the best way to maintain a CLAUDE.md file with project learnings and trade-offs?

Maintaining a CLAUDE.md file requires capturing concise summaries of decisions and learnings after code changes. This skill provides a documentation framework to guide maintainers in recording project rationale and trade-offs.

How do I ensure code changes start with failing tests during PR reviews?

To ensure code changes start with failing tests, apply a TDD-first discipline that blocks production code additions without an initial failing test, guiding both code changes and PR reviews.

Can I use this TDD and documentation framework for software projects of any size?

Yes, this TDD and documentation framework applies to software projects of all sizes. It guides code changes, PR reviews, and documentation updates to reduce ambiguity and streamline team collaboration.

How do I codify working agreements and communication expectations for a development team?

Codify working agreements and communication expectations by enforcing explicit rationale, consistency across changes, and a documentation framework that captures decisions. This reduces ambiguity and improves code quality.