reflect

Classify post-release observations into categorized product-context.yaml updates.

14|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/memorysaver/agentic-engineering-patterns --skill reflect-memorysaver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/memorysaver/agentic-engineering-patterns/tree/main/skills/product-context/reflect
Command: npx skills add https://github.com/memorysaver/agentic-engineering-patterns --skill reflect-memorysaver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams close the feedback loop by classifying real-world observations (user testing, error logs, cost data) and routing them into actionable changes in the product-context.yaml. It supports both split mode (using product/index.yaml for product intent) and v1 mode (operational state in product-context.yaml).

Core Features & Use Cases

  • Classify observations into defined categories (Bug, Refinement, Discovery, Opportunity Shift, Process) and assign appropriate layers.
  • Update product-context.yaml with new stories, cost data, and changelog entries; in split mode also update product/index.yaml as needed.
  • Generate actionable outputs for the next steps (dispatch, envision, map, calibrate) and guide iterative roadmap adjustments.
  • Re-slice the map when feedback shifts priorities, updating layer assignments and dependencies accordingly.
  • Summarize lessons learned and capture process improvements for future workflows.

Quick Start

Classify the latest feedback observations into actionable product-context updates and apply them to the appropriate layer and changelog.

Frequently Asked Questions about reflect

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

FAQPage Schema
How do I classify post-release feedback into actionable product roadmap updates?▼

Classify post-release feedback by routing observations from user testing, error monitoring, and cost data into defined categories like Bug, Refinement, or Discovery, then apply them as structured updates to your product-context.yaml.

What is the best way to close the feedback loop and update product context after a release?▼

Closing the feedback loop involves classifying real-world observations, updating product-context.yaml with new stories and changelog entries, and generating actionable outputs like dispatch or calibrate to guide iterative roadmap adjustments.

Can I use split mode and v1 mode workflows together for product context classification?▼

Yes, split mode and v1 mode workflows can be used together. Split mode uses product/index.yaml for product intent, while v1 mode manages operational state in product-context.yaml, allowing you to handle both strategic and operational feedback layers.

How do I re-slice a product roadmap map when feedback shifts priorities?▼

To re-slice a product roadmap map when feedback shifts priorities, update layer assignments and dependencies in your product context files, capturing the decision rationale and next steps in the changelog to reflect the new priorities.

When should I create new stories versus updating existing layers with user testing feedback?▼

Create new stories when feedback reveals novel opportunities or discovery insights, and update existing layers when observations classify as Bugs or Refinements, ensuring all changes are recorded in the changelog with associated cost data and next steps.