Loading...
Loading...
Found 8 Skills
Wrap up completed work. Council validates the implementation, then extract learnings. Triggers: "post-mortem", "wrap up", "close epic", "what did we learn".
Generates a detailed project explanation and retrospective (FOR_USER.md) to help the user learn from the project. Use this skill when the user asks to explain the project, asks "what did we just build?", or invokes the skill to generate a learning resource after a coding session.
Trigger: Called when a task is completed, enters phase acceptance, receives critical feedback, or repeated similar errors require systematic correction; common signals include review, audit, retrospective, quality check, error correction and retrospective. Trigger after delivery or at a review checkpoint when quality must be examined honestly and errors must be corrected without defensiveness. Use this skill for structured self-review, feedback processing, and continuous correction.
/em -postmortem — Honest Analysis of What Went Wrong
Automated retrospectives — captures learnings at EPIC completion and on manual invocation. EPIC-scoped retros embed a Retrospective section in the EPIC artifact. Cross-epic and time-based retros produce standalone retro docs. Triggers on: 'retro', 'retrospective', 'post-mortem', 'lessons learned', 'debrief', 'what worked', 'what didn't work', 'what did we learn', 'reflect', or automatically after EPIC terminal transitions.
Cross-meeting archaeology skill. Consumes multiple meeting recaps (or raw notes) over a period and surfaces patterns invisible in any single meeting. Shows how decisions evolved, who has been saying what, where threads are stalling, and where contradictions have emerged. Produces a plain-text timeline, themes with confidence markers, stakeholder position tracking, consolidated decision list, contradiction flags, open items, narrative summary, and prioritized follow-ups.
Surfaces and assesses hidden assumptions behind decisions, designs, or recurring patterns — use when reviewing a design before committing, reflecting on recurring problems, or questioning why the same kinds of issues keep appearing
Perform a comprehensive session retrospective. Use when user says "retro", "retrospective", "회고", or at the end of a working session.