Skip to content
Back to skills

Pause

ASecurity

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

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 26, 2026
ai-agentsnodegit

Security analysis

A100/100

Scanned November 11, 2026

npx -y skills add MorganKryze/GentleTeaM --skill pause --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pause?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pause
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/morgankryze-pause/badge)](https://www.skillsdirectory.com/skills/morgankryze-pause)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pause
description: Stop the current GTM run cleanly, keep its work, and write how to resume it.
disable-model-invocation: true
---
# Pause: stop a run cleanly

Ground rules: as in the `gtm` skill §0. This skill stops dispatches and writes only under
`<root>`: progress lines, `.partial` renames, the handoff, one ledger line, NOW.md and its
`state.json`. It runs
no git command that writes; it pushes, commits and removes nothing.

1. The slug is NOW.md line 1's; `?` or no NOW.md: ask one question naming the active slugs.
2. Read the running items as `/gtm:status` step 1 reads them, the phase NOW.md shows, and what
   waits (kind, task) for the handoff's "What waited".
3. `TaskStop` each running item. One that has already returned: write its normal progress line
   instead, as `/gtm:deliver` §1 says.
4. Per stopped item, append to `reports/<slug>/progress.md`
   `- <step> · PAUSED · <base>..<head> · ? s · ?k · ? agents`: a task, final review or fix wave
   with its own range; a wave's tasks with the wave's base. Then append `- paused · <phase>`.
5. Nothing stopped: skip this step, nothing is half-written. Else run `node
   "${CLAUDE_PLUGIN_ROOT}/scripts/now-facts.mjs" --root '<root>' --slug '<slug>' --since
   '<earliest stopped since>'`. Each spec or plan in `changed`: rename it to `<name>.partial`,
   never deleted; a target that exists: leave both, list it. List each report in `changed`, left
   in place. It exits 1, here and in step 6, while a fact reads `?` (`handoff` until step 6
   writes it): use the JSON anyway; exit 2 or no JSON: stop, rename nothing more, tell the human.
6. Write `reports/<slug>/handoff.md` whole from `${CLAUDE_PLUGIN_ROOT}/templates/handoff.md`,
   from steps 3 to 5 and the facts JSON of step 5's command rerun after the renames, without
   `--since` (worktrees and their `changes`, `resume`). A handoff already there: read it first
   and carry forward each `.partial` it lists that still exists, its pause and its own "Earlier
   pauses" lines under "Earlier pauses".
7. Append to the ledger `<date> · <slug> · ruling · paused on the human's request: <phase>, <n>
   stopped, <k> worktrees kept; resume from reports/<slug>/handoff.md`.
8. Rewrite NOW.md as the `gtm` skill §0 says, then tell the human the `resume` command to type.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.