aep-reflect

Classify user feedback and update product context YAML files post-shipment.

Updated May 18, 2026
One-click install
npx skills add https://github.com/memorysaver/project-understanding --skill aep-reflect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aep-reflect
Source: https://github.com/memorysaver/project-understanding/tree/main/.agents/skills/aep-reflect
Command: npx skills add https://github.com/memorysaver/project-understanding --skill aep-reflect

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps product teams classify feedback and update the product context after shipping features, ensuring that real-world observations lead to actionable changes.

Core Features & Use Cases

  • Feedback Classification: Classify feedback into bugs, refinements, discoveries, opportunity shifts, and process observations.
  • Product Context Update: Update product-context.yaml and product/index.yaml based on classified feedback.
  • Cost Review: Review the cost section of product-context.yaml for optimization opportunities.
  • Workflow Improvement: Document and propose improvements to the workflow based on process observations.

Quick Start

Run the aep-reflect skill to gather feedback, classify it, and update the product context.

Frequently Asked Questions about aep-reflect

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

FAQPage Schema
How do I close the feedback loop after shipping a product feature?

To close the feedback loop after shipping, classify user feedback into categories like bugs and refinements, then update your product context files to reflect actionable changes based on those observations.

How do I classify user feedback for product improvement?

Classify user feedback for product improvement by categorizing observations into bugs, feature refinements, discoveries, opportunity shifts, and process observations to ensure real-world data drives updates.

What is the best way to update product context based on post-shipment observations?

The best way to update product context based on post-shipment observations is to classify the feedback and apply those structured insights directly into your product context and index files.

How do I review product costs for optimization opportunities from user feedback?

Review product costs for optimization opportunities by analyzing the cost section within your product context file, identifying areas where classified process observations or bug fixes can reduce overhead.

What do I need to classify feedback and update product context?

To classify feedback and update product context, you need a structured feedback input detailing post-shipment observations and an existing product context file to apply the classified changes.

Can I document workflow improvements based on process observations?

Yes, you can document workflow improvements by categorizing process observations from user feedback and proposing actionable updates to your development workflow based on those classified insights.