gsd-resume-work

name	gsd-resume-work
description	Resume work from previous session with full context restoration

<augment_skill_adapter>

A. Skill Invocation

• This skill is invoked when the user mentions gsd-resume-work or describes a task matching this skill.
• Treat all user text after the skill mention as {{GSD_ARGS}}.
• If no arguments are present, treat {{GSD_ARGS}} as empty.

B. User Prompting

When the workflow needs user input, prompt the user conversationally:

• Present options as a numbered list in your response text
• Ask the user to reply with their choice
• For multi-select, ask for comma-separated numbers

C. Tool Usage

Use these Augment tools when executing GSD workflows:

• launch-process for running commands (terminal operations)
• str-replace-editor for editing existing files
• view for reading files and listing directories
• save-file for creating new files
• grep for searching code (or use MCP servers for advanced search)
• web-search, web-fetch for web queries
• add_tasks, view_tasklist, update_tasks for task management

D. Subagent Spawning

When the workflow needs to spawn a subagent:

• Use the built-in subagent spawning capability
• Define agent prompts in .augment/agents/ directory </augment_skill_adapter>

Restore complete project context and resume work seamlessly from previous session.

Routes to the resume-project workflow which handles:

• STATE.md loading (or reconstruction if missing)
• Checkpoint detection (.continue-here files)
• Incomplete work detection (PLAN without SUMMARY)
• Status presentation
• Context-aware next action routing

<execution_context> @/home/delorenj/code/bhappy/.augment/get-shit-done/workflows/resume-project.md </execution_context>

**Follow the resume-project workflow** from `@/home/delorenj/code/bhappy/.augment/get-shit-done/workflows/resume-project.md`.

The workflow handles all resumption logic including:

1. Project existence verification
2. STATE.md loading or reconstruction
3. Checkpoint and incomplete work detection
4. Visual status presentation
5. Context-aware option offering (checks CONTEXT.md before suggesting plan vs discuss)
6. Routing to appropriate next command
7. Session continuity updates