META·SUITE ← all nine
overview / skills / meta-craft
Skill 06 · keep axis

meta-craft

A tailored craft constitution — plus an evidence-based Definition of Done.

CRAFT CHECKLIST clear over clever nothing padded in handles the edges a reader can follow it leaves something reusable QUALITY → DoD DONE not "looks fine" — provably done WHAT'S HAPPENING 1 · List the standards this kind of work must meet. 2 · The quality bar rises as each standard is satisfied. 3 · “Done” = the bar clears the line — provably, not by vibes. The Definition of Done is checkable: every item is pass or fail, tailored to the task.
FIG — each craft rule checks off; the quality bar must clear the Definition-of-Done line
// what it does

"Good" is not a feeling. meta-craft writes the constitution for a kind of work — the standards it must meet — and pairs it with a Definition of Done you can actually check against, not just nod at.

The standards are tailored to the task and grounded in evidence — so "done" means it cleared a bar, not that someone got tired of looking at it.

// the anatomy
constitution

The non-negotiable standards this kind of work must meet.

definition of done

A checkable bar — pass or fail, not vibes.

evidence

Why each standard is there — so it holds up under push-back.

// invoke it
/meta-suite:meta-craft <the kind of work to hold to a standard>

Returns a craft constitution and a checkable Definition of Done, tailored to the task and backed by evidence — so quality is a bar you clear, not a mood you hope for.

Checkable done

Pass/fail, not vibes.

Task-tailored

Not a generic rubric.

Evidence-backed

Holds up to push-back.

It compounds

Reuse the standard.

Grounding

The ideas here aren't invented — the skill generalizes established practice into one reusable, task-agnostic move. Below: the prior art it builds on, and the in-repo contract it actually runs on.

Prior art
Definition of Done — the Scrum Guide (Schwaber & Sutherland) — completion is agreed in advance and shown with evidence, not asserted.
The Pragmatic Programmer — Hunt & Thomas (1999) — clear beats clever, reuse before building, validate at the boundaries.
Rule of Three — Martin Fowler, Refactoring — no abstraction until the repetition is real.
In this suite
The 13 craft principles references/principles.md — tailored to the 5–8 that bite for the work at hand — plus the evidence-based Definition of Done.