Spec-Lint Checklist for specs/CONTRACT.md Patches

Validate specs/CONTRACT.md patches for normative requirements and acceptance criteria.

1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/speelbreaker/ralph-trader --skill spec-lint-checklist-for-specs-contract-md-patches
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Spec-Lint Checklist for specs/CONTRACT.md Patches
Source: https://github.com/speelbreaker/ralph-trader/tree/main/SKILLS/spec_lint_checklist
Command: npx skills add https://github.com/speelbreaker/ralph-trader --skill spec-lint-checklist-for-specs-contract-md-patches

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive, battle-tested checklist to validate patches to specs/CONTRACT.md, ensuring consistency, safety, and test coverage across governance documents.

Core Features & Use Cases

  • Enforces single source of truth for rules and cross‑references to prevent duplication and drift.
  • Detects duplicate enumerations and promotes centralized definitions.
  • Requires acceptance tests for every normative requirement (MUST / SHALL / REQUIRED) and provides guidance on AT blocks.
  • Enforces patch hygiene by labeling and accounting for section references, cross-references, and patch minimality.
  • Tracks cross‑reference validity and drift to maintain contract integrity.
  • Guides handling of threshold changes and boundary testing in contracts.

Quick Start

Review a patch to specs/CONTRACT.md using the checklist:

  • Scan for pasted normative language (MUST, SHALL, REQUIRED) and ensure an AT‑### block exists.
  • Verify there is a single canonical source for each rule and that cross‑references are valid.
  • Check for new or renamed terms and confirm they are defined and test-bound.
  • Confirm patch changes are minimal and well-scoped to reduce churn.

Frequently Asked Questions about Spec-Lint Checklist for specs/CONTRACT.md Patches

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

FAQPage Schema
How do I validate acceptance tests for MUST and SHALL rules in a contract patch?

To validate contract patches, scan for normative language like MUST, SHALL, or REQUIRED and ensure a grammatically defined AT block exists for each rule. This guarantees must-have test coverage and maintains governance integrity.

What is a spec-lint checklist and when do I need it for specs/CONTRACT.md?

A spec-lint checklist is a validation framework for contract patches that enforces single source of truth, duplicate rule detection, and cross-reference integrity. You need it when modifying governance documents to prevent drift and ensure test coverage.

How do I check cross-reference validity and prevent duplicate rules in contract patches?

Check cross-reference validity by verifying all section references point to existing definitions and detecting duplicate enumerations. Promote centralized definitions to enforce a single canonical source for each rule and prevent drift.

How to handle threshold changes and boundary testing in governance contract patches?

Track threshold changes by adding boundary tests to the acceptance test blocks within the contract patch. This ensures that modified values or limits in the governance document are properly validated and test-bound.

What are the patch hygiene requirements for minimal churn in contract updates?

Patch hygiene requires labeling and accounting for section references, verifying cross-references, and confirming changes are minimal and well-scoped. This reduces patch churn while preserving the overall governance integrity.

Can I use this spec-lint framework for single-source-of-truth enforcement on large governance specs?

Yes, the framework enforces single-source-of-truth by detecting duplicate enumerations and promoting centralized definitions. It is designed to maintain cross-reference integrity and drift control across rigorous contract patches.