speckit-retrospect-runlisted

## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). Treat it as optional scope guidance, such as a focus area, a pasted transcript summary, or a preferred disposition. ## Outline Run a retrospective on the current agent session while the work is still fresh in context. The goal is to identify concrete improvements to the repository's context-management surface area: `AGENTS.md`, `CLAUDE.md`, `.claude/settings.json`, `.agents/skills/`, `.agents/commands/`, `.specify/templates/`, `dev/knowledge/`, `dev/guides/`, `dev/guidelines/`, `dev/adr/`, and product or architecture decisions that caused avoidable friction. This command closes the loop from "the agent struggled with X" to "X is captured as an approved repo improvement, dedicated PR, GitHub issue, or local-only note." ## Operating Constraints - Stay read-only until the user approves the report and any disposition buckets. Do not edit files, commit, push, or create GitHub issues before approval. - Present the full retrospective before taking action. Ask for explicit approval per disposition bucket: `fix-now`, `open-pr`, `github-issue`, and `local-only`. - For `fix-now`, present a diff preview or precise patch plan before writing files. Apply only the approved changes. - For `github-issue`, defer to the existing `create-issue` skill when available; if it is unavailable, use `gh issue create` only after the user approves the exact issue content. - Respect `AGENTS.md