skills.rest
thefrederiksen
thefrederiksenCOMMUNITY
Explore all skills by this author →
GitHub

wingman-brief-reviewer

Reviews saved wingman turn briefs through blind reads and evidence checks with scored verdicts.

96|11|Updated Feb 8, 2026
Search Tags:#agent supervision#retired#wingman#brief review#devthrottle#turn verdict#cold reader
One-click install
npx skills add https://github.com/thefrederiksen/devthrottle --skill wingman-brief-reviewer-thefrederiksen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wingman-brief-reviewer
Source: https://github.com/thefrederiksen/devthrottle/tree/main/.claude/skills/wingman-brief-reviewer
Command: npx skills add https://github.com/thefrederiksen/devthrottle --skill wingman-brief-reviewer-thefrederiksen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill is RETIRED as of 2026-09-16 and must not be run. It previously automated cold-reader review of wingman turn briefs, judging whether a brief gave a busy operator all decision-relevant information in the simplest form. Its function was replaced by the turn VERDICT mechanism (docs/architecture/wingman/TURN_VERDICT.md) and owner-reported corrections via the verdict panel. ## Core Features & Use Cases - Historical record: Kept deliberately to document the cold-reader reasoning that the verdict's label, summary, and receipt rules inherited. - Blind-read methodology: Describes a two-phase review where a subagent judges the brief alone, then a reviewer checks it against terminal evidence. - Use Case: Read this Skill only as design history when working on the turn VERDICT specification or the WINGMAN charter; do not execute its review loop, since the brief writer, contract class, and brief store it references no longer exist. ## Quick Start Do not run this retired skill; instead read docs/architecture/wingman/TURN_VERDICT.md for the mechanism that replaced it.

Frequently Asked Questions about wingman-brief-reviewer

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

FAQPage Schema
Can I still run the wingman-brief-reviewer skill?▼

No, the skill was retired on 2026-09-16 and must not be run. The brief writer was retired in issue #549, the TurnBriefContract.cs class was deleted, and the gateway-turnbriefs store is no longer written to.

What replaced the wingman brief review loop?▼

The turn VERDICT replaced it: one structured question per stop answered against a closed vocabulary and validated mechanically. Wrong verdicts are reported by the owner through a verdict panel via POST /sessions/{sid}/turn-verdict/feedback, not reviewed by a model.

Why was the wingman-brief-reviewer kept instead of deleted?▼

It was kept deliberately as a historical record. The cold-reader framing and the rounds of findings it documents are the reasoning behind the verdict's label, summary, and receipt rules, so deleting it would leave a hole in the design argument.

Where is the specification for the turn VERDICT mechanism?▼

The specification lives at docs/architecture/wingman/TURN_VERDICT.md, and the charter section is docs/wingman/WINGMAN.md section 3b. These documents define what replaced the brief-based stop decisions.

What did the blind read phase of the review do?▼

The blind read spawned a subagent that saw only the brief fields in the pane's shape, never the TurnPackage evidence. It answered whether the card was decidable, what was missing, what jargon was unexplained, and what was noise.

Related Skills

Explore More Software Engineering Skills→
SJTU-IPADSSJTU-IPADS
7

todo

Convert vague intentions into structured tasks with local storage.

Official
Intermediate
cabeznocabezno

github-issues

Manage GitHub issues via gh or the REST API.

Community
Intermediate
Rycen7822Rycen7822
2

decision

Record quest decisions with verdicts, reasons, and next steps.

Community
Advanced
ShawhinTShawhinT
40

conversion-copy

Produces and reviews channel-specific marketing copy with customer-language grounding.

Community
Advanced