Help us improve
Share bugs, ideas, or general feedback.
From project-plugin
Analyzes git status, PRDs, feature trackers, and work orders to identify next development task and resume work via TDD workflow.
npx claudepluginhub laurigates/claude-plugins --plugin project-pluginHow this skill is triggered — by the user, by Claude, or both
Slash command
/project-plugin:project-continuesonnetThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Continue project development by analyzing current state and resuming work.
Executes plan tasks one at a time with TDD, reviewing diffs before each commit and enforcing project architecture standards. Useful for structured, incremental coding workflows.
Routes sessions in long-task projects to the correct phase skill by checking files like bugfix-request.json, feature-list.json, design docs, and codebase state.
Share bugs, ideas, or general feedback.
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:
Check current state:
# Check git status
git status
# Check recent commits
git log -5 --oneline
# Check current branch
git branch --show-current
Read project context:
.claude/blueprints/prds/
docs/blueprint/feature-tracker.json tasks section
.claude/blueprints/work-orders/
Analyze state and determine next task:
If uncommitted changes exist:
If on clean state:
Report status before starting:
📊 Project Status:
Current Branch: [branch]
Uncommitted Changes: [yes/no - list files if yes]
Recent Work:
- [Last 3 commits]
PRDs Found:
- [List PRD files with brief summary]
Work Overview: Phase [N] - [Phase name]
✅ Completed: [N] tasks
⏳ In Progress: [Current task if any]
⏹️ Pending: [N] tasks
Next Task: [Identified next task]
Approach: [Brief plan]
Begin work following TDD:
Update feature tracker as you go:
Important:
Handling Common Scenarios:
Scenario: Starting new feature:
/blueprint-work-orderScenario: Blocked by dependency:
Scenario: Tests failing:
Scenario: Unclear what to do next:
For large codebases with multiple work fronts, spawn teammates for parallel progress:
| Teammate | Focus | Value |
|---|---|---|
| Research teammate | Investigate codebase state, PRDs, work-orders | Parallel context gathering |
| Implementation teammate | Begin work on next task from feature tracker | Start implementation immediately |
The research teammate gathers project state while the implementation teammate begins the most obvious next task. This is optional — single-session continuation works for most projects.