Review To Revisions Pipeline
review_to_revisions_pipeline
Start with BeatBandit-led diagnosis first, then route the resulting review findings into the right revision path.
When to use
Use when the caller wants BeatBandit to identify what should change before choosing a revision tool.
Use when the workflow should begin with room review, analysis, or continuity checks and then continue into revisions.
When not to use
Do not use when the caller already has a concrete revision request and does not want review first; use `revision_strategy_pipeline` instead.
Do not use for pure generation or media workflows.
Examples
“Review this draft and then tell me the best revision path.”
“Diagnose what is broken first, then route me into the right BeatBandit fix flow.”
Anti-examples
- Apply this known screenplay change directly.
Related tools
Prompts are orchestration guidance only. They route into these public tools instead of replacing them.
Live-state resources
Prompt resolution may inspect these resources or their backing backend reads before steering the client.
Arguments schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"required": [
"project_id"
],
"properties": {
"project_id": {
"type": "string",
"pattern": "^[0-9]+quot;
},
"review_goal": {
"type": "string"
},
"focus_areas": {
"type": "string",
"description": "Comma-separated list of review focus areas."
}
},
"additionalProperties": false
}