Claude Code Plugins

Community-maintained marketplace

Feedback

context-resume

@glittercowboy/plugin-freedom-system
4
0

Load plugin context from handoff files to resume work

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name context-resume
description Load plugin context from handoff files to resume work
allowed-tools Read, Bash, Skill
preconditions Handoff file must exist in one of 3 locations

context-resume Skill

Purpose: Universal entry point for resuming plugin work from .continue-here.md handoff files. Handles workflow, ideation, mockup, and improvement resume scenarios.

Capabilities:

  • Locates handoff files (3 possible locations)
  • Parses YAML frontmatter and markdown context
  • Presents state summary with time-ago calculation
  • Routes to appropriate continuation skill (via Skill tool)
  • Graceful error recovery for missing/corrupt handoffs

Orchestration Protocol

CRITICAL: This skill MUST NOT implement workflow stages directly.

When resuming workflow (Stages 0-6), this skill:

  1. Locates handoff file
  2. Parses context
  3. Presents summary to user
  4. Checks for orchestration_mode: true in handoff YAML
  5. If orchestration_mode enabled → Invokes plugin-workflow skill via Skill tool
  6. If orchestration_mode disabled → Uses legacy direct routing

NEVER bypass orchestration_mode. This enforces the dispatcher pattern:

  • plugin-workflow orchestrates
  • Subagents implement
  • context-resume just loads and routes

See references/continuation-routing.md Step 4a-1 for complete protocol.

Handoff File Locations

The system uses 3 handoff locations, checked in priority order:

**Path:** `plugins/[PluginName]/.continue-here.md` **Meaning:** Plugin in active development (Stages 0-6) **Creator:** plugin-workflow skill **Contains:** stage, phase, orchestration_mode, next_action, completed work, next steps **Path:** `plugins/[PluginName]/.ideas/.continue-here.md` **Meaning:** Plugin in planning/ideation phase **Creator:** plugin-ideation skill **Contains:** Creative brief status, mockup status, ready-to-implement flag **Path:** `plugins/[PluginName]/.ideas/mockups/.continue-here.md` **Meaning:** UI mockup iteration in progress **Creator:** ui-mockup skill **Contains:** mockup_version, iteration notes, finalization status

Search order: Priority 1 → 2 → 3. If multiple found, disambiguate (see references/handoff-location.md).

Resume Workflow

Search for handoff files across 3 locations, handle interactive plugin selection if no name provided, and disambiguate when multiple handoffs exist for same plugin.

See references/handoff-location.md for complete location logic.

MUST complete before Step 2. If no handoff found, see error recovery.

Parse YAML frontmatter (plugin, stage, status, last_updated, etc.) and markdown body (current state, completed work, next steps, key decisions).

See references/context-parsing.md for parsing logic.

MUST complete before Step 3.

Calculate "time ago" and build user-facing summary showing where we are in workflow, what's completed, what's next, build/test status, time since last session.

See references/context-parsing.md for presentation logic.

MUST wait for user confirmation. DO NOT auto-proceed. Present numbered decision menu following checkpoint protocol. Determine routing based on stage type (workflow, ideation, mockup, improvement), load relevant context files (contracts, source code, git history), and invoke appropriate continuation skill.

See references/continuation-routing.md for routing logic.

Error Recovery

Common error scenarios with recovery strategies:

  • No Handoff Found: Check PLUGINS.md and git log to infer state, offer reconstruction options
  • Corrupted Handoff File: Parse git log to infer stage, offer manual recreation
  • Stale Handoff (>2 weeks old): Warn about staleness, offer to verify code changes
  • Multiple Handoffs for Same Plugin: Present disambiguation menu with recommendations

See references/error-recovery.md for all error scenarios and advanced features.

Integration Points

Invoked by:

  1. /continue command (no args) → Triggers interactive plugin selection
  2. /continue [PluginName] command → Triggers specific plugin resume
  3. Natural language: "resume [PluginName]", "continue working on [PluginName]"

Invokes (via Skill tool):

  1. plugin-workflow - For workflow resume at specific stage (Stages 0-6)
  2. plugin-ideation - For ideation resume (improvements or refinement)
  3. ui-mockup - For mockup iteration resume
  4. plugin-improve - For improvement implementation resume

MUST use Skill tool for invocation, NEVER implement directly.

This skill is READ-ONLY for state files.

MUST read:

  • .continue-here.md files (all 3 locations)
  • PLUGINS.md (status verification)
  • Git log (commit history for inference)
  • Contract files (creative-brief.md, parameter-spec.md, architecture.md, plan.md)
  • Source files (if mentioned in handoff)
  • CHANGELOG.md (for improvements)

MUST NOT write:

  • Any .continue-here.md files
  • PLUGINS.md
  • Any source code or contract files

Continuation skills invoked by this skill will handle all state updates.

Success Criteria

Resume is successful when:

  1. Handoff located: Found correct handoff file(s) from 3 possible locations
  2. Context parsed: YAML and markdown extracted without errors
  3. State understood: User sees clear summary of where they left off
  4. Continuity felt: User doesn't need to remember details, handoff provides everything
  5. Appropriate routing: Correct continuation skill invoked with right parameters
  6. Context loaded: Contract files and relevant code loaded before proceeding
  7. Error handled: Missing/corrupt handoff handled gracefully with fallbacks
  8. User control: User explicitly chooses to continue, not auto-proceeded

Execution Requirements

MUST do when executing this skill:

  1. ALWAYS search all 3 handoff locations before declaring "not found"
  2. MUST parse YAML carefully - handle missing optional fields gracefully
  3. MUST present time-ago in human-readable format (not raw timestamps)
  4. MUST show enough context that user remembers where they were
  5. NEVER auto-proceed - wait for explicit user choice
  6. MUST load contract files BEFORE invoking continuation skill (provides context)
  7. MUST use git log as backup if handoff is stale/corrupt
  8. MUST preserve user's mental model - summary should match how they think about plugin

NEVER do these common pitfalls:

  • Forgetting to check all 3 locations
  • Auto-proceeding without user confirmation
  • Not loading contract files before continuation
  • Showing raw YAML instead of human summary
  • Missing disambiguation when multiple handoffs exist