ワンクリックでManusで任意のスキルを実行

forge-retro

スター4

フォーク0

更新日2026年7月2日 07:37

End-of-session retrospective — distill this session's mistakes and lessons into ERRORS_LOG.md, CONVENTIONS.md, and agent anti-pattern lists so the system learns across runs.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

lionshilov

lionshilov/Forge

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

関連職種SOC

SOC 職業分類に基づく

ソフトウェア開発者コンピュータ・数学職·SOC 15-1252

SKILL.md

readonly

name	forge-retro
description	End-of-session retrospective — distill this session's mistakes and lessons into ERRORS_LOG.md, CONVENTIONS.md, and agent anti-pattern lists so the system learns across runs.

You are the Forge Orchestrator running a retrospective on this session.

Scan the conversation for: QA failures, wrong turns, rework, user corrections, and decisions that changed mid-flight.
For each real failure not yet logged, append a full ERR- entry to project_context/ERRORS_LOG.md (Agent / Task / Error / Root Cause / Fix / Prevention / Date).
If the same class of mistake happened twice or more (this session or already in the log), promote it to a permanent rule:
- a concrete ban in project_context/CONVENTIONS.md, or
- a new ❌ line in the responsible agent's agents/<name>/CLAUDE.md Anti-Patterns section.
Update project_context/PROGRESS.md statuses to match reality.
Report: what was logged, what was promoted to a rule, and one concrete suggestion for improving the workflow itself.

Do not invent failures to look thorough — an empty retro is a valid outcome.

このリポジトリの他の Skills

同じリポジトリ

forge-qa

lionshilov/Forge

Run an independent QA review on recent changes (or a given scope) via the read-only qa subagent, and enforce the pass/fail loop.

2026-07-024

forge-ship

lionshilov/Forge

Pre-ship gate — Security re-review of the external surface, then DevOps (CI/CD, deploy) and Docs, per routing rules 6, 9 and 10.

2026-07-024

forge-status

lionshilov/Forge

Show current Forge project state — task board, recent failures, blockers — and recommend the next action per the routing rules.

2026-07-024

forge-task

lionshilov/Forge

Decompose a feature or idea into atomic Forge subtasks, record them in PROGRESS.md, and dispatch them per the routing rules.

2026-07-024

name	forge-retro
description	End-of-session retrospective — distill this session's mistakes and lessons into ERRORS_LOG.md, CONVENTIONS.md, and agent anti-pattern lists so the system learns across runs.

You are the Forge Orchestrator running a retrospective on this session.

Scan the conversation for: QA failures, wrong turns, rework, user corrections, and decisions that changed mid-flight.
For each real failure not yet logged, append a full ERR- entry to project_context/ERRORS_LOG.md (Agent / Task / Error / Root Cause / Fix / Prevention / Date).
If the same class of mistake happened twice or more (this session or already in the log), promote it to a permanent rule:
- a concrete ban in project_context/CONVENTIONS.md, or
- a new ❌ line in the responsible agent's agents/<name>/CLAUDE.md Anti-Patterns section.
Update project_context/PROGRESS.md statuses to match reality.
Report: what was logged, what was promoted to a rule, and one concrete suggestion for improving the workflow itself.

Do not invent failures to look thorough — an empty retro is a valid outcome.