with one click
maestro-grill
// Use when stress-testing a plan, idea, or requirement against codebase reality before brainstorming
// Use when stress-testing a plan, idea, or requirement against codebase reality before brainstorming
| name | maestro-grill |
| description | Use when stress-testing a plan, idea, or requirement against codebase reality before brainstorming |
| argument-hint | <topic|plan> [-y] [-c] [--from <source>] [--depth shallow|standard|deep] |
| allowed-tools | ["ask_question","define_subagent","grep_search","invoke_subagent","manage_subagents","replace_file_content","run_command","send_message","view_file","write_to_file"] |
Positioned BEFORE brainstorm in the pipeline: grill stress-tests and sharpens; brainstorm generates and elaborates.
<required_reading> @~/.maestro/workflows/grill.md </required_reading>
<deferred_reading>
Mode selection:
-y): Code exploration answers questions instead of the user-c or --session ID): Continue from a previous grill sessionFlags:
| Flag | Effect | Default |
|---|---|---|
-y / --yes | Auto mode — CLI exploration replaces human answers | false |
-c / --continue | Resume from last grill session | — |
--session ID | Resume specific session | — |
--depth shallow|standard|deep | Branch count 3/5/8 | standard |
--from <source> | Load upstream material (blueprint:ID, @file, or path) | — |
Output directory: .workflow/scratch/{YYYYMMDD}-grill-{slug}/
Produced files: grill-report.md, terminology.md, context-package.json
maestro spec load --category arch — load architecture constraintsmaestro wiki search "{topic keywords}" → load relevant entries before grilling<interview_protocol> Follows @~/.maestro/workflows/interview-mechanics.md standard.
Interaction mode override: adversarial Socratic — NOT menu-driven Question style:
{symbol} at {file:line} — your proposal calls it {term}. Which wins?"=== GRILL READY ===
Topic: {topic}
Branches walked: {count}/{depth_target}
Decisions locked: {locked_count}
Open risks: {risk_count}
Output: {output_dir}
Artifact: GRL-{id}
=== END GRILL ===
End the step by calling the CLI (no text block output):
maestro ralph complete <idx> --status {STATUS} [--evidence {path}]
Status verdicts:
--concerns--reason| Condition | Suggestion |
|---|---|
| Need multi-role elaboration | view_file(AbsolutePath="<agy-skills-dir>/maestro-brainstorm/SKILL.md") + execute inline (args: "{topic} --from grill:{artifact_id}") |
| Need deep technical analysis | view_file(AbsolutePath="<agy-skills-dir>/maestro-analyze/SKILL.md") + execute inline (args: "{topic} --from grill:{artifact_id}") |
| Scope is clear, ready for roadmap | view_file(AbsolutePath="<agy-skills-dir>/maestro-roadmap/SKILL.md") + execute inline (args: "--from grill:{artifact_id}") |
| Need formal spec package | view_file(AbsolutePath="<agy-skills-dir>/maestro-blueprint/SKILL.md") + execute inline (args: "--from grill:{artifact_id}") |
| More branches to walk | view_file(AbsolutePath="<agy-skills-dir>/maestro-grill/SKILL.md") + execute inline (args: "{topic} -c") |
<error_codes>
| Code | Severity | Condition | Recovery |
|---|---|---|---|
| E001 | error | No topic/plan and no --from/--continue flag | Prompt user for topic text |
| E002 | error | --session ID not found | Show available sessions |
| W001 | warning | Codebase scan failed or returned empty | Continue without code grounding, note limitation |
| W002 | warning | CLI exploration timeout in auto mode | Skip question, mark as open |
| W003 | warning | Max branch depth reached without resolution | Force synthesis, offer continuation |
| </error_codes> |
<success_criteria>
grill-report.md written with Branch Log table, all Q&A entries, synthesis sectionterminology.md written with >= 5 terms, code references where applicablecontext-package.json generated with schema "context-package/1.0"<on_complete> @~/.maestro/workflows/finish-work.md — SESSION_DIR={output_dir}, SESSION_TYPE=grill, SESSION_ID={artifact_id}, LINKED_MILESTONE=null </on_complete>
Use when a topic needs structured multi-dimensional investigation before planning or decision-making
Generate formal specification package (Product Brief, PRD, Architecture, Epics) through 6-phase document chain
Use when exploring ideas, evaluating approaches, or needing multi-perspective analysis before implementation
Use when a confirmed plan is ready for implementation
Initialize project with auto state detection
Audit current milestone for cross-phase integration gaps