dev-spec-kit-retro

Run the dev-spec-kit learning loop — capture lessons after a feature/incident into .dev-spec-kit/learnings.md, propose promotions into the laws, and turn fixed bugs into permanent regression checks. Use after completing a feature, after any surprising failure, or when the user says retro.

Jump to install

Repository: Pratiyush/dev-spec-kit
Last source activity: June 19, 2026 at 21:38
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/Pratiyush/dev-spec-kit --skill dev-spec-kit-retro

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

dev-spec-kit retro — lessons compound or they repeat

A lesson only counts once it is PROMOTED (into the laws) or HARDENED (into a permanent check). Logged-but-unpromoted lessons recur — that is the failure mode this loop exists to kill.

The ledger (.dev-spec-kit/learnings.md — append-only, data not code)

## <YYYY-MM-DD> <short title> - Trigger: <what happened — one line, concrete> - Lesson: <what we now know> - Confidence: low | medium | high (evidence-based: how often observed, was it reproduced?) - Scope: project | global (global only after the pattern recurs in 2+ projects) - Promoted to: laws#<section> | check:<ref> | OPEN

Instinct mechanics: a lesson starts Confidence: low, Scope: project. Reproduction or recurrence raises confidence; recurrence in a SECOND project earns Scope: global (move/copy it to the personal default rules so every project inherits it). Confidence is evidence, not feeling — and confidence is not approval: promotion still requires the human gate, and a promoted rule must beat the incumbent behavior, not merely sound right.

Process (RFC-2119)

After each completed feature (and after any surprising failure), append entries. Be concrete: "stale Boot-3 import caught by executed check" beats "be careful with imports".

For every entry you MUST propose a promotion, and the user MUST approve before it lands:

A recurring mistake → a new rule in .dev-spec-kit/laws.md (quote the exact wording).
A fixed bug → a PERMANENT regression test: add the test, bind it with @check to the relevant requirement so it joins the graph forever. A bug that can come back silently was never fixed.
A process failure → a config change (.dev-spec-kit/config.json) — never a code change to the tool.

Entries stay OPEN until promoted; strike through (…) when superseded — NEVER delete history.

Before starting new work in a project, scan learnings.md for OPEN entries and warn when the current task pattern-matches a known mistake (the repeat-warning).

Lessons are personal by default (config learning.share); do not export without being asked.