Deep Resume

uv run --project <plugin_root>/deep-plan <plugin_root>/scripts/tools/discover-session.py

The script outputs JSON. Parse it and proceed based on status:

Step 3: Handle Result

If status is "project_overview":

This is a comprehensive cross-phase view of a deep-project with multiple splits.

Display the overview table:

═══════════════════════════════════════════════════════════════
DEEP-RESUME: Project Overview
═══════════════════════════════════════════════════════════════
Project:  {project_dir}
Branch:   {git_branch}
Summary:  {plans_complete}/{total_splits} planned, {implementations_complete}/{total_splits} implemented

Split                            Spec  Plan              Implement
─────────────────────────────────────────────────────────────────────
(one row per split — see formatting below)
═══════════════════════════════════════════════════════════════

Row formatting — for each split in splits, show a row with:

For the Spec column: yes if spec_exists, no if not.

If summary.all_done is true:

All splits fully planned and implemented!
═══════════════════════════════════════════════════════════════

Stop here.

Otherwise, display the suggested next action (from suggested_next):

Suggested next: {action} {plugin} for {split}
  {description}
  Working dir: {working_dir}
═══════════════════════════════════════════════════════════════

Use AskUserQuestion to ask: "Proceed with suggested action, or pick a different split/phase?"

If user confirms the suggestion (or picks a specific split):

For resume actions (in-progress work exists):

• Print the resume context variables (DEEP_RESUME_STEP, etc.) from that split's plan or implement data
• Invoke the matching skill: Skill(skill="deep-trilogy:deep-plan") or Skill(skill="deep-trilogy:deep-implement")

For start actions (beginning a new phase):

• If plugin is deep-plan: Tell the user to run /deep-plan @{split_dir}/spec.md
• If plugin is deep-implement: Tell the user to run /deep-implement @{split_dir}/sections/.

Do NOT suggest starting a phase whose prerequisites are incomplete. The suggested_next field already respects this ordering:

1. Resume in-progress implementation first
2. Resume in-progress planning second
3. Start implementation only when planning is complete
4. Start planning only when a spec exists

If status is "found":

Check complete field first. If true:

═══════════════════════════════════════════════════════════════
DEEP-RESUME: {plugin} session is complete
═══════════════════════════════════════════════════════════════
All work finished. Start a new session with:
  /deep-plan, /deep-implement, or /deep-project
═══════════════════════════════════════════════════════════════

Stop here.

Otherwise, print the resume banner:

═══════════════════════════════════════════════════════════════
DEEP-RESUME: Resuming {plugin} session
═══════════════════════════════════════════════════════════════
Source:    {source} (snapshot or artifact-scan)
Progress:  {progress}
Next:      {resume_step_name}
Branch:    {git_branch}
Path:      {working_dir}
═══════════════════════════════════════════════════════════════

Set resume context. Print these key=value pairs so the target skill sees them:

DEEP_RESUME_STEP={resume_step}
DEEP_RESUME_NAME={resume_step_name}
DEEP_PLUGIN={plugin}
DEEP_SNAPSHOT={snapshot_path or "none"}
DEEP_PROGRESS={progress}
DEEP_BRANCH={git_branch}

Invoke the skill using the Skill tool:

• plugin is deep-plan → Skill(skill="deep-trilogy:deep-plan")
• plugin is deep-implement → Skill(skill="deep-trilogy:deep-implement")
• plugin is deep-project → Skill(skill="deep-trilogy:deep-project")

The target skill will see DEEP_RESUME_STEP in conversation context and auto-resume.

If status is "multiple":

Multiple plugin sessions detected. Present the sessions array as choices:

Use AskUserQuestion: