skill resume

Engineering Community

Skill notes

Overview

Restore context from a previous session and seamlessly continue the workflow where you left off. Core principle: Check state → Load adaptive context → Display restoration summary → Route to appropriate action.

When to Use

Use this skill when user says: "Resume" or "continue working" "Pick up where I left off" "What was I doing?" "Restore session"

Phase 0: Check Session Handoff File (v9.6.0)

Step 0: Check for .octo-continue.md Before checking .octo/, look for a session handoff file. This is written automatically by PreCompact and SessionEnd hooks and contains a human-readable summary of the last session. If .octo-continue.md exists, read it and display its contents to the user as context. Then continue to Phase 1 to load the full state. The handoff file provides a

Phase 1: Check Project Initialization

Step 1: Verify .octo/ Directory Exists If .octo/ does not exist but .octo-continue.md exists, display the handoff file contents and offer to start a new session based on that context. If neither exists, display: /octo:embrace build a REST API with user authentication

Phase 2: Read Current State

Step 1: Execute octo-state.sh read_state Expected output format: Step 2: Parse State Variables Extract these key values: current_phase - Phase number (1-4)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@nyldn · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 0: Check Session Handoff File (v9.6.0)

Step 0: Check for .octo-continue.md Before checking `.octo/`, look for a session handoff file. This is written automatically by PreCompact and SessionEnd hooks and contains a human-readable summary of the last session. If `.octo-continue.md` exists, read it and display its contents to the user as context. Then continue to Phase 1 to load the full state. The handoff file provides a

02
Phase 1: Check Project Initialization

Step 1: Verify .octo/ Directory Exists If .octo/ does not exist but `.octo-continue.md` exists, display the handoff file contents and offer to start a new session based on that context. If neither exists, display: /octo:embrace build a REST API with user authentication

03
Phase 2: Read Current State

Step 1: Execute octo-state.sh read_state Expected output format: Step 2: Parse State Variables Extract these key values: `current_phase` - Phase number (1-4)

04
Phase 3: Load Adaptive Context

Step 1: Get Context Tier (Auto Mode) This automatically selects the appropriate context tier based on current status: Status · Tier Selected · Context Loaded ready, planned, planning, complete, shipped · planning · STATE.md + PROJECT.md + ROADMAP.md building, in_progress · execution · + phase plans + recent summaries

05
Phase 4: Extract History and Blockers

Step 1: Read Last 3 History Entries from STATE.md Expected format: Step 2: Extract Blockers from STATE.md Expected format: If blockers exist: List of blocker items

06
Phase 5: Display Restoration Summary

Step 1: Build and Display Summary Step 2: Map Phase Number to Name Phase · Name 1 · Discover 2 · Define

07
Phase 6: Intelligent Routing

Step 1: Route Based on Status Status · Action · Message `in_progress` · Continue current phase · "Continue with current phase. Context loaded." `blocked` · Review blockers · "Review blockers first: `/octo:issues`" `complete` · Ready for next phase · "Phase complete. Ready for `/octo:ship`"

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.