菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/laurigates/claude-plugins --skill project-continue命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| 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 |
| 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:
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:
docs/prds/
docs/blueprint/feature-tracker.json tasks section
docs/blueprint/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.
Install, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.