gtm

Plugin gtm from marketplace gentleteam in MorganKryze/GentleTeaM. Commands read from the repo's manifest — 2 days ago.

Skills (14)

• brainstorm

  Brainstorm a topic with the GTM team (three stances, methods, a roundtable) into a note for the spec. Use when the human has an idea, not yet a request.

• brief-me

  Re-present a GTM artifact at the detail level the human picks, or dig into it with a method. Use when the human wants one explained or challenged.

• deliver

  Deliver an approved GTM plan: tasks with reviews and correction rounds, then the final review. Use when /gtm:plan is done.

• design

  GTM design loop: mockups scored against the design guideline, then shown for approval. Use when a Feature changes screens.

• 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.

• init

  Set up GTM in a project: brief, config, team settings and guidelines from the codebase, after a short interview. Use when a project has no GTM root, or to refresh it.

• pause

  Stop the current GTM run cleanly, keep its work, and write how to resume it.

• plan

  Write the GTM task plan from an approved spec with the architect. Use when the spec is approved.

• research

  Write a sourced state of the art of a domain with the researcher, and show its proposals as cards.

• retro

  Turn a shipped GTM branch into ledger lessons and guideline proposals; close resolved minors. Use when a branch has shipped.

• 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.

• spec

  Write a GTM spec with the architect and present its summary for approval. Use when a Feature or Milestone needs one.

• status

  Show where the current GTM run stands from NOW.md, rebuilt from the files when missing or stale.

• 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.

Subagents (13)

• analyst

  GTM analyst: clarifies a request and proposes the track; drafts the setup at init. Read-only on code.

• architect

  GTM architect: writes the spec and the task plan, replaying risky tasks in a scratch clone.

• art-director

  GTM art director: gathers references and proposes three directions before any mockup.

• data-reviewer

  GTM data-integrity reviewer for diffs on its configured paths. Read-only.

• design-critic

  GTM design critic: scores a mockup against the design guideline. Read-only.

• designer

  GTM designer: draws PNG mockups from a brief and the design guideline.

• final-reviewer

  GTM whole-branch reviewer before the go; triages deferred minors. Read-only.

• implementer

  GTM implementer: one plan task or one list of findings, test-first, gated, committed.

• release-qa

  GTM release QA: runs the scripted journey on the live instance after deploy.

• researcher

  GTM researcher: writes a sourced state of the art of a domain and proposes improvements as cards.

• reviewer

  GTM code reviewer for one task: spec compliance, then quality. Read-only.

• security-reviewer

  GTM security reviewer for diffs on its configured paths. Read-only.

• ux-qa

  GTM UX and accessibility QA: captures touched screens and compares with the mockup.

Similar plugins