zcross00/planner-review
skills/planner-review/SKILL.md
PLANNER REVIEW SKILL — Review a completed backlog item and update design artifacts accordingly. USE FOR: PLANNER reviewing an EXECUTOR's completed work; updating FEATURES.md after a feature lands; removing completed items from BACKLOG.md; checking for drift. DO NOT USE FOR: implementing backlog items (EXECUTOR work); initial planning (read GOALS and DESIGN directly).
development
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add zcross00/ProcessDocumentation planner-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 4:12 PM132.4s1 file scanned
SKILL.md
- name:
- planner-review
- description:
- PLANNER REVIEW SKILL — Review a completed backlog item and update design artifacts accordingly. USE FOR: PLANNER reviewing an EXECUTOR's completed work; updating FEATURES.md after a feature lands; removing completed items from BACKLOG.md; checking for drift. DO NOT USE FOR: implementing backlog items (EXECUTOR work); initial planning (read GOALS and DESIGN directly).
Planner Review
Use this skill after an EXECUTOR reports that a backlog item is complete. The PLANNER verifies the work and updates design artifacts.
Step 1 — Read the Backlog Item
Open design/BACKLOG.md and find the reported BL-N. Read the full detail block, including:
- The description of what was requested.
- The Done-when criteria.
- The Design-Ref.
Step 2 — Verify Completion
Check each Done-when criterion against the actual codebase:
- Read the files mentioned or implied by the criteria.
- Run
build-verify(or confirm the EXECUTOR already did). - Confirm all criteria are met. If any criterion is not met, stop and communicate to the user what is incomplete.
Verdict: All done-when criteria pass → proceed. Any criterion fails → report the gap; do not update artifacts.
Step 3 — Update FEATURES.md
If the completed item was type Feature or Rework that adds visible capability:
- Open
design/FEATURES.md. - Find the goal section matching the item's linked goal.
- Add a row to the feature table:
| [Feature name] | [Brief description] | BL-N | YYYY-MM-DD |
If the feature doesn't clearly map to a goal, add it to the Features Without Goal Link section and consider logging drift.
Step 4 — Remove from BACKLOG.md
Delete both the table row and the detail block for the completed BL-N. Do not renumber other items.
If priority section becomes empty after removal, leave the section header in place.
Step 5 — Check for Follow-Up Work
Review the implementation for:
- Drift — Does anything in the implementation work against a stated goal? If yes, use the drift-entry skill.
- New backlog items — Did the implementation reveal needed follow-up work? If yes, use the backlog-entry skill.
- Design updates — Does
design/DESIGN.mdneed to reflect new decisions, constraints, or changes that emerged during implementation? If yes, update the relevant section.
Step 6 — Communicate
Report the review result to the user:
- Confirmed complete, artifacts updated.
- Or: incomplete, with specific gaps listed.
Related Skills
zcross00/test-writing
development
VerifiedTrustedCommunity
TEST WRITING SKILL — Write correctly structured JUnit 5 tests that match this project's conventions. USE FOR: adding tests for a new backlog item; flagging missing test coverage; writing tests for engine classes, domain logic, or persistence. Covers class placement, naming conventions, setup patterns, assertion style, and what not to test. DO NOT USE FOR: running tests (use build-verify skill); diagnosing test failures (read the Surefire report directly).
SKILL.mdUpdated Apr 25, 2026
zcross00/standards-check-java
development
VerifiedTrustedCommunity
STANDARDS CHECK JAVA SKILL — Apply standards/general.md and standards/java.md systematically to a Java file or diff. USE FOR: pre-commit standards compliance check; reviewing a file for standards adherence before or after a change. Produces a categorized violation list with the specific rule cited for each. DO NOT USE FOR: general code review (use planner-review skill for implementation review).
SKILL.mdUpdated Apr 25, 2026
zcross00/refinement
testing
VerifiedTrustedCommunity
REFINEMENT SKILL — Analyze design, features, backlog, and drift to identify and plan needed work. USE FOR: PLANNER producing new backlog items from gaps between design and current state; evaluating tech debt and drift for resolution; structured backlog growth when the user asks the PLANNER to refine or plan more work. DO NOT USE FOR: implementing backlog items (EXECUTOR work); reviewing completed work (use planner-review skill).
SKILL.mdUpdated Apr 25, 2026
zcross00/git-workflow
testing
VerifiedTrustedCommunity
GIT WORKFLOW SKILL — Exact command sequences for all branch lifecycle operations in this project. USE FOR: creating a work branch for a backlog item; committing and merging work; tagging design versions or releases. Eliminates the need to look up git-workflow.md during implementation. DO NOT USE FOR: deciding what to work on (use backlog-entry or agent-orientation).
SKILL.mdUpdated Apr 25, 2026