Writer critic pair
Skill roronoazoroshao369/vibe-coding-os/skills/agents/writer-critic-pair
Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.From the repository description
npx -y skills add roronoazoroshao369/vibe-coding-os --skill writer-critic-pairAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.5 KB, 480 tokens by cl100k_base, as published. Nobody here has run it
Writer-Critic Pair
Purpose
Use a two-role agent pattern where a writer or implementer creates the artifact and a critic or reviewer independently challenges it before final delivery.
When to use
Use for complex implementations, risky changes, architecture decisions, high-stakes user communication, ambiguous requirements, security-sensitive work, or any task where same-context self-approval would be too weak.
Inputs
Original task, acceptance criteria, scope boundaries, writer output or diff, validation results, repository conventions, known risks, and time or tool constraints.
Workflow
- Assign the writer to understand the task, inspect context, propose or implement the smallest correct solution, and report verification honestly.
- Assign the critic to read the original task and evidence independently before reading the writer's summary.
- The critic challenges correctness, assumptions, scope, tests, compatibility, safety, and maintainability.
- The writer responds with a fix plan, applies necessary changes, and records any deferred risks.
- The critic re-reviews the revised artifact or explicitly states why re-review was not possible.
- The final owner synthesizes the result and decides whether to ship, revise, or ask for clarification.
Outputs
A handoff with:
- Task: original goal and constraints.
- Writer output: summary, changed files or artifact, and verification run.
- Critic findings: critical, important, and minor findings with evidence.
- Writer response: fixes applied, deferred items, and rationale.
- Re-review: critic result after fixes.
- Final decision: ship, revise, or ask.
Failure modes
- Writer and critic share the same assumptions and miss the same bug.
- Critic rubber-stamps instead of adversarially checking evidence.
- Roles edit the same files concurrently and create conflicting changes.
- Handoff omits validation results or known limitations.
- Critic blocks on taste rather than task risk.
- Final owner ignores unresolved critical findings.
Verification checklist
- Writer and critic responsibilities are distinct.
- Critic reviewed against the original task, not only the writer summary.
- Findings are severity-ranked and evidence-based.
- Writer response addresses or explicitly defers each critical and important finding.
- Final decision reflects re-review status and residual risk.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.