メニュー
Improve agent harness configuration based on recent friction points. Use when invoked as `$retro` or when the user asks for autonomous cleanup of Codex, agent harness, or migrated Claude configuration.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
End-of-day — draft and post daily comments for tracked tickets missing a comment
Morning startup workflow for daily notes, yesterday summary, agenda, status comments, meeting sections, and daily branch setup. Use when invoked as `$work-start` or when the user asks to start the work day.
Track a Linear ticket or GitHub PR in today's daily note with fields and timestamped activity. Use when invoked as `$work-track` or when the user asks to track a work item.
Start work on a Linear ticket by gathering context, planning, creating a branch/worktree, implementing, testing, opening a draft PR, and updating Linear. Use when invoked as `$linear-plan` or when the user asks to start a Linear ticket.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
| name | retro |
| description | Improve agent harness configuration based on recent friction points. Use when invoked as `$retro` or when the user asks for autonomous cleanup of Codex, agent harness, or migrated Claude configuration. |
Apply targeted agent-configuration improvements based on recent friction points.
Use the user's supplied friction points. If none are provided, ask for 2-5 concrete issues from recent sessions before editing.
Prefer active Codex and shared harness paths:
.codex/.agents/AGENTS.md or provided global/project instructionsRead or edit .claude/ only when the friction point is explicitly about Claude parity or a migration source.
Load relevant baseline instructions and config.
For each friction point, identify root cause:
Create a concrete fix plan listing file, change, and prevented failure.
Apply only targeted edits. Preserve unrelated config.
Validate modified files:
Report:
## Retrospective Report
### Friction Points
- <issue> → <root cause> → <fix>
### Changes Made
| File | Change | Prevents |
|---|---|---|
### Validation
- ...