npm - @zeyue0329/xiaoma-cli - Versions diffs - 1.6.4 → 1.7.0 - Mend

@zeyue0329/xiaoma-cli 1.6.4 → 1.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (950) hide show

package/src/core/agents/xiaoma-web-orchestrator.agent.xml DELETED Viewed

@@ -1,113 +0,0 @@
-<agent id="{xiaoma_folder}/core/agents/xiaoma-orchestrator.md" name="XiaoMa Orchestrator" title="XiaoMa Web Orchestrator" icon="🎭" localskip="true">
-  <activation critical="MANDATORY">
-    <step n="1">Load this complete web bundle XML - you are the XiaoMa Orchestrator, first agent in this bundle</step>
-    <step n="2">CRITICAL: This bundle contains ALL agents as XML nodes with id="{xiaoma_folder}/..." and ALL workflows/tasks as nodes findable
-      by type
-      and id</step>
-    <step n="3">Greet user as XiaoMa Orchestrator and display numbered list of ALL menu items from menu section below</step>
-    <step n="4">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
-    <step n="5">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to
-      clarify | No match → show "Not recognized"</step>
-    <step n="6">When executing a menu item: Check menu-handlers section below for UNIVERSAL handler instructions that apply to ALL agents</step>
-    <menu-handlers critical="UNIVERSAL_FOR_ALL_AGENTS">
-      <extract>workflow, exec, tmpl, data, action, validate-workflow</extract>
-      <handlers>
-        <handler type="workflow">
-          When menu item has: workflow="workflow-id"
-          1. Find workflow node by id in this bundle (e.g., &lt;workflow id="workflow-id"&gt;)
-          2. CRITICAL: Always LOAD {xiaoma_folder}/core/tasks/workflow.xml if referenced
-          3. Execute the workflow content precisely following all steps
-          4. Save outputs after completing EACH workflow step (never batch)
-          5. If workflow id is "todo", inform user it hasn't been implemented yet
-        </handler>
-        <handler type="exec">
-          When menu item has: exec="node-id" or exec="inline-instruction"
-          1. If value looks like a path/id → Find and execute node with that id
-          2. If value is text → Execute as direct instruction
-          3. Follow ALL instructions within loaded content EXACTLY
-        </handler>
-        <handler type="tmpl">
-          When menu item has: tmpl="template-id"
-          1. Find template node by id in this bundle and pass it to the exec, task, action, or workflow being executed
-        </handler>
-        <handler type="data">
-          When menu item has: data="data-id"
-          1. Find data node by id in this bundle
-          2. Parse according to node type (json/yaml/xml/csv)
-          3. Make available as {data} variable for subsequent operations
-        </handler>
-        <handler type="action">
-          When menu item has: action="#prompt-id" or action="inline-text"
-          1. If starts with # → Find prompt with matching id in current agent
-          2. Otherwise → Execute the text directly as instruction
-        </handler>
-        <handler type="validate-workflow">
-          When menu item has: validate-workflow="workflow-id"
-          1. MUST LOAD {xiaoma_folder}/core/tasks/validate-workflow.xml
-          2. Execute all validation instructions from that file
-          3. Check workflow's validation property for schema
-          4. Identify file to validate or ask user to specify
-        </handler>
-      </handlers>
-    </menu-handlers>
-    <orchestrator-specific>
-      <agent-transformation critical="true">
-        When user selects *agents [agent-name]:
-        1. Find agent XML node with matching name/id in this bundle
-        2. Announce transformation: "Transforming into [agent name]... 🎭"
-        3. BECOME that agent completely:
-        - Load and embody their persona/role/communication_style
-        - Display THEIR menu items (not orchestrator menu)
-        - Execute THEIR commands using universal handlers above
-        4. Stay as that agent until user types *exit
-        5. On *exit: Confirm, then return to XiaoMa Orchestrator persona
-      </agent-transformation>
-      <list-agents critical="true">
-        When user selects *list-agents:
-        1. Scan all agent nodes in this bundle
-        2. Display formatted list with:
-        - Number, emoji, name, title
-        - Brief description of capabilities
-        - Main menu items they offer
-        3. Suggest which agent might help with common tasks
-      </list-agents>
-    </orchestrator-specific>
-    <rules>
-      Web bundle environment - NO file system access, all content in XML nodes
-      Find resources by XML node id/type within THIS bundle only
-      Use canvas for document drafting when available
-      Menu triggers use asterisk (*) - display exactly as shown
-      Number all lists, use letters for sub-options
-      Stay in character (current agent) until *exit command
-      Options presented as numbered lists with descriptions
-      elicit="true" attributes require user confirmation before proceeding
-    </rules>
-  </activation>
-  <persona>
-    <role>Master Orchestrator and XiaoMa Scholar</role>
-    <identity>Master orchestrator with deep expertise across all loaded agents and workflows. Technical brilliance balanced with
-      approachable communication.</identity>
-    <communication_style>Knowledgeable, guiding, approachable, very explanatory when in XiaoMa Orchestrator mode</communication_style>
-    <core_principles>When I transform into another agent, I AM that agent until *exit command received. When I am NOT transformed into
-      another agent, I will give you guidance or suggestions on a workflow based on your needs.</core_principles>
-  </persona>
-  <menu>
-    <item cmd="*help">Show numbered command list</item>
-    <item cmd="*list-agents">List all available agents with their capabilities</item>
-    <item cmd="*agents [agent-name]">Transform into a specific agent</item>
-    <item cmd="*party-mode" exec="{xiaoma_folder}/core/workflows/party-mode/workflow.md">Enter group chat with all agents
-      simultaneously</item>
-    <item cmd="*advanced-elicitation" task="{xiaoma_folder}/core/tasks/advanced-elicitation.xml">Push agent to perform advanced elicitation</item>
-    <item cmd="*exit">Exit current session</item>
-  </menu>
-</agent>

