feat: add retrospective intelligence to create-story workflow

Load all retrospective files during story creation to carry forward
lessons learned, open action items, architecture corrections, and
deferred code review items. Fulfills Epic 2 retro action item A1.

Also includes Epic 2 retrospective and sprint status updates.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-03-24 10:56:14 +01:00
parent 716e9fc4f6
commit ff92311994
7 changed files with 286 additions and 4 deletions

View File

@@ -181,7 +181,22 @@
<invoke-protocol
name="discover_inputs" />
<note>Available content: {epics_content}, {prd_content}, {architecture_content}, {ux_content},
{project_context}</note>
{project_context}, {retrospective_content}</note>
<!-- Load retrospective lessons — Team Agreement: non-negotiable (Epic 2 Retro) -->
<critical>🔄 RETROSPECTIVE INTELLIGENCE — Load lessons learned from previous epics to prevent repeated mistakes!</critical>
<check if="retrospective files found in {retrospective_content}">
<action>From {retrospective_content}, extract and prioritize for current story:</action>
**RETROSPECTIVE INTELLIGENCE:**
- Action items still open or relevant to this epic
- Architecture corrections and doc drift identified
- Code patterns that worked well (to replicate)
- Problems encountered and solutions found (to avoid repeating)
- Team agreements and conventions established
- Deferred code review items that may affect this story
<action>Flag any action item that directly impacts this story's implementation</action>
<action>Include relevant retrospective lessons in the story's Dev Notes section</action>
</check>
<!-- Analyze epics file for story foundation -->
<action>From {epics_content}, extract Epic {{epic_num}} complete context:</action> **EPIC ANALYSIS:** - Epic
@@ -279,6 +294,11 @@
file_structure_requirements</template-output>
<template-output file="{default_output_file}">testing_requirements</template-output>
<!-- Retrospective intelligence -->
<check if="retrospective lessons available">
<template-output file="{default_output_file}">retrospective_intelligence</template-output>
</check>
<!-- Previous story intelligence -->
<check
if="previous story learnings available">

View File

@@ -21,6 +21,13 @@ so that {{benefit}}.
- [ ] Task 2 (AC: #)
- [ ] Subtask 2.1
## Retrospective Intelligence
- Applicable lessons from previous epics
- Open action items affecting this story
- Architecture corrections to incorporate
- Deferred code review items relevant here
## Dev Notes
- Relevant architecture patterns and constraints

View File

@@ -50,3 +50,7 @@ input_file_patterns:
whole: "{planning_artifacts}/*epic*.md"
sharded: "{planning_artifacts}/*epic*/*.md"
load_strategy: "SELECTIVE_LOAD" # Only load needed epic
retrospective:
description: "Latest retrospective for lessons learned, action items, and architecture corrections"
whole: "{implementation_artifacts}/*retro*.md"
load_strategy: "FULL_LOAD" # Load all retros — context window can handle it