project-continue

description	Resume development from current project state. Use when the user asks to continue work, pick up where we left off, find the next task, or resume a TDD cycle after a break.
args	[--task <id>] [--skip-status]
argument-hint	--task to resume specific task, --skip-status to skip state analysis
allowed-tools	Read, Bash(git status *), Bash(git log *), Bash(git branch *), Grep, Glob, Edit, Write
created	"2025-12-16T00:00:00.000Z"
modified	"2026-06-05T00:00:00.000Z"
reviewed	"2026-06-05T00:00:00.000Z"
name	project-continue

/project:continue

When to Use This Skill

Use this skill when...	Use project-discovery instead when...
Resuming work on a known project with PRDs and feature-tracker state	Entering an unfamiliar codebase needing orientation on tooling/structure
Picking the next task off the feature tracker after a break	Use project-test-loop instead when the next step is iterating on failing tests
Asking "what's next" in a project with established blueprint state	Use project-init instead when no project structure exists yet
Resuming a TDD session and beginning implementation yourself	Use /blueprint:execute instead when you want blueprint to pick and run the next logical blueprint action (derive/sync/work-order) rather than continue coding

Continue project development by analyzing current state and resuming work.

Note: Configure project-specific test/build commands in CLAUDE.md or .claude/rules/ for automatic detection.

Steps:

1. Check current state:

   # Check git status
   git status
   
   # Check recent commits
   git log -5 --oneline
   
   # Check current branch
   git branch --show-current
   

2. Read project context:

   • PRDs: Read all files in docs/prds/
     • Understand project goals and requirements
     • Identify features and phases
   • Feature Tracker: Read docs/blueprint/feature-tracker.json tasks section
     • Current phase and progress
     • Completed, in-progress, and pending tasks
   • Work Orders: Check docs/blueprint/work-orders/
     • Recent work-orders (see what's been done)
     • Pending work-orders (see what's planned)

3. Analyze state and determine next task:

   If uncommitted changes exist:

   • Review uncommitted files