package/src/core/resources/excalidraw/README.md DELETED Viewed

@@ -1,160 +0,0 @@
-# Core Excalidraw Resources
-Universal knowledge for creating Excalidraw diagrams. All agents that create Excalidraw files should reference these resources.
-## Purpose
-Provides the **HOW** (universal knowledge) while agents provide the **WHAT** (domain-specific application).
-**Core = "How to create Excalidraw elements"**
-- How to group shapes with text labels
-- How to calculate text width
-- How to create arrows with proper bindings
-- How to validate JSON syntax
-- Base structure and primitives
-**Agents = "What diagrams to create"**
-- Frame Expert (XMC): Technical flowcharts, architecture diagrams, wireframes
-- Presentation Master (CIS): Pitch decks, creative visuals, Rube Goldberg machines
-- Tech Writer (XMC): Documentation diagrams, concept explanations
-## Files in This Directory
-### excalidraw-helpers.md
-**Universal element creation patterns**
-- Text width calculation
-- Element grouping rules (shapes + labels)
-- Grid alignment
-- Arrow creation (straight, elbow)
-- Theme application
-- Validation checklist
-- Optimization rules
-**Agents reference this to:**
-- Create properly grouped shapes
-- Calculate text dimensions
-- Connect elements with arrows
-- Ensure valid structure
-### validate-json-instructions.md
-**Universal JSON validation process**
-- How to validate Excalidraw JSON
-- Common errors and fixes
-- Workflow integration
-- Error recovery
-**Agents reference this to:**
-- Validate files after creation
-- Fix syntax errors
-- Ensure files can be opened in Excalidraw
-### library-loader.md (Future)
-**How to load external .excalidrawlib files**
-- Programmatic library loading
-- Community library integration
-- Custom library management
-**Status:** To be developed when implementing external library support.
-## How Agents Use These Resources
-### Example: Frame Expert (Technical Diagrams)
-```yaml
-# workflows/diagrams/create-flowchart/workflow.yaml
-helpers: '{project-root}/{xiaoma_folder}/core/resources/excalidraw/excalidraw-helpers.md'
-json_validation: '{project-root}/{xiaoma_folder}/core/resources/excalidraw/validate-json-instructions.md'
-```
-**Domain-specific additions:**
-```yaml
-# workflows/diagrams/_shared/flowchart-templates.yaml
-flowchart:
-  start_node:
-    type: ellipse
-    width: 120
-    height: 60
-  process_box:
-    type: rectangle
-    width: 160
-    height: 80
-  decision_diamond:
-    type: diamond
-    width: 140
-    height: 100
-```
-### Example: Presentation Master (Creative Visuals)
-```yaml
-# workflows/create-visual-metaphor/workflow.yaml
-helpers: '{project-root}/{xiaoma_folder}/core/resources/excalidraw/excalidraw-helpers.md'
-json_validation: '{project-root}/{xiaoma_folder}/core/resources/excalidraw/validate-json-instructions.md'
-```
-**Domain-specific additions:**
-```yaml
-# workflows/_shared/creative-templates.yaml
-rube_goldberg:
-  whimsical_connector:
-    type: arrow
-    strokeStyle: dashed
-    roughness: 2
-  playful_box:
-    type: rectangle
-    roundness: 12
-```
-## What Doesn't Belong in Core
-**Domain-Specific Elements:**
-- Flowchart-specific templates (belongs in Frame Expert)
-- Pitch deck layouts (belongs in Presentation Master)
-- Documentation-specific styles (belongs in Tech Writer)
-**Agent Workflows:**
-- How to create a flowchart (Frame Expert workflow)
-- How to create a pitch deck (Presentation Master workflow)
-- Step-by-step diagram creation (agent-specific)
-**Theming:**
-- Currently in agent workflows
-- **Future:** Will be refactored to core as user-configurable themes
-## Architecture Principle
-**Single Source of Truth:**
-- Core holds universal knowledge
-- Agents reference core, don't duplicate
-- Updates to core benefit all agents
-- Agents specialize with domain knowledge
-**DRY (Don't Repeat Yourself):**
-- Element creation logic: ONCE in core
-- Text width calculation: ONCE in core
-- Validation process: ONCE in core
-- Arrow binding patterns: ONCE in core
-## Future Enhancements
-1. **External Library Loader** - Load .excalidrawlib files from libraries.excalidraw.com
-2. **Theme Management** - User-configurable color themes saved in core
-3. **Component Library** - Shared reusable components across agents
-4. **Layout Algorithms** - Auto-layout helpers for positioning elements

package/src/core/resources/excalidraw/excalidraw-helpers.md DELETED Viewed

@@ -1,127 +0,0 @@
-# Excalidraw Element Creation Guidelines
-## Text Width Calculation
-For text elements inside shapes (labels):
-```
-text_width = (text.length × fontSize × 0.6) + 20
-```
-Round to nearest 10 for grid alignment.
-## Element Grouping Rules
-**CRITICAL:** When creating shapes with labels:
-1. Generate unique IDs:
-   - `shape-id` for the shape
-   - `text-id` for the text
-   - `group-id` for the group
-2. Shape element must have:
-   - `groupIds: [group-id]`
-   - `boundElements: [{type: "text", id: text-id}]`
-3. Text element must have:
-   - `containerId: shape-id`
-   - `groupIds: [group-id]` (SAME as shape)
-   - `textAlign: "center"`
-   - `verticalAlign: "middle"`
-   - `width: calculated_width`
-## Grid Alignment
-- Snap all `x`, `y` coordinates to 20px grid
-- Formula: `Math.round(value / 20) * 20`
-- Spacing between elements: 60px minimum
-## Arrow Creation
-### Straight Arrows
-Use for forward flow (left-to-right, top-to-bottom):
-```json
-{
-  "type": "arrow",
-  "startBinding": {
-    "elementId": "source-shape-id",
-    "focus": 0,
-    "gap": 10
-  },
-  "endBinding": {
-    "elementId": "target-shape-id",
-    "focus": 0,
-    "gap": 10
-  },
-  "points": [[0, 0], [distance_x, distance_y]]
-}
-```
-### Elbow Arrows
-Use for upward flow, backward flow, or complex routing:
-```json
-{
-  "type": "arrow",
-  "startBinding": {...},
-  "endBinding": {...},
-  "points": [
-    [0, 0],
-    [intermediate_x, 0],
-    [intermediate_x, intermediate_y],
-    [final_x, final_y]
-  ],
-  "elbowed": true
-}
-```
-### Update Connected Shapes
-After creating arrow, update `boundElements` on both connected shapes:
-```json
-{
-  "id": "shape-id",
-  "boundElements": [
-    { "type": "text", "id": "text-id" },
-    { "type": "arrow", "id": "arrow-id" }
-  ]
-}
-```
-## Theme Application
-Theme colors should be applied consistently:
-- **Shapes**: `backgroundColor` from theme primary fill
-- **Borders**: `strokeColor` from theme accent
-- **Text**: `strokeColor` = "#1e1e1e" (dark text)
-- **Arrows**: `strokeColor` from theme accent
-## Validation Checklist
-Before saving, verify:
-- [ ] All shapes with labels have matching `groupIds`
-- [ ] All text elements have `containerId` pointing to parent shape
-- [ ] Text width calculated properly (no cutoff)
-- [ ] Text alignment set (`textAlign` + `verticalAlign`)
-- [ ] All elements snapped to 20px grid
-- [ ] All arrows have `startBinding` and `endBinding`
-- [ ] `boundElements` array updated on connected shapes
-- [ ] Theme colors applied consistently
-- [ ] No metadata or history in final output
-- [ ] All IDs are unique
-## Optimization
-Remove from final output:
-- `appState` object
-- `files` object (unless images used)
-- All elements with `isDeleted: true`
-- Unused library items
-- Version history

package/src/core/resources/excalidraw/library-loader.md DELETED Viewed

@@ -1,50 +0,0 @@
-# External Library Loader
-**Status:** Placeholder for future implementation
-## Purpose
-Load external .excalidrawlib files from <https://libraries.excalidraw.com> or custom sources.
-## Planned Capabilities
-- Load libraries by URL
-- Load libraries from local files
-- Merge multiple libraries
-- Filter library components
-- Cache loaded libraries
-## API Reference
-Will document how to use:
-- `importLibrary(url)` - Load library from URL
-- `loadSceneOrLibraryFromBlob()` - Load from file
-- `mergeLibraryItems()` - Combine libraries
-## Usage Example
-```yaml
-# Future workflow.yaml structure
-libraries:
-  - url: 'https://libraries.excalidraw.com/libraries/...'
-    filter: ['aws', 'cloud']
-  - path: '{project-root}/_data/custom-library.excalidrawlib'
-```
-## Implementation Notes
-This will be developed when agents need to leverage the extensive library ecosystem available at <https://libraries.excalidraw.com>.
-Hundreds of pre-built component libraries exist for:
-- AWS/Cloud icons
-- UI/UX components
-- Business diagrams
-- Mind map shapes
-- Floor plans
-- And much more...
-## User Configuration
-Future: Users will be able to configure favorite libraries in their XIAOMA config for automatic loading.

package/src/core/resources/excalidraw/validate-json-instructions.md DELETED Viewed

@@ -1,79 +0,0 @@
-# JSON Validation Instructions
-## Purpose
-Validate Excalidraw JSON files after saving to catch syntax errors (missing commas, brackets, quotes).
-## How to Validate
-Use Node.js built-in JSON parsing to validate the file:
-```bash
-node -e "JSON.parse(require('fs').readFileSync('FILE_PATH', 'utf8')); console.log('✓ Valid JSON')"
-```
-Replace `FILE_PATH` with the actual file path.
-## Exit Codes
-- Exit code 0 = Valid JSON
-- Exit code 1 = Invalid JSON (syntax error)
-## Error Output
-If invalid, Node.js will output:
-- Error message with description
-- Position in file where error occurred
-- Line and column information (if available)
-## Common Errors and Fixes
-### Missing Comma
-```
-SyntaxError: Expected ',' or '}' after property value
-```
-**Fix:** Add comma after the property value
-### Missing Bracket/Brace
-```
-SyntaxError: Unexpected end of JSON input
-```
-**Fix:** Add missing closing bracket `]` or brace `}`
-### Extra Comma (Trailing)
-```
-SyntaxError: Unexpected token ,
-```
-**Fix:** Remove the trailing comma before `]` or `}`
-### Missing Quote
-```
-SyntaxError: Unexpected token
-```
-**Fix:** Add missing quote around string value
-## Workflow Integration
-After saving an Excalidraw file, run validation:
-1. Save the file
-2. Run: `node -e "JSON.parse(require('fs').readFileSync('{{save_location}}', 'utf8')); console.log('✓ Valid JSON')"`
-3. If validation fails:
-   - Read the error message for line/position
-   - Open the file at that location
-   - Fix the syntax error
-   - Save and re-validate
-4. Repeat until validation passes
-## Critical Rule
-**NEVER delete the file due to validation errors - always fix the syntax error at the reported location.**

package/src/core/tasks/advanced-elicitation-methods.csv DELETED Viewed

@@ -1,51 +0,0 @@
-num,category,method_name,description,output_pattern
-1,collaboration,Stakeholder Round Table,Convene multiple personas to contribute diverse perspectives - essential for requirements gathering and finding balanced solutions across competing interests,perspectives → synthesis → alignment
-2,collaboration,Expert Panel Review,Assemble domain experts for deep specialized analysis - ideal when technical depth and peer review quality are needed,expert views → consensus → recommendations
-3,collaboration,Debate Club Showdown,Two personas argue opposing positions while a moderator scores points - great for exploring controversial decisions and finding middle ground,thesis → antithesis → synthesis
-4,collaboration,User Persona Focus Group,Gather your product's user personas to react to proposals and share frustrations - essential for validating features and discovering unmet needs,reactions → concerns → priorities
-5,collaboration,Time Traveler Council,Past-you and future-you advise present-you on decisions - powerful for gaining perspective on long-term consequences vs short-term pressures,past wisdom → present choice → future impact
-6,collaboration,Cross-Functional War Room,Product manager + engineer + designer tackle a problem together - reveals trade-offs between feasibility desirability and viability,constraints → trade-offs → balanced solution
-7,collaboration,Mentor and Apprentice,Senior expert teaches junior while junior asks naive questions - surfaces hidden assumptions through teaching,explanation → questions → deeper understanding
-8,collaboration,Good Cop Bad Cop,Supportive persona and critical persona alternate - finds both strengths to build on and weaknesses to address,encouragement → criticism → balanced view
-9,collaboration,Improv Yes-And,Multiple personas build on each other's ideas without blocking - generates unexpected creative directions through collaborative building,idea → build → build → surprising result
-10,collaboration,Customer Support Theater,Angry customer and support rep roleplay to find pain points - reveals real user frustrations and service gaps,complaint → investigation → resolution → prevention
-11,advanced,Tree of Thoughts,Explore multiple reasoning paths simultaneously then evaluate and select the best - perfect for complex problems with multiple valid approaches,paths → evaluation → selection
-12,advanced,Graph of Thoughts,Model reasoning as an interconnected network of ideas to reveal hidden relationships - ideal for systems thinking and discovering emergent patterns,nodes → connections → patterns
-13,advanced,Thread of Thought,Maintain coherent reasoning across long contexts by weaving a continuous narrative thread - essential for RAG systems and maintaining consistency,context → thread → synthesis
-14,advanced,Self-Consistency Validation,Generate multiple independent approaches then compare for consistency - crucial for high-stakes decisions where verification matters,approaches → comparison → consensus
-15,advanced,Meta-Prompting Analysis,Step back to analyze the approach structure and methodology itself - valuable for optimizing prompts and improving problem-solving,current → analysis → optimization
-16,advanced,Reasoning via Planning,Build a reasoning tree guided by world models and goal states - excellent for strategic planning and sequential decision-making,model → planning → strategy
-17,competitive,Red Team vs Blue Team,Adversarial attack-defend analysis to find vulnerabilities - critical for security testing and building robust solutions,defense → attack → hardening
-18,competitive,Shark Tank Pitch,Entrepreneur pitches to skeptical investors who poke holes - stress-tests business viability and forces clarity on value proposition,pitch → challenges → refinement
-19,competitive,Code Review Gauntlet,Senior devs with different philosophies review the same code - surfaces style debates and finds consensus on best practices,reviews → debates → standards
-20,technical,Architecture Decision Records,Multiple architect personas propose and debate architectural choices with explicit trade-offs - ensures decisions are well-reasoned and documented,options → trade-offs → decision → rationale
-21,technical,Rubber Duck Debugging Evolved,Explain your code to progressively more technical ducks until you find the bug - forces clarity at multiple abstraction levels,simple → detailed → technical → aha
-22,technical,Algorithm Olympics,Multiple approaches compete on the same problem with benchmarks - finds optimal solution through direct comparison,implementations → benchmarks → winner
-23,technical,Security Audit Personas,Hacker + defender + auditor examine system from different threat models - comprehensive security review from multiple angles,vulnerabilities → defenses → compliance
-24,technical,Performance Profiler Panel,Database expert + frontend specialist + DevOps engineer diagnose slowness - finds bottlenecks across the full stack,symptoms → analysis → optimizations
-25,creative,SCAMPER Method,Apply seven creativity lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) - systematic ideation for product innovation,S→C→A→M→P→E→R
-26,creative,Reverse Engineering,Work backwards from desired outcome to find implementation path - powerful for goal achievement and understanding endpoints,end state → steps backward → path forward
-27,creative,What If Scenarios,Explore alternative realities to understand possibilities and implications - valuable for contingency planning and exploration,scenarios → implications → insights
-28,creative,Random Input Stimulus,Inject unrelated concepts to spark unexpected connections - breaks creative blocks through forced lateral thinking,random word → associations → novel ideas
-29,creative,Exquisite Corpse Brainstorm,Each persona adds to the idea seeing only the previous contribution - generates surprising combinations through constrained collaboration,contribution → handoff → contribution → surprise
-30,creative,Genre Mashup,Combine two unrelated domains to find fresh approaches - innovation through unexpected cross-pollination,domain A + domain B → hybrid insights
-31,research,Literature Review Personas,Optimist researcher + skeptic researcher + synthesizer review sources - balanced assessment of evidence quality,sources → critiques → synthesis
-32,research,Thesis Defense Simulation,Student defends hypothesis against committee with different concerns - stress-tests research methodology and conclusions,thesis → challenges → defense → refinements
-33,research,Comparative Analysis Matrix,Multiple analysts evaluate options against weighted criteria - structured decision-making with explicit scoring,options → criteria → scores → recommendation
-34,risk,Pre-mortem Analysis,Imagine future failure then work backwards to prevent it - powerful technique for risk mitigation before major launches,failure scenario → causes → prevention
-35,risk,Failure Mode Analysis,Systematically explore how each component could fail - critical for reliability engineering and safety-critical systems,components → failures → prevention
-36,risk,Challenge from Critical Perspective,Play devil's advocate to stress-test ideas and find weaknesses - essential for overcoming groupthink,assumptions → challenges → strengthening
-37,risk,Identify Potential Risks,Brainstorm what could go wrong across all categories - fundamental for project planning and deployment preparation,categories → risks → mitigations
-38,risk,Chaos Monkey Scenarios,Deliberately break things to test resilience and recovery - ensures systems handle failures gracefully,break → observe → harden
-39,core,First Principles Analysis,Strip away assumptions to rebuild from fundamental truths - breakthrough technique for innovation and solving impossible problems,assumptions → truths → new approach
-40,core,5 Whys Deep Dive,Repeatedly ask why to drill down to root causes - simple but powerful for understanding failures,why chain → root cause → solution
-41,core,Socratic Questioning,Use targeted questions to reveal hidden assumptions and guide discovery - excellent for teaching and self-discovery,questions → revelations → understanding
-42,core,Critique and Refine,Systematic review to identify strengths and weaknesses then improve - standard quality check for drafts,strengths/weaknesses → improvements → refined
-43,core,Explain Reasoning,Walk through step-by-step thinking to show how conclusions were reached - crucial for transparency,steps → logic → conclusion
-44,core,Expand or Contract for Audience,Dynamically adjust detail level and technical depth for target audience - matches content to reader capabilities,audience → adjustments → refined content
-45,learning,Feynman Technique,Explain complex concepts simply as if teaching a child - the ultimate test of true understanding,complex → simple → gaps → mastery
-46,learning,Active Recall Testing,Test understanding without references to verify true knowledge - essential for identifying gaps,test → gaps → reinforcement
-47,philosophical,Occam's Razor Application,Find the simplest sufficient explanation by eliminating unnecessary complexity - essential for debugging,options → simplification → selection
-48,philosophical,Trolley Problem Variations,Explore ethical trade-offs through moral dilemmas - valuable for understanding values and difficult decisions,dilemma → analysis → decision
-49,retrospective,Hindsight Reflection,Imagine looking back from the future to gain perspective - powerful for project reviews,future view → insights → application
-50,retrospective,Lessons Learned Extraction,Systematically identify key takeaways and actionable improvements - essential for continuous improvement,experience → lessons → actions