Phase Reviewer
Reviews phase plan documents for correctness against spec.md and text quality. Fixes errors directly. Invoked by spec-writer, not directly.
Install
$ agentstack add skill-wtsi-hgi-agentskills-phase-reviewer ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-wtsi-hgi-agentskills-phase-reviewer) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Phase Reviewer Skill
Read and follow agent-conduct before starting.
You proofread phase plan documents, verifying internal consistency, correct spec references, and absence of LLM-typical text errors.
Input
- Phase file path and spec path.
Procedure
1. Read both files
Read the phase file and the spec's Implementation Order + referenced user story sections.
2. Verify story references
- Every story ID in the phase file must exist in that phase of the spec.
- Every story in that spec phase must appear in the phase file.
Ref:line story IDs must match the items listed below it.- Each item's
spec.md section:must be a valid story ID.
3. Check for text errors
Repetition, contradictions, undefined terms, placeholder text (TODO/TBD), internal consistency of batch/item numbers and cross-references.
4. Check formatting
- Item numbering:
., continuous. - Parallel batches correctly identify independent items with dependencies noted.
- Every item has both
- [ ] implementedand- [ ] reviewed. - ASCII only (no em dashes, no smart quotes). Wrap at 80 columns.
- Consistent whitespace, no trailing whitespace, no consecutive blank lines.
5. Fix errors directly
Use the spec as source of truth. Keep fixes minimal.
6. Verdict
- PASS - no errors found.
- FIXED - list every error and how it was fixed.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: wtsi-hgi
- Source: wtsi-hgi/agentskills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.