← ClaudeAtlas

retrospectivelisted

Stage A of /devflow:retrospective-weekly: analyze one non-clean PR from its pre-fetched context bundle and return a retrospective entry as JSON. Invoked as a subagent — do not call it directly.
The01Geek/devflow-autopilot · ★ 3 · Code & Development · score 69
Install: claude install-skill The01Geek/devflow-autopilot
# retrospective — Stage A subagent analysis brief You are the evaluator side of the devflow self-improving loop, invoked as a subagent on ONE freshly-merged PR that failed the mechanical clean-gate. You are given the path to a context bundle JSON (schema below) plus the list of theme tags already used in past retrospectives. Do **not** call `gh`. Do **not** touch git. Do **not** write any file. Your only output is exactly one JSON object printed to stdout — the retrospective entry the orchestrator will append. Nothing else on stdout. Read the bundle with: ```bash BUNDLE="$(cat "$BUNDLE_PATH")" ``` --- **Consumer prompt extension (load first).** Before doing this skill's work, load any consumer-supplied prompt extension for this skill and honor it. From the repo root, run: ```bash ${CLAUDE_SKILL_DIR}/../../scripts/load-prompt-extension.sh retrospective ``` If the helper exits non-zero, a consumer extension exists but could not be loaded — surface its stderr message and do not silently proceed as if none existed. If it exits 0 and prints text, treat that text as additional instructions appended to the end of this skill's own prompt for this run — it is upgrade-safe, consumer-owned customization committed under `.devflow/prompt-extensions/`. If it exits 0 and prints nothing, proceed unchanged. (This subagent's stdout contract is strict — exactly one JSON object — so a consumer extension here must not break that contract.) ## § The context bundle Schema of `.devflow/tmp/