Critic Dispatch Skill

Manage @critic agent review frequency during PRD development.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/mdmagnuson-creator/helm-ade-toolkit --skill critic-dispatch-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Critic Dispatch Skill
Source: https://github.com/mdmagnuson-creator/helm-ade-toolkit/tree/main/skills/critic-dispatch
Command: npx skills add https://github.com/mdmagnuson-creator/helm-ade-toolkit --skill critic-dispatch-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps manage the frequency of code reviews (@critic) during the Product Requirement Document (PRD) development process, striking a balance between thoroughness and development speed.

Core Features & Use Cases

  • Configurable Review Cadence: Allows users to set critic review frequency to 'strict', 'balanced', or 'fast' modes.
  • Intelligent Scheduling: Implements specific logic for 'balanced' mode to run reviews at optimal intervals (e.g., every 2-3 stories).
  • Use Case: A development team can use the 'balanced' mode to ensure code quality without slowing down rapid prototyping, while a security-critical project could switch to 'strict' mode for more frequent checks.

Quick Start

Configure the critic mode to 'strict' for the current builder session.

Frequently Asked Questions about Critic Dispatch Skill

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

FAQPage Schema
How do I balance code review frequency with development velocity during PRD creation?

Balanced mode triggers critic reviews at specific story intervals, like every 2-3 stories, ensuring code review thoroughness while maintaining development velocity during PRD creation.

What are the different modes for scheduling automated code reviews?

Scheduling supports strict, balanced, and fast modes. Strict maximizes review frequency for security-critical projects, fast minimizes interruptions for rapid prototyping, and balanced triggers reviews at defined story intervals.

When should I use strict mode versus fast mode for code review automation?

Use strict mode for security-critical projects requiring frequent checks and maximum thoroughness. Use fast mode during rapid prototyping when development velocity is the priority and interruptions must be minimized.

Can I dynamically change the code review cadence using CLI flags?

Yes, you can dynamically control the code review cadence by integrating project-level configuration with CLI flags, allowing you to switch between strict, balanced, and fast execution modes during your builder session.

How do I configure the critic agent to run at specific story intervals?

Configure the critic agent to balanced mode to run reviews at specific story intervals, such as every 2-3 stories. This ensures regular code quality checks without continuously halting the PRD development workflow.