beo-reviewing

Orchestrate specialist reviews to validate artifacts and enforce quality gates.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/minhtri2710/skills --skill beo-reviewing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beo-reviewing
Source: https://github.com/minhtri2710/skills/tree/main/skills/beo/reviewing
Command: npx skills add https://github.com/minhtri2710/skills --skill beo-reviewing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Post-execution quality gate and review orchestration ensuring artifacts match the original CONTEXT.md, UAT is completed, and learnings are captured.

Core Features & Use Cases

  • Coordinates specialist review subagents (Code Quality, Architecture, Security, Test Coverage, Learnings Synthesis) to validate changes.
  • Verifies artifact integrity, ensures phase contracts alignment, and hands off learnings to beo-compounding for synthesis.
  • Orchestrates gating and task creation (P1/P2/P3) to produce fix beads or independent follow-up beads as needed.

Quick Start

Run beo-reviewing after an epic is ready for review to trigger automated specialist checks and capture learnings.

Frequently Asked Questions about beo-reviewing

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

FAQPage Schema
How do I automate artifact verification and enforce a quality gate before feature completion?

Specialist review orchestration automates artifact verification by validating CONTEXT.md alignment, running human UAT, and enforcing a quality gate before feature completion. It coordinates multiple subagents to validate changes and capture learnings.

What is the process for running specialist reviews to validate code quality and architecture?

Specialist review orchestration coordinates five subagent prompts covering code quality, architecture, security, test coverage, and learnings synthesis. These operate in the post-execution phase to verify artifact integrity and ensure phase contracts alignment.

How do I manage P1, P2, and P3 findings from a software review workflow?

The review workflow orchestrates gating and task creation by transforming P1, P2, and P3 findings into fix beads or independent follow-up beads. This ensures issues identified during artifact verification are tracked and resolved.

When do I need to run a post-execution quality gate for UAT and learnings synthesis?

You need a post-execution quality gate when an epic is ready for review. It triggers automated specialist checks to perform human UAT, verify artifact integrity, and hand off captured learnings to a compounding process for synthesis.

Does this artifact verification process require specific dependencies to run?

No, this artifact verification process operates without external dependencies. It uses internal references to orchestrate five specialist prompts for managing phase transitions and validating CONTEXT.md alignment during the review workflow.