Glossary

What does each term mean?

Art direction

The stage of /gtm:design for a new look: the art director proposes three directions and you pick one before any designer draws.

Backlog

.gtm/backlog.md: epics, their stories, priority and status, one table per epic.

Brainstorm

/gtm:brainstorm: explores a vague idea with you, in one of three stances, and keeps the result in a note under .gtm/brainstorms/ that the spec cites.

Brief

.gtm/brief.md: your project’s one-page constitution: purpose, users, principles, limits.

CI-only red

A check that went red in CI on a commit whose local gate is green. /gtm:ship gives it a class and runs the failing test again only in the runner’s conditions, never the red check itself.

Checkpoint

A moment where you decide, three per Feature: the mockups, the summary and the go, at /gtm:design, /gtm:spec and /gtm:ship.

Confirmation

What would show a decision still holds, named in its row of the spec: an acceptance line, a step of the gate, or a named review when nothing can be measured.

Conventions

The project’s rules, one file per area: conventions.md in .gtm/, and its files under guidelines/.

Correction round

The implementer fixes open findings, then the same reviewers re-check; 3 at most (team.md), each raising the implementer one level, up to high, or xhigh on a risky path.

Craft

What a studio knows about a kind of job, one file per job (brand, website, mobile) under the plugin’s templates/crafts/, read only when a prompt names it.

Decision card

A question, its options, a firm recommendation and the cost if wrong; in a spec, its criteria, at most one objection. Under a mandate: only at four moments, via AskUserQuestion.

Decisions made for you

What the team decided unasked, with its cost if wrong: in ledger.md as ruling lines; under a mandate, ruling · default: … for those taken by default, counted in state.json.

Dry run

The architect runs a risky task’s code in a scratch copy while planning, to prove the plan; risky paths are set in team.md, and work on them raises the security and final reviewers one level.

Dig

/gtm:brief-me asked to challenge an artifact with one method; it changes no file.

Feature

One capability on one branch, with three checkpoints, started with /gtm:gtm.

File limit for a fix

The most files a Fix may change, 3 by default: the Fix track ceiling line in team.md. Past it, a fix grows into a Feature.

Final review

One last review of the whole branch against the spec and the plan, by the final-reviewer, once every task is done.

Fix

A change of at most 3 files with no schema or sign-in change, run by /gtm:gtm.

Handoff

handoff.md, written by /gtm:pause: what was stopped, what waited, the worktrees kept and the command that resumes.

Landing

What /gtm:ship records under a standing go instead of pushing: the class, the commit and its proofs, in .gtm/reports/<slug>/landing.json, for a program of yours to check and merge.

Lens

The method behind an item, named at its end as (lens: <method name>).

Logbook

ledger.md, in .gtm/: one line per lesson, decision or deferred finding, kept across changes.

Mandate

Four lines letting /gtm:deliver settle reversible decisions alone; it asks you only at four moments: a costly or irreversible choice, a very visible one, the end of the run, a release.

Milestone

Work across several branches, each run as a Feature, tracked as an epic in backlog.md.

Mockups

One page showing each new screen in light and dark, scored by the critic, kept in .gtm/mockups/.

Mutation

A small planted change; it survives when no test catches it.

Reflex

A method a role applies every time, listed in its file; it adds a lens and never weakens a check.

Project sheet

sheet.json in your GTM folder, one page of the project as data for a program of yours, kept while project.sheet is on; see what it holds. Not a speciality sheet.

Retro

/gtm:retro: distils a delivered branch into at most five lessons and guideline edits.

Roundtable

The voices of a brainstorm: architect, security, UX, data and a user or a skeptic, played in the chat, each line prefixed with its speaker.

Runner’s conditions

The CI runner’s OS family, toolchain and, as far as stated, its architecture, CPU and memory, rebuilt on your machine by the verify.runner command, such as docker run --rm --init ….

Spec

The document the architect writes before any code, in .gtm/specs/: what will be built, what is left out, and how each part is checked.

Speciality sheet

One file per speciality that a plan names for a task, at most 2 per task: it adds a lens to the roles that read it and never softens a check. Not the project sheet.

Stealth

stealth: on in config.yml: GTM keeps its files out of the tracked tree and its names out of everything it writes into the project.

Stance

Who brings the ideas in a brainstorm: facilitator (only you), partner (you and the team) or ideate for me (the team, and you keep or drop).

Standing go

Your go given ahead for one class of change, docs, until you take it back: git.push: standing and a line /gtm:tune writes on your answer. GTM still pushes nothing; tags and releases ask.

State of the art

What /gtm:research reports on a domain from public sources: its practices, its tools and what changed, with cards you adopt or leave.

Summary

The ten lines at the top of a spec in .gtm/specs/, written for you.

Taste score

The lowest of the design critic’s five grades on a board drawn from a picked direction. The bar is the taste threshold line in team.md, 7 out of 10 by default.

Team settings

team.md, in .gtm/: which roles run, how hard each one thinks, and why, each with its date.

Tune

/gtm:tune: re-evaluates your team settings and conventions from the logbook’s evidence, and switches stealth on or off.

Internal terms

These appear only in the reference and in the team’s reports.

• EARS: Easy Approach to Requirements Syntax, the form of a spec’s acceptance lines.
• footprint check: the scan /gtm:ship runs in stealth; a hit stops the ship.
• gate: a check that must pass before work moves on; see How the team works.
• GTM root: the folder holding GTM’s files, .gtm/ by default.
• hand-back: an agent’s return: ten lines or a structured object.
• hand-off: giving an agent paths to files instead of pasting their content.
• minor: a review finding that does not block a task; logged and triaged by the final review.
• NEEDS CLARIFICATION: a marker for something the spec must not guess; none may remain.

Retired words

Older docs and reports may use these; each now has a plain word.

• Board: now mockups.
• Escalation: now “a fix that grows becomes a Feature”.
• Fix ceiling: now file limit for a fix.
• Fix round: now correction round.
• For you: now summary.
• Ledger: now logbook.
• Replay: now dry run.
• Ruling: now decisions made for you.
• Team profile: now team settings.
• Touchpoint: now checkpoint.