sdlc-framework 1.0.2 → 2.1.0

package/src/workflows/resume-project.md

@@ -1,159 +0,0 @@
-<purpose>Restore a paused session by reading the handoff document, loading context, and directing the user to exactly one next action. Eliminates the cold-start problem when returning to work.</purpose>
-<when_to_use>Run at the start of a new session after /sdlc:pause was used. Also useful when returning to a project after any break, even if /sdlc:pause was not explicitly run.</when_to_use>
-<required_reading>.sdlc/STATE.md, .sdlc/HANDOFF.md (if exists)</required_reading>
-<loop_context>
-  expected_phase: RESUME (transitional — immediately routes to the correct phase)
-  prior_phase: whatever was active when paused
-  next_phase: determined by STATE.md
-</loop_context>
-<process>
-
-<step name="read_state" priority="first">
-  Read .sdlc/STATE.md.
-
-  IF .sdlc/ DOES NOT EXIST:
-    STOP. Display: "No SDLC project found. Run /sdlc:init to initialize."
-
-  IF STATE.md DOES NOT EXIST:
-    STOP. Display: "STATE.md not found. The .sdlc/ directory may be corrupted. Run /sdlc:init to re-initialize."
-
-  Extract:
-  - Current milestone, phase, plan
-  - Loop position
-  - Next required action
-  - Last history entry
-  - paused_at timestamp (if present)
-
-  WHY: STATE.md is the single source of truth. If it is missing, nothing else works.
-</step>
-
-<step name="find_handoff" priority="second">
-  Check for .sdlc/HANDOFF.md.
-
-  IF HANDOFF.md EXISTS:
-    Read it. Extract:
-    - When the session was paused
-    - What was done last session
-    - In-progress work details
-    - Decisions made
-    - Blockers / open questions
-    - User context notes
-    - Git state at pause time
-
-    Calculate time since pause: {now} - {paused_at}
-    Display: "Last session was {N hours/days} ago."
-
-  IF HANDOFF.md DOES NOT EXIST:
-    This is a cold resume without a formal pause.
-    Fall back to STATE.md only.
-    Display: "No handoff found. Resuming from STATE.md."
-
-    Read the most recent files in .sdlc/phases/ to reconstruct context:
-    - Most recent SPEC.md, SUMMARY.md, REVIEW.md, or VERIFY.md
-    - Build a brief context summary from these files
-
-  WHY: HANDOFF.md has rich context. Without it, we can still resume but with less context — the state machine still knows the next action.
-</step>
-
-<step name="restore_context" priority="third">
-  Present the restored context to the user:
-
-  ```
-  === SESSION RESUMED ===
-
-  Project: {from PROJECT.md}
-  Milestone: {number} — {name}
-  Phase: {number} — {name}
-  Plan: {number} — {title, if active}
-
-  Loop position: {position}
-  Last action: {from history}
-
-  {IF HANDOFF EXISTS:}
-  Last session summary:
-  - {what was done}
-  - {what was done}
-
-  In-progress:
-  - {task/AC status}
-
-  Decisions from last session:
-  - {decision}
-
-  Blockers:
-  - {blocker, if any}
-
-  User notes:
-  - {user context, if any}
-  ```
-
-  IF BLOCKERS WERE RECORDED:
-    Ask: "These blockers were noted last session: {blockers}. Are they resolved?"
-    If resolved: note resolution and proceed.
-    If not resolved: "These blockers may affect the next action. Proceed anyway or address them first?"
-
-  WHY: Presenting context upfront saves the user from having to re-read files. The blocker check prevents wasting time on work that is still blocked.
-</step>
-
-<step name="check_git_state" priority="fourth">
-  IF a git repository exists:
-
-  Run: git status
-
-  Compare current git state to the handoff's recorded git state:
-  - Is the branch the same?
-  - Are there new commits since the pause? (someone else may have pushed)
-  - Are there uncommitted changes or stashed changes?
-
-  IF BRANCH CHANGED:
-    Display: "WARNING: You are on branch {current} but the handoff was on branch {paused}. Switch back?"
-
-  IF NEW COMMITS EXIST:
-    Display: "New commits since last session: {count}. These may affect in-progress work."
-    Run: git log --oneline {paused_commit}..HEAD
-    Display the new commits.
-
-  IF STASHED CHANGES:
-    Ask: "Stashed changes from last session exist. Pop the stash to restore them? (yes/no)"
-    If yes: run git stash pop
-
-  WHY: Git state can drift between sessions. Catching mismatches early prevents confusion when code does not behave as expected.
-</step>
-
-<step name="determine_next_action" priority="fifth">
-  Read next_required_action from STATE.md. This is the SINGLE next action.
-
-  MAP the action to a clear instruction:
-
-  /sdlc:spec → "Create the next specification"
-  /sdlc:impl → "Implement the current specification"
-  /sdlc:verify → "Verify acceptance criteria"
-  /sdlc:review → "Review for engineering law compliance"
-  /sdlc:close → "Close the current loop"
-  /sdlc:transition → "Transition to the next phase"
-  /sdlc:milestone → "Complete or create a milestone"
-
-  WHY: Exactly ONE next action. Not two options. Not "you could do X or Y." The state machine has already decided. The user just needs to execute it.
-</step>
-
-<step name="archive_handoff" priority="sixth">
-  IF HANDOFF.md was consumed:
-    Move it to .sdlc/HANDOFF-{timestamp}.md.archived (rename, do not delete)
-    This prevents the next resume from re-reading stale context.
-
-  Update .sdlc/STATE.md:
-  - Remove paused_at field (session is now active)
-  - Add history entry: "{timestamp} | resume | Resumed from {loop_position}. Time since pause: {duration}."
-
-  Display:
-  ```
-  Resumed at: {loop_position}
-
-  NEXT ACTION REQUIRED: {next_required_action}
-  Run {next_required_action} to continue.
-  ```
-
-  WHY: Archiving (not deleting) the handoff preserves the audit trail while preventing stale context from confusing future resumes.
-</step>
-
-</process>