Help us improve
Share bugs, ideas, or general feedback.
From great_cto
Resumes a previous session by collecting project context from logs, tasks, decisions, git status, open PRs, and more to produce a structured snapshot in under 60 seconds.
npx claudepluginhub avelikiy/great_ctoHow this command is triggered — by the user, by Claude, or both
Slash command
/great_cto:resume [project-path] — defaults to current directoryhaikuThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
You are the great_cto `/resume` command. Your job is to restore full session context in under 60 seconds so the CTO can continue exactly where they left off — without re-explaining the project, stack, or pending work. ## Step 1 — Collect context (run all in parallel) Read the 3 most recent session logs: ## Step 2 — Build the context snapshot If `NO_PROJECT` — stop and say: Otherwise synthesize everything into a **single structured snapshot**: --- ### 📍 Project: `<name>` · `<archetype>` · `<phase>` **Stack:** `<stack from PROJECT.md>` **Team:** `<team-size>` · **Mode:** `<mode>`...
/catchupRestores project context after /clear by reading core docs like CLAUDE.md and memory-bank files, git status/logs/diffs, and sessions; outputs markdown summary of status, recent work, tasks, and next steps. Also supports deep/quick modes.
/syncBootstraps session by reading project context (README.md, AGENTS.md, CLAUDE.md, PLAN.md), restores .claude/session-cache.json state, shows status. Supports --verbose, --diff, --git, --status.
/primePrimes fresh session context with git snapshot (branch, status, commits, stashes) and task-relevant repo analysis via subagents. Supports [task hint], --quick, --verbose.
/continueResumes prior session by scanning progress files and git state, summarizes work status with branch/phase details and next action, then loads context after confirmation.
/briefGenerates a concise visual briefing on project state, progress, key decisions, blockers, and next steps from git status, specs, tasks, and context.
/resumeResumes a previously-running Claude agent by ID, picking up its transcript and continuing the interrupted task.
Share bugs, ideas, or general feedback.
You are the great_cto /resume command. Your job is to restore full session context in under 60 seconds so the CTO can continue exactly where they left off — without re-explaining the project, stack, or pending work.
# Project identity
cat .great_cto/PROJECT.md 2>/dev/null || echo "NO_PROJECT"
# Recent session logs (last 3)
ls -t .great_cto/logs/session-*.md 2>/dev/null | head -3
# Open tasks (Beads or tasks.md)
cat .great_cto/tasks.md 2>/dev/null | grep -E "^\- \[ \]|^## " | head -20
# Recent decisions
tail -60 docs/decisions/DECISION-LOG.md 2>/dev/null || echo "NO_DECISION_LOG"
# Latest ADR
ls -t docs/decisions/ADR-*.md 2>/dev/null | head -1 | xargs head -20 2>/dev/null
# Open gates
find .great_cto/verdicts -name "*.md" 2>/dev/null | xargs grep -l "status: open\|OPEN\|pending" 2>/dev/null | head -5
# Git: last 5 commits
git log --oneline -5 2>/dev/null || echo "NO_GIT"
# Git: what's dirty / in progress
git status --short 2>/dev/null | head -10
# Open PRs
gh pr list --state open --limit 5 --json number,title,reviewDecision 2>/dev/null | python3 -c "import json,sys; prs=json.load(sys.stdin); [print(f'PR #{p[\"number\"]}: {p[\"title\"]} [{p.get(\"reviewDecision\") or \"pending\"}]') for p in prs]" 2>/dev/null || true
# Graphify graph (if present)
[ -f graphify-out/GRAPH_REPORT.md ] && head -20 graphify-out/GRAPH_REPORT.md || true
Read the 3 most recent session logs:
for LOG in $(ls -t .great_cto/logs/session-*.md 2>/dev/null | head -3); do
echo "=== $LOG ==="
cat "$LOG"
echo ""
done
If NO_PROJECT — stop and say:
No .great_cto/PROJECT.md found in this directory.
Run `npx great-cto init` to set up this project, or `cd` into your project root.
Otherwise synthesize everything into a single structured snapshot:
<name> · <archetype> · <phase>Stack: <stack from PROJECT.md>
Team: <team-size> · Mode: <mode>
Compliance: <compliance>
<date of most recent log>
What was done:
<bullet 1 from log><bullet 2 from log>Decisions made:
<any decisions recorded>Left pending:
<pending items from log>If no logs exist: "No session logs found — this appears to be a fresh project."
List up to 8 open tasks from tasks.md or Beads. If none: "No open tasks recorded."
From DECISION-LOG.md and latest ADR. If none: "No decisions logged yet."
<last 5 oneline><git status short><list or "none">List any verdicts with status: open. If none: "All gates clear."
1. THIS SNAPSHOT — what was decided, what's pending
2. .great_cto/ — PROJECT.md, logs, verdicts for deeper context
3. Source code — only when editing or snapshot doesn't answer
End with exactly one of:
If clear next step exists:
Ready. Continuing from: <last pending item>.
Say "go" to start, or tell me what to work on first.
If ambiguous:
Ready. Last session ended without a clear next step.
What would you like to tackle?
1. <most likely next thing based on context>
2. <second option>
3. Something else
mkdir -p .great_cto/logs
echo "resumed: $(date -u +%Y-%m-%dT%H:%M:%SZ)" >> .great_cto/logs/.last-resume
graphify-out/graph.json), mention it: "Codebase graph available — Claude will query it before reading source files"