菜单
Dry-run project status report. Produces a read-only snapshot of all feature specs, plans, and task progress without spawning any agents or modifying any files. Use this when the user invokes /review-tasks or asks for a project status snapshot, completion percentage, or "what's left".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | review-tasks |
| description | Dry-run project status report. Produces a read-only snapshot of all feature specs, plans, and task progress without spawning any agents or modifying any files. Use this when the user invokes /review-tasks or asks for a project status snapshot, completion percentage, or "what's left". |
| installed-from | llm_skills |
Produce a read-only status report. Do not modify any files.
docs/features/docs/plans/ and identify specs missing a plandocs/tasks/active/docs/issues/This command is safe to run at any time to get a project snapshot.
docs/
INITIAL_PROMPT.md # Source of truth for product intent (never modified)
features/ # Feature specs — final authority on scope
{feature-slug}.md
plans/ # One plan per feature spec
{feature-slug}-plan.md
tasks/ # Active task files (one at a time per phase)
active/
{feature-slug}-p{N}-t{M}.md
archive/
{feature-slug}-p{N}-t{M}.md
guides/ # Supporting docs, architecture notes (optional)
issues/ # Logged failures and blockers
/continue-tasks — run the full orchestration loop (spawns agents, executes tasks)/update-tasks — sync active task files that may have been completed by agents/reinit — archive legacy state, normalize specs, then launchUse when the user wants to merge dev into main for a production release — covers rebasing dev from main if behind, automatic semantic versioning from conventional commits, merge commit, release tagging, and syncing dev back onto main.
Use when the user wants to ship current working changes through a feature branch PR into the DEV branch — covers pulling latest, staging, committing, pushing, PR creation, merge, branch cleanup, and syncing DEV locally.
Audit all feature specs in docs/features/ against the current template, CAP-ID standards, open questions, logical gaps, and plan coverage — then request user authorization before making any changes
Universal coding patterns, constraints, TDD workflow, atomic todos
Prevent semantic code duplication with capability index and check-before-write
Mandatory code reviews via /code-review before commits and deploys