gtm
GentleTeaM entry point: picks the track and routes, or proposes the next command. Use when starting GTM work or unsure what to do next.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- gtm
- description
- GentleTeaM entry point: picks the track and routes, or proposes the next command. Use when starting GTM work or unsure what to do next.
- argument-hint
- [what you want done]
03 SKILL.md 正文
GTM: the light agent team
0. Ground rules (every GTM skill)
- GTM root:
.gtm/unless the project's CLAUDE.md or CLAUDE.local.md saysGTM root: <path>. No root: offer/gtm:initin one line and stop. - Read
<root>/config.ymland<root>/team.md. Every human-facing message follows${CLAUDE_PLUGIN_ROOT}/templates/briefing.md, inlanguage.human. - Dispatch roles as
gtm:<role>with the model and effort the team settings give that role, on every dispatch (the profile wins over the agent's defaults). Pass the same values to workflows inargs.team. - Hand-offs are files: give agents paths, never paste documents. Keep their hand-backs out of the human's view unless something deviates.
- Detail level: before presenting an artifact, use
briefing.remembered.<kind>, elsebriefing.detail; when that isask, ask one question (brief / standard / deep) and store the answer underbriefing.remembered.<kind>. - Stealth (
stealth: onin the config): GTM leaves no footprint in the project. Nothing it writes into tracked files, commits, PR text, comments, docs, changelogs or branch names names GTM, its root, roles, skills, plans, ledger or workflows; no attribution trailer; no line in the tracked CLAUDE.md or AGENTS.md; branches followgit.branch, the project's own pattern; text follows<root>/guidelines/voice.md./gtm:shipruns the footprint check before anything leaves. - Run view: in every track (a Fix included), rewrite
<root>/NOW.mdwhole, never append, as the last write of the step: before each dispatch or workflow run, after each progress line, when a checkpoint or decision card is shown or answered, and when a skill ends or stops its run. Facts fromnode "${CLAUDE_PLUGIN_ROOT}/scripts/now-facts.mjs" --root '<root>'(add the--runningand--waitingyou know), shape from${CLAUDE_PLUGIN_ROOT}/templates/now.md. Write it only in the main checkout (git rev-parse --git-direqualsgit rev-parse --git-common-dir), never in a worktree. Read the NOW.md there first: tracked (git ls-files --error-unmatchsucceeds) or line 1 neither the template's# <slug> · <HH:MM>nor that ending in· rebuilt, it is the user's.<rel>: the root's path fromgit rev-parse --show-toplevel(an absolute root made relative to it); run the git commands below from that top. Untracked and<root>/NOW.md.bakabsent: rename it to that, with a Heads-up. Before that, whengit check-ignore -q <rel>/NOW.mdsucceeds and fails for<rel>/NOW.md.bak, add/<rel>/NOW.md.bakas/<rel>/NOW.mdis added below; rename only whengit check-ignore -qthen succeeds for the.bak. No rename: write no run view, and say why in one Heads-up the first time in a session only. Root inside the repository, NOW.md untracked,git check-ignore -q <rel>/NOW.mdfailing and the exact line/<rel>/NOW.mdabsent from the filegit rev-parse --git-path info/excludenames: add it on its own line (never.gitignore), create the folder if missing, and add a newline first when the file does not end with one. Say so in one Heads-up, only when you added the line. A?in the facts or a failed write never holds up a dispatch. State and card file: asnow.mdsays. - Limits: when a phase starts (design, spec, plan, a task or wave, the final review, a fix
wave), run
node "${CLAUDE_PLUGIN_ROOT}/scripts/usage-line.mjs" --read --ledger '<root>/ledger.md'with--tokensand--minutesleft (the plan's estimate, else the spec's, less the branch's measures; no estimate: leave both out). When this slug has none and the reading is notstale,?ornone, append a ledgerusagelinelimits at start: <w> <p>% resets <ISO> · …, one per window shown. Aflagline: one Heads-up and one card per window and reset in a branch, and the phase waits for the answer: A lighter for this branch (at most two of implementer, reviewer, architect, designer, largestrolesshare first, all?: implementer and reviewer, tosonnetlow, old → new), B keep, C/gtm:pauseuntil the reset; no saving promised. A: a ledgerrulinglimits: lighter <role> <old> → sonnet low, …quoting the answer, for this slug's dispatches, resumes included;team.mdunchanged.none: nothing;staleor?: one Heads-up per session. - Nothing is pushed, merged, tagged or released without the human's explicit go. The advisor only
proposes: it runs no skill, workflow or git command that writes, and never pushes, merges, tags or
starts a run until the human picks. Next steps may name one next command from
${CLAUDE_PLUGIN_ROOT}/templates/commands.md, none when the state calls for none.
1. Pick the track (≤ 2 questions)
Request: $ARGUMENTS
Facts with phase paused (now-facts.mjs): before anything else, one line naming the slug
and its resume command (?: the handoff file to read instead); on yes, run it only when
git branch --show-current is the facts' branch, else name that branch (?: the
handoff's branch) and stop.
No request: propose as ${CLAUDE_PLUGIN_ROOT}/templates/advisor.md says. Asked which commands
exist: show ${CLAUDE_PLUGIN_ROOT}/templates/commands.md, read only then. Clear and small: judge
it yourself. Otherwise dispatch gtm:analyst with the request, the root and, for a request from a
brainstorm note, its path, read only: tell the analyst never to write it.
| Track | When | Flow | Human checkpoints |
|---|---|---|---|
| Fix | ≤ the file limit for a fix (team settings, 3 by default), no schema, migration or auth change | 3-line design in chat → implementer + reviewer, plus the specialist on security or data ground | approve the 3-line design, then the go |
| Feature | one capability, one branch | design-loop if screens change → spec → plan → deliver per task → final review | mockups, spec summary, go |
| Milestone | several branches, a new surface | decomposition into sub-features, then the Feature flow per branch, final review per branch | decomposition, then per branch: mockups, spec, go |
A Feature is small when it changes no screen, schema, migration or auth and touches at most
twice the file limit for a fix in estimated files (6 by default): /gtm:spec then has one architect pass
write the spec and the plan.
Present the track with its reason and at most two decision cards in one message. For a Fix,
include the 3-line design (what changes, where, how it is proven; for a threshold, the mutation its
test catches) in that same message, naming the specialists whose team.md triggers match its
files. For a Feature, say small or not, with the file count ("Feature, small, ~4 files").
A Feature whose screens use only design.kit's patterns (the analyst says so), with ux-qa on:
the track message says "design in code" and why, and the route skips /gtm:design. A new
pattern or direction, the human's ask, no kit or ux-qa off: the design loop as today.
A Fix that grows past its file limit becomes a Feature on its own, one way only (say so in a Heads-up). Nothing downgrades mid-task.
Record the work in <root>/backlog.md: add or update its story (type, priority P0-P3 per
guidelines/work.md, status doing, track). A Milestone is an epic.
2. Route
- Fix: write
<root>/reports/<slug>/brief.md(the approved 3 lines plus the test that proves it), create the branch asgitsays, run the workflowgtm:deliver-taskwithtrack: "fix"(args as/gtm:deliverbuilds them).ESCALATE→ read it as/gtm:deliver§2 says; the commits stay.OPENorBLOCKED→ stop, and read it as/gtm:deliver§2 says. Any result: its progress line and measure as/gtm:deliver§1 and §2 step 3 say.CLEAN→ append each minor to the ledger (minor) as/gtm:deliver§2 does, onerunline as its §5 says (its phasetasks, one task), holdingFix: CLEAN, no final review; then present the result and ask the go (/gtm:ship). - Feature:
/gtm:design(only if screens change anddesign.screensis true) →/gtm:spec→/gtm:plan→/gtm:deliver→/gtm:ship. Invoke each skill in turn; stop only at a checkpoint. - Milestone: dispatch
gtm:architectto write<root>/specs/<date>-<slug>-milestone.md: the sub-features, one branch each, their order and dependencies, ≤ 1 page with a Summary block. Present it (checkpoint), then run the Feature flow per sub-feature.
3. End every run with
The result per the briefing format, then Decisions made for you (each with its cost if wrong), and
append each one, as a ruling line, to <root>/ledger.md.
04 同仓库更多 Skills
open
yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy
human
zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
tune
Re-tune GTM team settings (roles, effort, specialists, gates, companions, reflexes, stealth) from the ledger, as decision cards. Use when the team feels slow, costly or blind.
status
Show where the current GTM run stands from NOW.md, rebuilt from the files when missing or stale.
spec
Write a GTM spec with the architect and present its summary for approval. Use when a Feature or Milestone needs one.
ship
Ship a GTM branch: gate, PR text, then push, merge, tag or release only on the human's go. Use when /gtm:deliver is ready.