consensus-specialist

Dispatch phase-specific specialists to rewrite artifacts and generate patch files.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/mytechsonamy/VibeFlow --skill consensus-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consensus-specialist
Source: https://github.com/mytechsonamy/VibeFlow/tree/main/skills/consensus-specialist
Command: npx skills add https://github.com/mytechsonamy/VibeFlow --skill consensus-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Consensus Specialist orchestrates targeted phase-specific rewrites by dispatching the appropriate subagent without touching the source, ensuring structured, review-driven artifact improvements.

Core Features & Use Cases

  • Dispatches the correct phase-specialist (prd-rewriter, adr-author, design-spec-refiner, test-strategy-refiner, coverage-gap-filler, or runbook-editor) based on vibeflow.config.json.currentPhase.
  • Produces a patch file and a decisions report for operator review, avoiding direct edits to source code.
  • Supports safe, diff-first collaboration across requirements, design, architecture, planning, testing, and deployment phases.

Quick Start

Invoke the consensus-specialist with a session ID to dispatch the correct phase specialist and generate a patch for review.

Frequently Asked Questions about consensus-specialist

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

FAQPage Schema
How do I apply multi-AI reviewer feedback to rewrite artifacts without altering source files?

To rewrite artifacts without altering source files, the consensus specialist dispatches phase-specific subagents to process reviewer feedback and generate a patch file with a decisions report for safe, diff-first operator review.

What is the best way to orchestrate phase-specific rewrites for requirements, design, and testing artifacts?

Orchestrating phase-specific rewrites involves dispatching the correct specialist, such as a prd-rewriter or test-strategy-refiner, based on the current vibeflow configuration to produce a targeted patch for operator review.

Do I need a valid consensus session ID to generate a patch from reviewer verdicts?

Yes, generating a patch from reviewer verdicts requires a valid consensus session ID and access to the .vibeflow state directory to locate the verdicts and safely generate the patch file.

Can I use this consensus workflow to refactor architecture decision records and deployment runbooks?

Yes, you can use this workflow to refactor artifacts like architecture decision records and deployment runbooks by dispatching the adr-author or runbook-editor subagents to generate review-driven patches.

Why does the consensus specialist avoid direct edits to source code during the review workflow?

The consensus specialist avoids direct edits to source code to ensure structured, review-driven artifact improvements by producing a diff-first patch file and decisions report for the operator to review before applying changes.

Which vibeflow phases are supported for coverage gap filling and design spec refinement?

Coverage gap filling and design spec refinement are supported across six vibeflow phases, dispatching specialists like the coverage-gap-filler and design-spec-refiner to generate targeted patches based on multi-AI reviewer feedback.