continue

Included with Lifetime

$97 forever

Use to resume from /pause. Reads the pause state, injects relevant memory context, and proposes the next concrete step. Pairs with /pause skill.

General

What this skill does


# continue

Resume from `/pause`. Inverse operation. Reads pause state, refreshes memory context, proposes next move.

## Method

1. **Locate pause.** User specifies `<id>` or "most recent".
2. **Load `pause-<id>.json`** from `.siftcoder/checkpoints/`.
3. **Memory refresh.** `mem_get { id: pause.memoryId }`. Also `mem_search` for activity since the pause (any progress someone else made? any new constraints?).
4. **Verify state.** Has the codebase changed since pause? `git log --since=<pause.createdAt>`. Major changes invalidate the dead-end list.
5. **Propose resume.** Summarise the pause + propose the next concrete step + confirm with user.
6. **Mark resumed.** Update memory: `kind: pause`, `status: resumed`.

## Output shape

```
Resuming: pause-<id> (from <ISO>)

Original open question:    <pause.openQuestion>
Progress at pause:
  ✓ <item>
Hypothesis at pause:       <pause.hypothesis>

Since pause (X days ago):
  - <commits / activity>
  - <new memory items>

Dead ends still relevant: <count>
Constraints still hold:   <count>

Proposed next step:        <pause.nextStep>

Confirm to proceed, or describe variant?
```

## Rules

- **Verify state.** Codebase may have moved; pause's hypothesis may be stale.
- **Propose, don't auto-execute.** User confirms before resuming.
- **Memory updated.** Pause status moves to `resumed`.
- **List dead ends prominently.** They're the highest-value part of pause memory.

## Anti-patterns

- Resuming on a stale hypothesis without verification
- Ignoring activity since pause
- Bypassing the user-confirm step
- Re-exploring dead ends because they weren't surfaced

## When NOT to use

- No prior `/pause` to resume from
- Pause was about an abandoned thread — `/dream` for fresh thinking
- Better to start fresh — sometimes the right call

## Subagent dispatch

- None for the load step
- Memory MCP for refresh
- `general-purpose` for the next step if it's well-defined

## Value over native CC

CC has no native pause/resume. The pair `/pause` + `/continue` provides explicit session-bridging. The structured resumption (with verification) IS the value.

Files: 1

Size: 2.2 KB

Complexity: 5/100

Category: General

Source: https://github.com/ialameh/sift-coder/tree/main/skills/workflow/continue

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts