ce-doc-review

Run parallel reviewer agents to surface role-specific issues in requirements or plan documents.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026 --skill ce-doc-review-diestok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-doc-review
Source: https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026/tree/main/.agents/skills/compound-engineering/skills/ce-doc-review
Command: npx skills add https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026 --skill ce-doc-review-diestok

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Review requirements or plan documents through multi-persona analysis, enabling parallel surface-level critique by role-specific agents to surface issues earlier and guide improvements.

Core Features & Use Cases

  • Parallel persona reviewers surface coherence, feasibility, security, and scope concerns in a single document review session.
  • Auto-apply safe_auto corrections where a single, mechanical fix exists, and route remaining findings through Open Questions, bulk previews, and guided routing to determine next actions.
  • Supports both interactive and headless modes, delivering structured findings ready for review, triage, and planning conversations.

Quick Start

Provide a document path to review (e.g., docs/plans/feature.md) and ce-doc-review will surface a structured multi-persona findings report.

Frequently Asked Questions about ce-doc-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a multi-persona document review for requirements and plans?

Parallel reviewer agents run multi-persona document review to surface role-specific issues in requirements or plan documents. Provide a document path to generate a structured findings report for triage and planning conversations.

How does multi-agent document review classify and route findings?

Multi-agent document review classifies findings into safe_auto, gated_auto, manual, and FYI categories. Safe_auto corrections apply mechanical fixes automatically, while remaining findings route through Open Questions and bulk previews for guided decisions.

Can I automate requirements document review in a headless workflow?

Yes, requirements document review supports both interactive and headless workflows. Headless mode delivers structured findings ready for automated triage without manual input, routing issues through Open Questions when needed.

What issues does parallel persona review surface in plan documents?

Parallel persona review surfaces coherence, feasibility, security, and scope concerns in plan documents. Role-specific agents analyze the document in a single session to identify these issues earlier and guide improvements.

What is the best way to triage findings from a multi-persona requirements review?

The best way to triage findings is using the structured findings pipeline that outputs named frontmatter and a findings schema. This pipeline applies per-finding decision processes with safe_auto, gated_auto, manual, and FYI classifications for guided routing.