Main Confidence / confidence (push) Failing after 48s

Details

docs: add Spec 212 test authoring guardrails (#245 )

## Summary

- add Spec 212 planning artifacts for test authoring constitution and review guardrails
- expand `TEST-GOV-001` and sync the SpecKit spec/plan/tasks/checklist templates plus contributor guidance
- define the canonical review checklist outcomes and record low-impact and higher-cost validation examples

## Validation

- docs/workflow only; no runtime Pest or Sail test lanes were run
- validation is recorded in `specs/212-test-authoring-guardrails/spec.md` and `specs/212-test-authoring-guardrails/quickstart.md`

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #245

2026-04-18 10:08:00 +00:00

2.0 KiB

Raw Blame History

`.specify/` (Tooling)

This folder contains SpecKit tooling (templates, scripts, constitution, etc.).

Important

Do not create new feature specs in .specify/spec.md, .specify/plan.md, .specify/tasks.md.
Active feature specs live under specs/<NNN>-<slug>/:
- spec.md
- plan.md
- tasks.md
- checklists/requirements.md
Runtime-changing or test-affecting work MUST carry actual test-purpose classification (Unit, Feature, Heavy-Governance, Browser), affected lanes, fixture/default cost risks, heavy-family changes, escalation decisions, and minimal validation commands through the active spec.md, plan.md, and tasks.md.
Review-oriented checklists MUST surface lane fit, hidden defaults, heavy-family visibility, and runtime-budget follow-up before merge; lane upkeep belongs to the feature, not to a later cleanup pass.

Review Entry Point

Use the active feature's spec.md, plan.md, and tasks.md together with the generated checklist based on .specify/templates/checklist-template.md.

Confirm the spec names the affected validation lane(s) or a deliberate N/A, the test family impact, setup-cost impact, reviewer handoff, and any escalation outcome.
Confirm the plan turns that into changed test types, narrowest proving commands, helper/default widening checks, and the note target for budget or trend drift.
Apply the checklist and end with one explicit outcome: keep, split, document-in-feature, follow-up-spec, or reject-or-split.

Low-Impact Rule

Docs-only or template-only work may answer N/A or none.
Do not force fake lane prose when no runtime or suite impact exists.

Escalation Rule

Use document-in-feature for contained cost or drift that belongs in the active feature.
Use follow-up-spec only for recurring pain or structural lane or family changes.
Use reject-or-split when hidden test cost or wrong-lane scope is still unresolved.

The files .specify/spec.md, .specify/plan.md, .specify/tasks.md may exist as legacy references only.

2.0 KiB Raw Blame History

.specify/ (Tooling)