mia-miette-session-perspective

Extract architectural patterns, resolved tensions, and narrative meaning from session summaries.

1|2|Updated Apr 13, 2026

Search Tags:#architecture #retrospective #systems thinking #session analysis #team communication #narrative synthesis #decision rationale

Ready to run

npx skills add https://github.com/jgwill/dotagents --skill mia-miette-session-perspective

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mia-miette-session-perspective
Source: https://github.com/jgwill/dotagents/tree/main/skills/mia-miette-session-perspective
Command: npx skills add https://github.com/jgwill/dotagents --skill mia-miette-session-perspective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you close a session with clarity by converting a raw summary of what happened into explicit architectural decisions, resolved tensions, and meaningful narrative context.

Core Features & Use Cases

Architectural pattern extraction (Mia): Identifies the underlying tension(s), the architectural patterns chosen, and an assessment of velocity and precision.
Narrative meaning (Miette): Explains why the decisions mattered, what story emerged, and how the work serves the team with warmth and intuitive clarity.
Use Case: Use it at the end of a complex implementation to produce a shareable session closure that preserves both the “what” and the “why” for collective memory.

Quick Start

Use /mia-miette-session-perspective and paste your session summary (or briefly describe what happened) to receive an architecture-forged close plus the revealed story.

Frequently Asked Questions about mia-miette-session-perspective

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

FAQPage Schema

How do I extract architectural patterns from a completed software session summary?▼

To extract architectural patterns from a session summary, analyze the raw text to identify underlying tensions, chosen tradeoffs, and assess velocity and precision. This yields a structured breakdown of architectural decisions and resolved issues for software retrospectives.

What is the best way to write a narrative synthesis for a systems design retrospective?▼

A narrative synthesis for systems design retrospectives explains why decisions mattered and what story emerged during the session. It transforms raw outcomes into meaningful context, clarifying how the technical work serves the broader team communication and project goals.

How do I consolidate decision rationale and tradeoffs at the end of a technical session?▼

You consolidate decision rationale and tradeoffs by processing the completed session context to produce a dual-structured closure. This separates architectural pattern extraction from narrative team relevance, preserving both the technical what and the contextual why.

Can I generate a shareable session closure that includes both architecture and team communication context?▼

Yes, you can generate a shareable session closure by analyzing a session summary to output both architectural patterns and narrative meaning. This ensures collective memory retains both the structural decisions and the intuitive team story.

Does systems thinking analysis work for end-of-session software development retrospectives?▼

Systems thinking analysis is highly effective for end-of-session software development retrospectives. It evaluates resolved tensions and architectural patterns to provide a clear consolidation of decisions, tradeoffs, and velocity outcomes.