mst:feedback-composer

Synthesize review reports into prioritized feedback documents with root cause classifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating precise, actionable feedback documents from review reports, enabling external agents to fix issues efficiently in a single iteration.

Core Features & Use Cases

  • Synthesizes Review Data: Consolidates feedback from multiple reviewers into a single, coherent document.
  • Actionable Instructions: Formats feedback with file:line references, clear problem descriptions, and specific fix instructions.
  • Root Cause Classification: Identifies whether issues stem from implementation errors or insufficient specifications.
  • Prioritization: Organizes issues by criticality (CRITICAL, HIGH, MEDIUM, LOW).
  • Use Case: After code reviews, use this Skill to generate a consolidated feedback report for an outsourced development team, ensuring they have all the necessary details to address bugs and spec discrepancies accurately.

Quick Start

Use the feedback composer skill to generate a feedback document for task REQ-001-01, round 1, using the provided spec content, review reports, and no previous feedback.

Frequently Asked Questions about mst:feedback-composer

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

FAQPage Schema
How do I generate actionable feedback for external agents from code review reports?

To generate actionable feedback for external agents, synthesize multiple review reports into a single document using file:line references, clear problem descriptions, and specific fix instructions. This consolidates feedback for efficient single-iteration bug fixing.

What is the best way to consolidate code review feedback for an outsourced development team?

The best way to consolidate code review feedback is to classify root causes and prioritize issues by criticality (CRITICAL, HIGH, MEDIUM, LOW). This routes feedback based on whether issues require implementation fixes or spec revisions for the external team.

How does root cause classification work for code review feedback?

Root cause classification for code review feedback identifies whether issues stem from implementation errors or insufficient specifications. This routes feedback appropriately, directing implementation errors for bug fixing and spec discrepancies for spec revision.

Can I carry forward unresolved issues during iterative code review feedback generation?

Yes, you can carry forward unresolved issues during iterative code review feedback generation. The process supports iterative development by incorporating previous feedback documents alongside current spec content and review reports to track persistent bugs.

How do I format feedback documents for bug fixing to ensure single-iteration resolution?

Format feedback documents for bug fixing by including file:line references, clear problem descriptions, and specific fix instructions. Prioritizing issues by criticality ensures external agents resolve bugs accurately within a single iteration.

What limitations exist when synthesizing multiple code review reports into feedback?

A limitation when synthesizing multiple code review reports is the dependency on provided spec content and previous feedback data. Without accurate review results and spec content, generating precise, actionable feedback documents for external agents is constrained.