recipe-reflect
Skill7 starsChanged 3 months agoMITView on GitHub
Orchestrates reflection by updating affected artifacts and distilling reusable knowledge from validation results.
In this repository15 other files it gives its agents.
- blueprint-standardsSkill
- business-contextSkill
- design-perspectiveSkill
- hypothesis-disciplineSkill
- prd-standardsSkill
- product-principlesSkill
- prototype-guideSkill
- recipe-blueprintSkill
- recipe-defineSkill
- recipe-discoverSkill
- recipe-personaSkill
- recipe-prototype-promptSkill
- recipe-refine-visualsSkill
- recipe-validateSkill
- recipe-visionSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Verify the hypothesis file has been updated with results (validation results, confidence scores, evidence)
- Distinctive: line 36
Document a learning when the result changes the parent Opportunity or a later decision
- Distinctive: line 37
Check if this result changes understanding of the parent Opportunity
- Distinctive: line 40
Start from the Opportunity and load the hypothesis evidence needed to assess candidate learnings and contradictions
- Distinctive: line 68
Write learnings to the Opportunity file's "Tier 2 Learnings" section
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Context: Drive the feedback loop by reflecting on outcomes, updating target artifacts, and distilling learnings across the knowledge pyramid (see product-principles skill for Tier definitions).
Required Skills [LOAD BEFORE EXECUTION]
- [LOAD IF NOT ACTIVE]
product-principles— Knowledge Pyramid and promotion criteria - [LOAD IF NOT ACTIVE]
hypothesis-discipline— validation results, lifecycle status, and confidence changes
Delegate Level 2 and Level 3 distillation to knowledge-distiller for independent evidence synthesis.
Execution Decision Flow
1. Scope Assessment
Input: Use the path or text supplied with the explicit skill invocation. If no input was supplied and the target cannot be inferred unambiguously, ask for it.
Determine the reflection level (see references/reflection-guide.md):
| Trigger | Level | Target Files |
| Hypothesis concluded | Level 1: Hypothesis | The hypothesis file |
| Multiple hypotheses concluded under an Opportunity | Level 2: Opportunity | Opportunity file (Tier 2 Learnings section) |
| PRD delivered, quarterly review, strategic pivot | Level 3: Vision | docs/product/vision.md, docs/product/learnings.md |
2. Result Recording
Level 1: Hypothesis Reflection
- Verify the hypothesis file has been updated with results (validation results, confidence scores, evidence)
- Document a learning when the result changes the parent Opportunity or a later decision
- Check if this result changes understanding of the parent Opportunity
Level 2: Opportunity Reflection
- Start from the Opportunity and load the hypothesis evidence needed to assess candidate learnings and contradictions
- Prepare context for knowledge-distiller (hypothesis summaries, results, confidence changes)
Level 3: Vision Reflection
- Gather the cross-Opportunity evidence needed for the outcome, NSM, or Tier 1 decision
- Review Product Outcomes — are targets still correct?
- Review NSM — still the right connecting metric?
- Prepare context for knowledge-distiller
3. Knowledge Distillation
Invoke knowledge-distiller for evidence distillation:
- knowledge-distiller operates in a separate context to avoid individual hypothesis bias
- It distills evidence into candidate learnings and contradictions
- It proposes Tier 2 learnings (for Opportunity) or Tier 1 learnings (for Vision)
- It enforces distillation quality criteria (per product-principles skill)
Present distillation results to the user for the knowledge-promotion decision:
- Candidate learnings with proposed tiers, supporting evidence, and contexts
- Contradictions found and the decisions they may affect
End the current turn with the distillation result as the workflow output. Promote knowledge only after the user confirms the proposal in a later turn.
4. Knowledge Promotion
After that confirmation:
Tier 3 → Tier 2
- Write learnings to the Opportunity file's "Tier 2 Learnings" section
- Include hypothesis references that support each learning
Tier 2 → Tier 1
- Write to
docs/product/learnings.md - Include supporting evidence references and their dates
- State the contexts where the learning applies
Sub-agent Usage
| Agent | When | Why (context separation benefit) |
| knowledge-distiller | Level 2 and Level 3 reflection | Independent evidence synthesis across hypotheses |
Scope Boundaries
Included: Result recording, knowledge distillation, and Tier promotion Not included: Hypothesis validation (→ recipe-validate), new hypothesis generation (→ recipe-discover)
Completion
The workflow is complete when approved promotions are updated, or a no-change result is reported with the evidence and contradictions relevant to the decision.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

