tim-hub/powerball-harness / harness/skills/harness-review
harness-review
VerifiedMulti-angle code and plan review with security, scope, and UI profiles. Use when reviewing code, plans, PRs, or running pre-merge quality gates.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.2 KB |
| references/code-review.md | markdown | 2.1 KB |
| references/codex-closeout.md | markdown | 2.6 KB |
| references/codex-review.md | markdown | 1.2 KB |
| references/dual-review.md | markdown | 2.8 KB |
| references/governance.md | markdown | 2.2 KB |
| references/opencode-review.md | markdown | 2.3 KB |
| references/plan-review.md | markdown | 891 B |
| references/result-schema.md | markdown | 2.7 KB |
| references/scope-review.md | markdown | 344 B |
| references/security-profile.md | markdown | 11.8 KB |
| references/team-debate.md | markdown | 2.0 KB |
| references/ui-rubric.md | markdown | 7.3 KB |
| references/verdict-framework.md | markdown | 1.6 KB |
references/plan-review.md
View on GitHub# Plan Review Flow
## Steps
1. Read `Plans.md`
2. Review from 5 perspectives:
- **Clarity**: Are task descriptions clear?
- **Feasibility**: Is it technically feasible?
- **Dependencies**: Are inter-task dependencies correct? (Depends column entries match actual dependencies?)
- **Acceptance**: Are completion criteria (DoD column) defined and verifiable?
- **Value**: Does this task solve a user problem? Is "whose problem" stated? Were alternatives considered? Are there Elephants (problems everyone notices but no one addresses)?
3. DoD / Depends column quality checks:
- Tasks with empty DoD → Warning ("Completion criteria undefined")
- Unverifiable DoD ("looks good", "works properly") → Warning + concretization suggestion
- Depends referencing non-existent task numbers → Error
- Circular dependencies → Error
4. Present improvement suggestions
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |