advisor-review-loop-maintainer

What problem does it solve?

It prevents Rudder development work from being accepted after a single author pass by enforcing an advisor-first scenario/requirements phase followed by an independent reviewer acceptance gate.

Core Features & Use Cases

• Advisor-first grounding: converts fuzzy intent into a scenario analysis, requirement map, options, and an evaluation rubric before committing to a direction.
• Independent acceptance pressure: runs two distinct reviewer perspectives to judge whether the proposal solves the right product problem and whether the delivery/validation is trustworthy.
• Iterate until blockers are resolved: supports repeated review rounds (including an additional round when requested or needed) and produces a clean handoff only when remaining risk is explicit.

Quick Start

Use this skill when you want Build Advisor-style scenario and requirement analysis followed by two independent reviewer roles, iterating until the proposal can pass an acceptance gate for the target Rudder development artifact.