Menü
Leave structured review comment via Beads
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Install Pasture binaries (pastured, pasture, pasture-release) from GitHub Releases, go install, or Nix
Pasture protocol reference documentation — 12-phase workflow, agent roles, constraints, and coding standards. Read when you need to understand the full workflow or look up conventions.
Create handoff document and transfer to supervisor
Create PROPOSAL-N task with full technical plan
Ratify proposal, mark old proposals pasture:superseded
Spawn 3 axis-specific reviewers (A/B/C)
| name | reviewer-comment |
| description | Leave structured review comment via Beads |
Command: pasture:reviewer:comment — Leave structured review comment via Beads
-> Full workflow in PROCESS.md <- Phases 4 + 10
[rev-comment-structured]
[rev-comment-beads]
bd comments addDocumenting review findings for the permanent record. Applies to both plan reviews (Phase 4) and code reviews (Phase 10).
bd show <task-id>)# Plan review comment (no severity tree)
bd comments add <proposal-id> "VOTE: ACCEPT - End-user alignment confirmed. MVP scope achievable."
# Code review comment (with severity references)
bd comments add <review-id> "VOTE: REVISE - 1 BLOCKER found (see severity tree). Suggestion: fix type error in auth middleware."
VOTE: {ACCEPT | REVISE}
## Findings
### BLOCKER Issues
{list or "None"}
### IMPORTANT Issues
{list or "None"}
### MINOR Issues
{list or "None"}
## Conclusion
{assessment and next steps}
| Severity | When to Use | Blocks? |
|---|---|---|
| BLOCKER | Security, type errors, test failures, broken production code paths | Yes (code review only) |
| IMPORTANT | Performance, missing validation, architectural concerns | No (follow-up epic) |
| MINOR | Style, optional optimizations, naming improvements | No (follow-up epic) |
pasture:p4-plan:s4-review): ACCEPT/REVISE only. No severity tree. Findings are described inline in the vote comment.pasture:p10-impl:s10-review): ACCEPT/REVISE vote + full severity tree with EAGER creation (3 groups per round). Findings are tracked as child tasks of severity groups.