feedback-pro

Generate evidence-based feedback reports with severity ratings and closure plans.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/truongnat/skills --skill feedback-pro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feedback-pro
Source: https://github.com/truongnat/skills/tree/main/skills/feedback-pro
Command: npx skills add https://github.com/truongnat/skills --skill feedback-pro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides structured, evidence-based feedback on code, docs, and design, enabling teams to move from vague comments to prioritized, actionable improvements with clear closure criteria.

Core Features & Use Cases

  • Convert ambiguous feedback into concrete, traceable findings with observed behavior, impact, and remediation steps.
  • Calibrate severity and create owner-ready action plans to close gaps efficiently.
  • Produce executive-friendly summaries plus implementer-level detail for follow-up and verification.

Quick Start

Ask for a deep, evidence-backed feedback report on the provided artifact with explicit closure criteria.

Frequently Asked Questions about feedback-pro

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

FAQPage Schema
How do I write actionable feedback for code review?

Actionable feedback converts ambiguous comments into traceable findings with observed behavior, impact, and remediation steps. It requires evidence-backed findings, severity calibration, and an explicit closure plan to prioritize must-fix versus nice-to-have items efficiently.

What is the best way to structure design critique findings?

Structured design critique findings separate executive-friendly summaries from implementer-level detail. This structure includes clear owner hints, severity calibration, and explicit verification steps, ensuring teams move from vague comments to prioritized improvements with clear closure criteria.

How do I calibrate severity and create owner-ready action plans for documentation gaps?

Calibrating severity for documentation gaps involves evidence-backed findings to distinguish must-fix issues from nice-to-haves. It produces owner-ready action plans with explicit closure criteria and verification steps to close quality gaps efficiently.

Can I use evidence-based feedback for quality assessments across engineering and product domains?

Evidence-based feedback applies directly to quality assessments across engineering, product, and documentation domains. It provides structured, evidence-backed findings with clear actions and closure, ensuring reviews and critiques yield prioritized, actionable improvements.

Does structured feedback generation require explicit closure criteria?

Structured feedback requires explicit closure criteria to ensure actionable outcomes. Outputs must include must-fix versus nice-to-have categorization, owner hints, and verification steps, enabling teams to move from vague comments to prioritized improvements efficiently.