From concept-dev
Resumes interrupted concept development session: loads state and phase artifacts, summarizes context, offers options to continue, go back, or view status.
npx claudepluginhub ddunnock/claude-plugins --plugin concept-dev<context>
<read required="true">${CLAUDE_PLUGIN_ROOT}/SKILL.md</read>
</context>
# /concept:resume
Resume a concept development session after interruption.
## Procedure
### Step 1: Load State
If no state file exists: "No active session found. Run `/concept:init` to start a new session."
### Step 2: Identify Resume Point
Determine the current phase and gate status:
### Step 3: Load Context
Based on current phase, load the relevant artifacts:
| Phase | Artifacts to Load |
|-------|-------------------|
| spitball | (none — session state only) |
| problem | .concept-dev/IDEAS.md.../fire-6-resumeResumes project from most recent handoff file with full context restoration, displays status summary, checks incomplete work, and routes to next action. Supports --handoff, --list, --diff flags.
/resume-workRestores full project context from previous session: loads/reconstructs STATE.md, detects checkpoints and incomplete work, presents status, offers context-aware next actions, and routes accordingly.
/deep-resumeResumes an active deep work session by detecting from registry or flags, restoring context and work directory, and continuing from the current phase. Supports --session and --resume-from flags.
/crucible-continueResumes Crucible project by detecting state from phase files (planning, outline, draft, edit) and presenting interactive options via AskUserQuestion.
/sessionStarts a development session (housekeeping, feature, deep). Researches project state from STATE.md for resume support and recommends next actions for user approval.
Share bugs, ideas, or general feedback.
Resume a concept development session after interruption.
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/update_state.py --state .concept-dev/state.json show
If no state file exists: "No active session found. Run /concept:init to start a new session."
Determine the current phase and gate status:
===================================================================
RESUMING SESSION
===================================================================
Session: [id]
Project: [name]
Last Updated: [timestamp]
Current Phase: [phase name]
Phase Status: [in_progress / completed]
Gate Status: [passed / pending]
===================================================================
Based on current phase, load the relevant artifacts:
| Phase | Artifacts to Load |
|---|---|
| spitball | (none — session state only) |
| problem | .concept-dev/IDEAS.md |
| blackbox | .concept-dev/IDEAS.md, .concept-dev/PROBLEM-STATEMENT.md |
| drilldown | .concept-dev/BLACKBOX.md (+ prior artifacts) |
| document | All artifacts |
Read each artifact and summarize key points to the user.
===================================================================
SESSION CONTEXT
===================================================================
[For each loaded artifact, provide a 2-3 sentence summary]
Phase 1 (Spit-Ball):
Themes selected: [list]
Phase 2 (Problem):
Problem: [1-sentence summary]
[if completed]
Phase 3 (Black-Box):
Approach: [name]
Blocks: [list]
[if completed]
Phase 4 (Drill-Down):
Blocks researched: [N] of [N]
Sources: [N] | Gaps: [N]
[if in progress or completed]
-------------------------------------------------------------------
RESUMPTION POINT:
Based on the state, you were in [phase] — [status].
[Specific context about where in the phase you were]
Ready to continue?
[A] Continue from where we left off
[B] Go back to a previous phase
[C] Show full status dashboard (/concept:status)
===================================================================
Based on user selection:
Continue: Invoke the appropriate command for the current phase. Re-enter at the beginning of the current phase — existing artifacts are preserved and provide context, but the phase restarts from Step 1 rather than attempting to detect and skip individual completed steps.
Go back: Ask which phase to return to. Warn that going back will not delete existing artifacts but will re-open the gate for that phase.
Dashboard: Run /concept:status.
| Phase | Resumption Behavior |
|---|---|
| spitball (in_progress) | Summarize captured ideas so far, continue ideation |
| spitball (gate pending) | Present theme clustering and gate prompt |
| problem (in_progress) | Summarize questions answered, continue questioning |
| problem (gate pending) | Present problem statement candidates for approval |
| blackbox (in_progress) | Check which sections are approved, continue from next |
| blackbox (gate pending) | Present architecture for final approval |
| drilldown (in_progress) | Show which blocks are done, continue from next block |
| drilldown (gate pending) | Present drill-down for final approval |
| document (in_progress) | Check which sections are approved, continue from next |
| document (gate pending) | Present documents for final approval |