continue
Resume interrupted work from context. Use when continuing after session break, context limit, or interruption.
What this skill does
## Pre-loaded Context
Active scopes:
!`find scopes -maxdepth 3 -name scope.md 2>/dev/null`
Checkpoints:
!`find scopes -name checkpoint.yaml -maxdepth 3 2>/dev/null`
Git status:
!`git status --short 2>/dev/null`
Current branch:
!`git branch --show-current 2>/dev/null`
# Continue Skill
Resume interrupted work from context. Picks up where `implement` (execute operation) left off.
---
## When to Use
- After hitting context limit during `/implement`
- Starting a new session to continue a scope
- Recovering from interruption mid-implementation
---
## Workflow
### Step 1: Find Checkpoint
1. Parse scope name from argument (e.g., `/continue auth-system`)
2. If no argument: find most recent checkpoint in `./scopes/*/*/checkpoint.yaml` (lifecycle dirs: `draft`, `active`, `done`)
3. If no checkpoint found: suggest `/implement` instead
```bash
# Find most recent checkpoint across all lifecycle states
ls -t ./scopes/*/*/checkpoint.yaml | head -1
```
### Step 2: Load Context
Read these files (in parallel):
```
./scopes/<state>/<scope>/checkpoint.yaml # Session state
./scopes/<state>/<scope>/scope.md # Requirements
./scopes/<state>/<scope>/tasks.yaml # Task definitions
./scopes/<state>/<scope>/dependencies.yaml # Batch structure
./scopes/<state>/<scope>/validation.yaml # Review config
```
`<state>` ∈ `{draft, active, done}` — typically `active` for in-flight work.
### Step 3: Verify Branch State
```bash
# Checkout scope branch
git checkout <checkpoint.branch>
# Verify at expected commit
git log -1 --format="%H" | head -c 8
# Should match checkpoint.last_commit
# If mismatch, warn user and ask to proceed or abort
```
### Step 4: Report Progress
Present concise status:
```
## Resuming: <scope_name>
**Progress:** Batch <last_batch>/<total_batches> complete
**Completed:** <N> tasks
**Remaining:** <M> tasks
**Next batch:** #<next_batch.number>
- <task_id>: <task_name>
- <task_id>: <task_name>
[parallel: yes/no]
**Deferred issues:** <count>
[list if any]
Continuing with three-phase pipeline...
```
### Step 5: Resume Three-Phase Pipeline
Execute the next batch using the same pipeline as `implement` (execute operation):
```
Phase A: TESTERS
├── Dispatch tester(s) for next_batch.tasks
└── Wait for completion
Phase B: IMPLEMENTERS
├── Dispatch implementer(s) with tester reports
└── Wait for completion
Phase C: REVIEWERS
├── Dispatch 1 Claude + N OpenCode reviewers (from review_config)
└── Wait for completion + synthesize
```
**CRITICAL:** Follow all `implement` execute operation rules:
- Always use `subagent_type: "general"` for subagents
- Dispatch parallel subagents in single message
- Never skip reviewer phase
- Fix Critical/High issues before proceeding
### Step 6: Update Checkpoint
After batch completes:
1. Update tasks.yaml statuses
2. Write new checkpoint.yaml
3. Commit with batch info
4. Continue to next batch or report completion
---
## Quick Resume Template
When resuming, use this condensed context for subagents:
**For Tester:**
```
Task: <task_id> - <task_name>
From: <scope_name> (batch <N>)
Requirements: [from tasks.yaml]
Test hints: [from tasks.yaml]
Invoke `test` skill. Write failing tests (RED).
Report tester_report YAML.
```
**For Implementer:**
```
Task: <task_id> - <task_name>
From: <scope_name> (batch <N>)
Tester report: [paste tester_report]
Invoke `implement` skill. Make tests pass (GREEN).
Report implementer_report YAML.
```
**For Reviewer:**
```
Batch <N> review for <scope_name>
Tasks: <task_ids>
Implementer reports: [paste all]
Scope requirements: [from tasks.yaml]
Invoke `code` review. Evaluate gates.
Report reviewer_report YAML.
```
---
## Handling Edge Cases
**Checkpoint not found:**
```
No checkpoint found for <scope>.
Run /implement <scope> to start fresh.
```
**Branch mismatch:**
```
Warning: Current branch differs from checkpoint.
Expected: feat/<scope> at <sha>
Actual: <current_branch> at <current_sha>
Options:
1. Checkout checkpoint branch and continue
2. Abort and investigate
```
**Checkpoint stale (tasks.yaml modified):**
```
Warning: tasks.yaml modified since checkpoint.
Checkpoint: <timestamp>
tasks.yaml: <modified_time>
Regenerating next batch from current state...
```
**All tasks complete:**
```
All tasks complete for <scope>.
Run final review? [Y/n]
```
---
## Integration
**Command:** `/continue [scope-name]`
**Related skills:**
- `implement` (execute operation) - Initial execution (writes checkpoints)
- `scope update` - Sync task status via /scope update
- `scope done` - Mark scope as done
---
## Example Session
```
User: /continue
Claude: Found checkpoint for auth-system
## Resuming: auth-system
**Progress:** Batch 2/4 complete
**Completed:** 4 tasks (T001-T004)
**Remaining:** 3 tasks
**Next batch:** #3
- T005: Add session management
- T006: Add token refresh
[parallel: yes]
**Deferred issues:** 1
- [M1] Variable naming in auth.py:45 (batch 2)
Continuing with three-phase pipeline...
[Dispatches 2 testers in parallel]
[Dispatches 2 implementers in parallel]
[Dispatches 1 Claude + 2 OpenCode reviewers in parallel]
[Synthesizes review, no critical issues]
[Writes checkpoint, commits batch 3]
Batch 3 complete. 1 batch remaining.
Continue in this session or /continue later.
```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.