auctra-novel-review-orchestrator

Orchestrates Auctra novel review queues, defect triage, and reviewer dispatch.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/yeisme/auctra-novel-skills --skill auctra-novel-review-orchestrator-yeisme
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auctra-novel-review-orchestrator
Source: https://github.com/yeisme/auctra-novel-skills/tree/main/auctra-runtime/auctra-novel-review-orchestrator
Command: npx skills add https://github.com/yeisme/auctra-novel-skills --skill auctra-novel-review-orchestrator-yeisme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing Chinese novel chapter candidates inside an Auctra project involves scattered context: pending review queues, chapter cards, reader contracts, continuity constraints, and multiple specialized reviewer skills. This Skill turns that chaos into a traceable workflow that inspects the review queue, dispatches the right reviewer skills, and produces a defect register with an accept, reject, or partial decision recommendation. ## Core Features & Use Cases - Review Queue Inspection: Reads Auctra CLI output such as auctra review list --status pending --json and chapter context or handoff JSON to establish a review baseline. - Reviewer Dispatch: Routes work to specialized skills like draft comparison, chapter review, continuity editing, hook and pacing analysis, and state ledger updates based on the task. - Defect Register & Decision Handoff: Produces a severity-ranked defect register with evidence, minimal fixes, owner skills, and a recommended Auctra review action (accept, reject, or partial). - Use Case: You have a pending candidate chapter in an Auctra project and want to know whether it fulfills the chapter card, where it regresses versus the accepted version, and whether to accept it. The Skill checks context completeness, dispatches reviewers, and returns a structured verdict with next commands. ## Quick Start Ask the agent to inspect the pending Auctra novel review items in your project, compare the candidate chapter against its chapter card and reader contract, and output a defect matrix with a review decision recommendation.

Frequently Asked Questions about auctra-novel-review-orchestrator

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

FAQPage Schema
How do I review a pending novel chapter candidate in an Auctra project?▼

Run auctra review list --status pending --json to find the review item, then gather chapter context and handoff JSON. The Skill builds a baseline from the chapter card, reader contract, and accepted version, dispatches reviewer skills, and returns a defect register with an accept, reject, or partial recommendation.

How does the review orchestrator decide accept, reject, or partial?▼

Accept requires no blocking defects and passing key dimensions. Partial applies when usable passages exist but need manual diff or local replacement. Reject applies when chapter goals are missing, continuity conflicts exist, characters violate their settings, or the genre contract is broken.

Which reviewer skills does the Auctra review workflow dispatch?▼

It dispatches skills for draft comparison, chapter review, continuity editing, hook and pacing analysis, reader retention, dialogue editing, style polishing, revision production, and state ledger updates. The choice depends on whether the task involves comparison, single-chapter gates, timeline facts, or retention concerns.

Can the review orchestrator modify chapter text or write Auctra state directly?▼

No. It never edits the manuscript, never auto-accepts candidates, and never writes .auctra files, SQLite rows, or review decisions by hand. It only suggests real Auctra commands and produces reports as ordinary material for human confirmation.

What happens when review context or command output is missing?▼

The Skill lowers its confidence rating and lists the missing materials plus the exact Auctra commands needed to fill the gaps. It can dispatch a context pack builder to enumerate minimal missing inputs before any verdict is given.