---
name: project-resume
description: "Full session startup sequence for returning to an already-started project. Triggers automatically when user says /resume, 'resume project', 'continue project', 'pick up where we left off', or 'open project'. Orchestrates persistent-memory load, security scan on changed files, and a gstack engineering review in one shot so the user has full context before writing a single line of code."
---

# Project Resume

Trigger keyword: **/resume**

Also activates on: "resume project", "continue project", "pick up where we left off", "open project [name]"

This skill runs the complete session startup sequence for an existing project. It chains persistent-memory, security-guidance, and gstack-engineering-team together so you walk into every session with full context, a clean security check, and an honest engineering assessment.

---

## Step 1: Identify the Project

When the user says `/resume` or a variant:

If a project name is included (e.g., `/resume my-saas-app`), use that name directly.

If no project name is given, ask exactly one question:

"Which project are we resuming? (If you have multiple memory files, I can list them for you.)"

To list available projects, run:
```bash
python3 /home/ubuntu/skills/persistent-memory/scripts/manage_memory.py list
```

---

## Step 2: Load Project Memory

Read the memory file at `~/.manus-memory/[project-name].md`.

If the file exists, extract and summarize:
- Project overview (what it is, current state)
- Tech stack
- Last 3 session history entries (what was done recently)
- Current status (what is working, in progress, broken)
- Any known issues flagged as HIGH or CRITICAL

Report back in this format:
```
MEMORY LOADED: [project-name]
Last session: [date and summary of last session]
Current status: [working / in progress / blocked items]
Tech stack: [brief stack summary]
Known issues: [any HIGH/CRITICAL items]
Ready to continue from: [what the next logical task is based on memory]
```

If no memory file exists, say:
"No memory file found for '[project-name]'. Would you like me to initialize one now? Say /kickoff [project-name] to set up a full new project session, or I can create a blank memory file and you can fill it in."

---

## Step 3: Quick Security Scan on Changed Files

Run a targeted security scan limited to files changed since the last git commit or in the current working tree.

```bash
# Get list of changed files
git diff --name-only HEAD 2>/dev/null || git status --short 2>/dev/null
```

For each changed file, run a quick scan focused on:
- Hardcoded secrets or API keys added in this diff
- New SQL queries without parameterization
- New `eval()`, `exec()`, or `subprocess` with `shell=True` calls
- New endpoints without auth checks

This is a fast diff-scoped scan, not a full audit. If you find anything, report it immediately as a SECURITY ALERT before proceeding. If nothing is found, say "Quick security scan: clean."

If there are no changed files or no git repo, skip this step and say "No changed files to scan."

---

## Step 4: GStack Engineering Review

Run the Engineering Manager persona from the gstack-engineering-team skill.

Read `~/.manus-memory/[project-name].md` for architecture context, then assess:

1. **Current state:** Based on memory and any code you can see, what is the overall health of the codebase?
2. **Test coverage:** Are tests present? When were they last updated?
3. **Technical debt:** Based on session history, what shortcuts have accumulated?
4. **Recommended next task:** Based on the current status and known issues, what is the single most important thing to work on this session?

Report in this format:
```
ENG REVIEW: [project-name]
Codebase health: [GOOD / NEEDS ATTENTION / CRITICAL ISSUES]
Test coverage: [assessment]
Technical debt: [what has accumulated]
Recommended focus this session: [the one most important task]
```

---

## Step 5: Session Ready Confirmation

After all steps complete, give the user a single clean summary:

```
SESSION READY: [project-name]
========================
Memory: Loaded ([N] sessions of history)
Security: [Clean / N issues found]
Engineering: [health status]

RECOMMENDED: [the single best next action this session]

Available commands this session:
  /review     — code review on any file or recent changes
  /qa         — QA test the current feature
  /cso        — full security audit
  /ship       — pre-ship checklist before deploying
  /save       — save important decisions to memory
  /end        — compress and save this session to memory
```

---

## Reference Files

- See `references/session-patterns.md` for handling common session scenarios (blocked tasks, context gaps, conflicting memory)