Generate an actionable retro from Pi session logs + orchestration artifacts, and propose concrete doc/template improvements.
Generate an actionable retro from Pi session logs + orchestration artifacts, and propose concrete doc/template improvements.
npx skills add https://github.com/l3wi/agents-workflow --skill retro이 명령을 Claude Code에 복사하여 붙여넣어 스킬을 설치하세요
Bootstrap new projects or add the agents-workflow system to existing projects. Use for new project scaffolding (Next.js, Python, Rust) or adding workflow capabilities to any git repository.
Entry point for feature planning workflow. Guides users through PRD creation, spec generation, and swarm design with automatic context management.
Execute implementation plans with parallel worker agents in git worktrees. Spawns agents, monitors progress, coordinates merges. Use after /skill:plan completes.
Implement features using worktree-based development with TDD. Use after spec approval to build features in isolated git worktrees with quality gates.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Analyze codebase for optimization and refactoring opportunities. Use for periodic quality checks, identifying tech debt, and planning improvements.
| name | retro |
| description | Generate an actionable retro from Pi session logs + orchestration artifacts, and propose concrete doc/template improvements. |
Turn recent workflow execution into improvements.
Use this skill when the user asks for a retro, postmortem, workflow improvement, or wants to learn from agent mistakes.
Write:
docs/retros/{feature}/{timestamp}.mddocs/retros/{feature}/{timestamp}-actions.md~/.pi/agent/sessions/.../*.jsonl.orchestration-state.json.orchestration-logs/**/events.jsonl, stderr.log, validation.phase.json, scope.jsondocs/specs/{feature}-spec.md, docs/plans/{feature}.md, docs/tasks/{feature}-phase-*.md.orchestration-state.json.feature.{feature}.YYYY-MM-DDTHH-mm-ssZPi sessions are stored as JSONL under:
~/.pi/agent/sessions/<cwd-sanitized>/...jsonlFind the correct session log:
# list the most recent sessions for this project
ls -t ~/.pi/agent/sessions/* | head
# narrow to this cwd by searching for the cwd header line
rg -n --fixed-string '"cwd":"' ~/.pi/agent/sessions -S | head
Pick the most recent JSONL file whose first line contains:
"type":"session" and your project cwd.From the JSONL, extract:
tool_execution_end with isError=true)Examples:
# show tool errors
jq -rc 'select(.type=="tool_execution_end" and .isError==true)' session.jsonl | tail -n 50
# show assistant final messages
jq -rc 'select(.type=="message_end" and .message.role=="assistant") | .message.content' session.jsonl | tail -n 20
Read .orchestration-state.json and list:
Then inspect:
events.jsonl for each phase runvalidation.phase.json and scope.jsondocs/retros/{feature}/{timestamp}.mdMust include:
docs/retros/{feature}/{timestamp}-actions.mdMust include:
If the retro is complex, spawn:
session-reviewerchore/{feature}-retroAnd have it write the two retro outputs.