shared-reference

Documents TDD, ATDD, and verification guidance for Claude Code planning tasks.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/smp4/claude-skills --skill shared-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shared-reference
Source: https://github.com/smp4/claude-skills/tree/main/dot_claude/skills/shared/reference
Command: npx skills add https://github.com/smp4/claude-skills --skill shared-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents Claude Code planning and execution from drifting by centralizing the TDD, ATDD, and verification references that /new-plan and /new-task need so everyone consults the same guidance instead of repeatedly re-explaining methodology.

Core Features & Use Cases

  • TDD Fundamentals: Captures the red-green-refactor loop, naming conventions, test structure, and persona heuristics from Kent Beck, Dave Farley, and Michael Feathers.
  • Verification Discipline: Documents acceptance criteria sweeps, full-suite runs, documentation audits, and verification-report templates needed to complete every SPEC, PLAN, and audit.
  • ATDD & Architecture Touchpoints: Houses the four-layer model, domain language rules, architectural fitness function guidance, stability patterns, and futher persona-specific review advice to keep plans evolvable.

Quick Start

Consult the shared reference library before drafting any SPEC or PLAN so the team aligns on TDD, ATDD, and verification expectations.

Frequently Asked Questions about shared-reference

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

FAQPage Schema
How do I centralize TDD and verification guidance for AI-assisted development planning?

Centralize TDD and verification guidance by consolidating red-green-refactor cycles, acceptance criteria sweeps, and fitness functions into a shared reference library that aligns SPEC and PLAN workflows on a single methodology.

What is the red-green-refactor cycle and how do acceptance criteria fit into verification?

The red-green-refactor cycle drives TDD by writing failing tests, making them pass, then cleaning code. Acceptance criteria fit into verification by defining the sweeps and full-suite runs needed to complete every audit.

How do I apply ATDD and the four-layer model when drafting development plans?

Apply ATDD and the four-layer model during planning by enforcing domain language conventions and architectural fitness functions, ensuring specifications remain evolvable and execution stays aligned with the intended design.

Does this shared reference library work with Claude Code /new-plan and /new-task workflows?

Yes, the shared reference library integrates directly with Claude Code /new-plan and /new-task workflows, providing the persona heuristics and verification report templates needed to keep planning and execution disciplined.

Why does my AI-assisted development planning drift without centralized verification discipline?

Planning drifts without centralized verification discipline because scattered reference materials cause teams to repeatedly re-explain methodology, leading to misaligned specifications and inconsistent test structure.

When should I consult the shared reference library to prevent methodology drift?

Consult the shared reference library before drafting any SPEC or PLAN, ensuring the team aligns on TDD, ATDD, and verification expectations prior to initiating the coding phase.