feedback

Submit structured Phase 4 feedback with failure categories and evidence.

24|5|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/myrtlepn/gran-maestro --skill feedback-myrtlepn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feedback
Source: https://github.com/myrtlepn/gran-maestro/tree/main/skills/feedback
Command: npx skills add https://github.com/myrtlepn/gran-maestro --skill feedback-myrtlepn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows users to provide structured, manual feedback on AI-generated output within the Gran Maestro workflow, specifically addressing issues in Phase 4 (feedback loop) to ensure continuous improvement and accurate implementation.

Core Features & Use Cases

  • Structured Feedback Submission: Enables users to categorize failures (ac_unclear, interpretation, implementation) and provide specific evidence (logs, screenshots, metrics).
  • Targeted Rework Instructions: Facilitates clear instructions for rework without dictating implementation details, focusing on restoring specific ACs or criteria.
  • Use Case: After an AI attempts to implement a feature, if the output doesn't match the specification due to a misunderstanding of the requirements, you can use this Skill to flag it as an interpretation failure, provide the relevant AC ID and a screenshot of the incorrect output, and request a re-evaluation based on the correct interpretation.

Quick Start

Submit feedback for request PLN-001, indicating an implementation error with evidence from log file /path/to/log.txt.

Frequently Asked Questions about feedback

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

FAQPage Schema
How do I submit manual feedback on AI-generated output that failed to meet acceptance criteria?▼

To submit manual feedback on AI-generated output, categorize the failure as `ac_unclear`, `interpretation`, or `implementation`, then provide specific evidence like logs or screenshots linked to the relevant AC ID and specify rework instructions.

What are the failure categories for AI quality assurance refinement in a workflow?▼

AI quality assurance refinement categorizes failures into three types: `ac_unclear` for ambiguous acceptance criteria, `interpretation` for misunderstood requirements, and `implementation` for execution errors, enabling automated routing to the correct rework protocol.

Can I route implementation errors to external services like codex or gemini for re-execution?▼

Yes, implementation errors support automated routing to external services like `/mst:codex` or `/mst:gemini` for re-executing tasks, ensuring that execution failures are automatically addressed through the appropriate external rework protocols.

What is the best way to provide targeted rework instructions without dictating implementation details?▼

The best way to provide targeted rework instructions is to focus on restoring specific acceptance criteria by linking evidence to AC IDs, guiding the AI to re-evaluate based on correct interpretations rather than explicitly dictating the underlying implementation details.

Are there limits on feedback rounds for AI output refinement?▼

Yes, the feedback mechanism manages feedback round limits to ensure continuous improvement. It restricts the number of rework iterations within the workflow, preventing endless loops during the AI output refinement process.