/forge-resume — Resume a FORGE Project
Resumes work on an existing FORGE project by analyzing the current state and identifying the next action to take.
Workflow
- Verify that FORGE is initialized:
- Read .forge/config.yml — if absent, suggest /forge-init - Read CLAUDE.md for project context
- Analyze the project state:
- Read .forge/sprint-status.yaml for sprint state - Read docs/ for existing artifacts: - docs/prd.md exists? → Planning done - docs/architecture.md exists? → Architecture done - docs/ux-design.md exists? → UX done - docs/stories/*.md exist? → Stories decomposed - Identify stories by status: - completed: finished - in_progress: in progress (priority) - pending: to do - blocked: blocked (identify blockers) - Vector search for recent context: forge-memory search "<project name> recent activity" --limit 3 → Load relevant history to better contextualize the resume
- Determine the next action: Case A — No artifacts: → Suggest
/forge-planto start planning Case B — PRD exists, no architecture: → Suggest/forge-architectCase C — Architecture exists, no stories: → Suggest/forge-storiesCase D — Stories exist, some pending: → Suggest/forge-build STORY-XXXfor the next unblocked story Case E — Story in_progress: → Resume the current story with/forge-build STORY-XXX→ Read the already written code and existing tests Case F — All stories completed: → Suggest/forge-verifyfor a global QA audit → Or/forge-storiesto decompose new stories - Display the resume report:
FORGE — Resuming project <name> ───────────────────────────────── Stack: <type> / <language> Sprint: #<id> Stories: X completed / Y in_progress / Z pending / W blocked Last: STORY-XXX (<status>) — <title> Artifacts: [OK] docs/prd.md [OK] docs/architecture.md [--] docs/ux-design.md (missing) [OK] docs/stories/ (N stories) Recommended next action: → /forge-build STORY-XXX — <story title> - Propose available actions:
- Continue development (recommended action) - View full status (/forge-status) - Go back (re-plan, re-architect) - Add new stories
Notes
- This skill is the entry point when opening an existing FORGE project
- It does not modify any files, it only analyzes and recommends
- Compatible with projects initialized manually or via
/forge-init - If sprint-status.yaml is missing but artifacts exist, the skill reconstructs the state from the existing files