boyingliu01boyingliu01/xp-gate/skills/test-specification-alignment/AGENTS.md

xp-gate / test-specification-alignment

AGENTS.md4 starsChanged 6 months agoMITView on GitHub

Generated: 2026-11-04 Commit: eb2097b0 Branch: sprint/2026-11-03-02 Version: 0.37.0.0

Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- githooks/AGENTS.mdAGENTS.md
- plugins/AGENTS.mdAGENTS.md
- skills/delphi-review/AGENTS.mdAGENTS.md
- skills/sprint-flow/AGENTS.mdAGENTS.md
- admin-template-guidelinesSkill
- batch-grill-meSkill
- delphi-reviewSkill
- domain-modelingSkill
- grillingSkill
- grill-with-docsSkill
- improve-codebase-architectureSkill
- ralph-loopSkill
- sprint-flowSkill
- test-driven-developmentSkill
- test-specification-alignmentSkill
- to-issuesSkill

The file

We split this AGENTS.md into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Test-Specification Alignment Engine — two-stage validation ensuring tests accurately reflect requirements and design specs.
line 9
Distinctive:
Test annotations trace to REQ-XXX and AC-XXX
line 31
Distinctive:
Do NOT modify tests during Phase 2 execution
line 34
Distinctive:
Do NOT proceed with low alignment score (<80%)
line 35
Distinctive:
Do NOT skip specification validation if specification exists
line 36
Distinctive:
Do NOT delete test files in Phase 2 (freeze intercepts)
line 37
Distinctive:
Do NOT modify assertions when tests fail (modify business code instead)
line 38

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

AGENTS.md

SKILLS/TEST-SPECIFICATION-ALIGNMENT KNOWLEDGE BASE

Generated: 2026-11-04 Commit: eb2097b0 Branch: sprint/2026-11-03-02 Version: 0.37.0.0

OVERVIEW

Test-Specification Alignment Engine — two-stage validation ensuring tests accurately reflect requirements and design specs.

STRUCTURE

skills/test-specification-alignment/
├── SKILL.md              # Core alignment workflow (2-phase)
├── AGENTS.md             # This file
├── evals/                # Evaluation test cases
└── references/           # Supporting documentation

WHERE TO LOOK

Task	Location	Notes
Core workflow	SKILL.md	Phase 1 (align) + Phase 2 (execute)
Freeze mechanism	SKILL.md	Prevents test modifications during Phase 2

CONVENTIONS

Phase 1 (Align): test modifications ALLOWED to align with specification
Phase 2 (Execute): test modifications FORBIDDEN (freeze enforced)
Minimum 80% alignment score required to pass
All @test, @intent, @covers JSDoc tags mandatory in test files
Test annotations trace to REQ-XXX and AC-XXX

ANTI-PATTERNS (THIS PROJECT)

Do NOT modify tests during Phase 2 execution
Do NOT proceed with low alignment score (<80%)
Do NOT skip specification validation if specification exists
Do NOT delete test files in Phase 2 (freeze intercepts)
Do NOT modify assertions when tests fail (modify business code instead)
Missing @test tags → test rejected

UNIQUE STYLES

Two-phase separation (modify vs. execute)
Freeze/unfreeze test protection mechanism
YAML specification-driven validation (specification.yaml)
Structured JSDoc tag requirements (@test, @intent, @covers)

COMMANDS

/test-specification-alignment   # Run alignment check

NOTES

Runs during BUILD (Phase 2) after TDD
Mandatory before gstack-ship release
Integrates with test-driven-development skill
Uses freeze skill to lock test directories during Phase 2

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free