菜单
[Task Mgmt] Verification tool for validating task completion in Review section. Use when checking if tasks are actually done before moving from Review to Done. Verifies subtask completion, code/file changes, and task-work alignment. Optional but recommended for quality assurance. (user)
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
[Utility] Analyzes user prompts and efficiently loads only relevant rule documents. Auto-generates category-document mapping config file on first invocation by scanning project documents. Supports both automatic and manual invocation. (project)
[Dev] Extracts and organizes best practices for a given topic into a minimal tree structure (max depth 3, max 5 children per node). Use during task planning when writing subtasks in Docs/{name}_Task.md - output is added under each subtask as a concise reference guide. Pure reasoning task with strict formatting rules: keywords/noun phrases only, no prose. (project)
[Utility] Analyzes user prompts and efficiently loads only relevant rule documents. Auto-generates category-document mapping config file on first invocation by scanning project documents. Supports both automatic and manual invocation. (project)
[Design System] Quantitative accessibility audit for UI - contrast ratios, font sizes, tap targets, heading hierarchy. Use when (1) checking WCAG color contrast compliance, (2) auditing text sizes for readability, (3) validating touch/click target sizes, (4) reviewing heading structure and landmarks, (5) user asks to 'check accessibility', 'audit contrast', 'WCAG compliance', or 'a11y check'.
[Aesthetics] Positions aesthetics within art/design history, identifies what traditions it echoes, and spots clichés, generic trends, and AI-slop patterns to avoid. Outputs Critical Notes as Memo nodes in Brain canvas.
[Aesthetics] Maps aesthetic briefs to cultural references: art movements, photography, film, architecture, music, fashion. Outputs reference lists with visual language analysis. Organizes findings as Image and Memo nodes in Brain canvas.
| name | task-valid-review |
| description | [Task Mgmt] Verification tool for validating task completion in Review section. Use when checking if tasks are actually done before moving from Review to Done. Verifies subtask completion, code/file changes, and task-work alignment. Optional but recommended for quality assurance. (user) |
Verification skill for validating task completion. Use this when reviewing tasks in the Review section to check if work is actually complete before moving to Done.
| Situation | Usage |
|---|---|
| Task is in Review section | Verify before moving to Done |
| User wants to check completion | Run validation checklist |
| Uncertain if work matches task | Generate validation report |
Note: This is a verification tool for the Review stage, not a mandatory gate. AI moves tasks to Review first, then this tool helps verify completion.
Check if all subtasks are completed.
Validation Steps:
1. Count total subtasks under parent task
2. Count completed subtasks (- [x])
3. If incomplete subtasks exist → List them
4. Determine if task is ready for Done
Check if actual changes exist for code-related tasks.
| Task Type | Expected Evidence |
|---|---|
| New Feature | New files created OR existing files modified |
| Bug Fix | Code changes in relevant files |
| Refactoring | File modifications detected |
| UI/UX | View/Component files changed |
| Documentation | .md files created/modified |
Verification Method:
git status # Check current changes
git diff --stat HEAD~N # Check recent commits
Check if completed work matches the task description.
| Check | Description |
|---|---|
| Title Match | Work addresses what the task title describes |
| Scope Match | All aspects mentioned in subtasks are addressed |
| No Partial Work | No "TODO" or "FIXME" left in new code |
| Build Success | Code compiles without errors |
On Validation PASS:
## Task Validation: PASS ✅
**Task:** [Task Title]
**Subtasks:** 5/5 completed
**Files Changed:** 3 files (+120, -45 lines)
**Evidence:**
- Created: `Sources/Features/Login/LoginView.swift`
- Modified: `Sources/App/AppCoordinator.swift`
→ Ready to move from Review to Done
On Validation FAIL:
## Task Validation: FAIL ❌
**Task:** [Task Title]
**Reason:** [Specific failure reason]
**Issues Found:**
1. ❌ Subtasks incomplete: 2/5 completed
- [ ] Add form validation logic
- [ ] Handle error states
2. ❌ No file changes detected
**Recommended Actions:**
- Complete remaining subtasks
- Move back to Worker for more work
| Task Type | Valid Reason for No Code |
|---|---|
| Research/Analysis | Output is documentation or notes |
| Planning | Output is plan document |
| Review | Output is review comments |
| Documentation-only | Only .md files expected |
| Skill | When to Use |
|---|---|
task-mover | Move task from Review to Done after verification |
task-segmentation | If subtasks need more breakdown |
task-add | When discovering additional work needed |
history-logger | After task moves to Done, log completion |