retro
Conduct a retrospective on the current conversation or work session to extract learnings and improve future workflows.
- License 许可
- MIT
- 最近更新
- 2026-10-30
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- retro
- description
- Conduct a retrospective on the current conversation or work session to extract learnings and improve future workflows.
- disable-model-invocation
- true
03 SKILL.md 正文
The user has asked for a retrospective. You are conducting a structured reflection on the current conversation, task, or session to improve future interactions, consolidate insights, and eliminate friction.
Steps
-
If
writing-for-agentsis available, consult it for communication and prompt structure guidelines. -
Review the transcript of the current session (or the specified topic/session). Identify what went smoothly, where friction or misunderstandings occurred, and what took longer than expected.
-
Analyze the session across these four core dimensions:
- Communication & Alignment:
- Where did instructions fail to land or cause confusion?
- Did the agent make unverified assumptions or act prematurely?
- What clarifying questions should have been asked earlier?
- Knowledge & Insights Consolidation:
- Were new domain concepts, definitions, decisions, or user preferences established during this session?
- Should any key facts, terminology, or takeaways be promoted into project documentation, notes, or long-term memory?
- Instruction & Prompt Improvement:
- Can steering files (e.g.,
AGENTS.md, system prompt, project instructions) be updated with positive, checkable rules to prevent this friction next time? - Are there rules or instructions that are redundant, ambiguous, or no longer relevant (sediment)?
- Can steering files (e.g.,
- Tooling & Efficiency:
- Were there inefficient tool calls, repetitive manual steps, or missing context that slowed the process down?
- Present the retrospective findings clearly:
- Highlights: Key successes and settled outcomes.
- Friction Points: Root causes of any missteps or delays.
- Concrete Actions: Specific updates to instructions, docs, or habits, ranked by impact.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wait-what
Stop. That last message did not land: re-pitch it.
to-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
teach
Teach the user a new skill or concept, within this workspace.
research
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
handoff
Compact the current conversation into a handoff document for another agent to pick up.