Retrospective

Reflect on how the work on the current branch actually went — not what was delivered, but what cost time — and turn that into durable guidance so future sessions avoid the same back-and-forths.

Arguments: $0 = [base-branch] (optional, default auto-detected: develop for mk-copilot, else main / master).

0. Preconditions

pwd
git rev-parse --abbrev-ref HEAD

• Do not run on the base branch itself (main/master/develop). If on base, stop and ask the user which branch to retrospect.
• Verify devsql is installed: which devsql. If missing, continue without devsql signals and note this to the user.

1. Establish Scope