S Skillteca
Receber por email
Explorar Categorias Coleções Newsletter
← Voltar para o catálogo

gsd:resume-work

Desenvolvimento Autor: davepoon

Resume work from previous session with full context restoration

3.1kestrelas
Atualizado há 4 meses
Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add davepoon/buildwithclaude

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/gsd-resume-work/svg)](https://www.skillteca.com.br/skills/gsd-resume-work)

Skills relacionadas

Ver todas de Desenvolvimento →

claude-api

153.1k

Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements). TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`; user asks for the Claude API, Anthropic SDK, or Managed Agents; user adds/modifies/tunes a C

Desenvolvimento #ai #api por anthropics

skill-creator

153.1k

Crie novas skills, modifique e aprimore as existentes, e meça seu desempenho. Utilize para desenvolver, editar, otimizar, testar e comparar skills, além de refinar suas descrições para maior precisão de acionamento.

Desenvolvimento #test por anthropics

claude-code-plugin-release

83.4k

Fluxo de trabalho automatizado de versionamento semântico e lançamento para plugins do Claude Code. Gerencia incrementos de versão em manifestos package.json, marketplace.json, plugin.json, publicação npm (para que npx claude-mem@X.Y.Z seja resolvido), verificação de build, marcação git, lançamentos no GitHub e geração de changelog.

Desenvolvimento #ai #git por thedotmack

claude-mem

83.4k

Contexto Persistente Entre Sessões para Cada Agente – Captura tudo o que seu agente faz durante as sessões, comprime com IA e injeta contexto relevante de volta em sessões futuras. Compatível com Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode e mais.

Desenvolvimento #ai por thedotmack

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

<objective> Restore complete project context from a previous session — handling both manual pause (from /gsd:pause-work) and auto-compact (from the PreCompact hook) handoffs identically. </objective>

<process>

  1. Detect handoff state.

Check for .planning/HANDOFF.json via Read tool. If missing, the session has no handoff — announce "No handoff found" and proceed to normal /gsd:progress routing.

  1. Load STATE.md.

Read .planning/STATE.md to restore the big-picture project position. If missing, reconstruct from .planning/ROADMAP.md and the latest phase directory's SUMMARY.md files; if reconstruction fails, surface the error and stop.

  1. Read the handoff.

Parse .planning/HANDOFF.json. Extract phase, plan, task, status, source, uncommitted_files, decisions, context_notes, next_action. Per HANDOFF schema, all fields are always present (empty arrays / null for unset).

  1. Present project status.

Emit a compact status block covering:

  • Milestone + percent complete (from STATE.md frontmatter progress.percent).
  • Current phase name and number.
  • Plan / task position from the handoff.
  • Handoff source (manual-pause vs auto-compact) and timestamp.
  • Top 3 decisions and any blockers from the handoff.
  • Uncommitted files summary.
  • The next_action string verbatim — it's the resumption hint.
  1. Route to the next action.

Offer 1-3 concrete options based on handoff state. Common patterns:

  • If task was mid-execute: offer /gsd:execute-phase with the current phase.
  • If phase is at plan boundary: offer /gsd:plan-phase or /gsd:execute-phase for the next phase.
  • If there are uncommitted files that look in-progress: call attention to them before offering continuation.
  1. Clean up the handoff (LIFE-01).

After routing — once steps 1-5 have completed without error — remove the handoff file:

``bash node "${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/cache/gsd-plugin/current}/bin/gsd-tools.cjs" checkpoint --clear ``

If the command is unavailable for any reason, fall back to direct removal: ``bash rm -f .planning/HANDOFF.json ``

Do not abort the resume if cleanup fails — it's hygiene, not correctness. The next session's SessionStart will overwrite a stale handoff anyway (per D-05 from Phase 4: latest snapshot wins).

</process>

<rules>

  • Step 6 runs last, after all context is loaded and the user has been shown status. A failed/aborted resume (steps 1-5 error out) leaves HANDOFF.json on disk for recovery (per D-08).
  • If HANDOFF.json is absent in step 1, skip everything — don't attempt to clean up what isn't there. checkpoint --clear is idempotent but unnecessary work.
  • The skill is the single owner of HANDOFF.json deletion. The SessionStart hook must NOT delete — it only detects (per D-10).

</rules>

Compartilhar X LinkedIn