메뉴
Interactive spec review via Plannotator. Use after writing a spec document (design doc, SPEC file) to let the user review it with inline annotations before committing. Auto-detects the most recently written spec file.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user wants to do a QA session or report multiple bugs — interactive session where bugs are reported conversationally and agents fix them in parallel
Use when executing implementation plans with independent tasks — orchestration pattern for worktree isolation, TDD discipline, and two-stage review. Referenced by execute-plan, fixit, and bugbash.
Use when the user reports a bug or issue that can be fixed without blocking their current work — backgrounds an agent in a worktree to fix and merge back without breaking stride
Use after implementing changes in an OpenSpec project to review implementation against the active change's deltas — auto-fixes confident issues, parks questions for the user
Install the anutron (claude-skills) kit into the current project — symlinks or copies skills, registers hooks, compiles CLAUDE.md from snippets.
Uninstall the anutron (claude-skills) kit from the current project — reverses everything /anutron-install did.
| name | plannotator-specs |
| description | Interactive spec review via Plannotator. Use after writing a spec document (design doc, SPEC file) to let the user review it with inline annotations before committing. Auto-detects the most recently written spec file. |
| allowed-tools | Bash(plannotator:*), Bash(find:*), Bash(git status:*), Read, Edit |
| tags | ["plannotator"] |
Review a spec document interactively using Plannotator annotations, then iterate on feedback until the user approves.
find specs -name "*.md" -type f 2>/dev/null | head -10git status --short 2>/dev/null | head -20Determine which spec file to review:
$ARGUMENTS is provided, use that as the file pathspecs/)git status for recently added or modified .md files in spec directoriesRun the plannotator annotate command on the identified spec file. The user will review it in their browser and leave inline comments.
If $ARGUMENTS was provided and you identified the file in step 1, run:
plannotator annotate <spec-file-path>
If $ARGUMENTS was not provided, you must first identify the file (step 1), then run the command with the resolved path.
After the user submits their annotations:
After addressing all comments, re-open the spec in Plannotator so the user can verify the changes and leave additional comments if needed.
Repeat steps 3-4 until the user has no more comments. The user signals approval by submitting with no annotations or by saying they approve.
Once the user approves:
The spec file is now reviewed and ready for the next step in whatever workflow invoked this skill.