feedback

Generates scored retrospective reports from completed agent work sessions, optionally creating GitHub tracking issues.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/nexus-a1/claude-skills --skill feedback-nexus-a1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feedback
Source: https://github.com/nexus-a1/claude-skills/tree/main/skills/feedback
Command: npx skills add https://github.com/nexus-a1/claude-skills --skill feedback-nexus-a1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool generates a retrospective report analyzing agent pipeline execution, duplication, scope adherence, and output quality from a completed work session.

Core Features & Use Cases

  • Generate scored retrospective reports of a finished workflow, identifying pipeline gaps, duplication, and scope adherence.
  • Produce a structured report saved to the project's artifact storage and optionally create a GitHub issue for tracking improvements.
  • Use across multiple work sessions (brainstorm, create-requirements, implement, epic) to standardize post-mortem QA.

Quick Start

Run /feedback to auto-detect the most recent work session and generate a comprehensive retrospective report.

Frequently Asked Questions about feedback

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

FAQPage Schema
How do I automate post-session retrospective analysis for agent workflows?▼

Automate post-session retrospectives by running /feedback to extract artifacts and outputs from completed agent work sessions, generating a structured report analyzing pipeline execution, duplication, and scope adherence.

What is a QA retrospective report for agent pipeline execution?▼

A QA retrospective report is a structured analysis of a finished agent workflow that identifies pipeline gaps, duplication, scope adherence, and output quality, saving the results to project artifact storage.

Can I create a GitHub issue automatically from a post-mortem report?▼

Yes, you can optionally create a GitHub issue directly from the generated retrospective report to track identified pipeline gaps and output quality improvements for future sessions.

Does the retrospective analysis work across different agent work phases?▼

Yes, the retrospective analysis applies to multiple work phases including brainstorm, create-requirements, implement, and epic, standardizing post-mortem QA across diverse agent work sessions.

What is the best way to identify workflow duplication and scope adherence in completed tasks?▼

The best way to identify duplication and scope adherence is to run /feedback on the most recent work session, which auto-detects session artifacts and produces a scored retrospective analysis report.

Do I need any external dependencies to generate post-session feedback reports?▼

No external dependencies are required to generate post-session feedback reports; the tool loads its operational instructions from Markdown body and YAML frontmatter to analyze session artifacts independently.