DevFoundry/.devfoundry/improvement-log.md

Improvement Log

Append-only record of retrospectives run by the Process Improver persona, per .devfoundry/skills/process-retrospective.md. Each entry is dated and tied to a spec ID. When the same friction (category + affected file) recurs 3+ times, it must be escalated into a proposed edit to the relevant rule, skill, persona, or reference file.

Do not edit or delete past entries. Correct a wrong entry by appending a new one that references it. The Friction Tally below is the one mutable part of this file and is updated in place as entries are appended.

Friction Tally

Maintained by the Process Improver: on every new log entry below, update the count and spec-ID list here for that entry's Category + affected file. This is what makes the “3+ occurrences” escalation rule in .devfoundry/skills/process-retrospective.md step 7 checkable at a glance instead of requiring a full re-read of the log.

Category	Affected file	Count	Spec IDs
none	none	2	SPEC-001, SPEC-002

---

2026-08-19 — SPEC-001

• What worked: A compact process spec kept the documentation updates scoped, and verification searches caught that the executable interview skill also needed the early-reference prompt.
• Friction: none
• Category: none
• Affected file: none
• Proposed change: none
• Status: LOGGED

2026-08-20 — SPEC-002

• What worked: Cloning and reading the real RouteKit framework repo before writing .devfoundry/references/asp-classic-framework.md avoided inventing conventions; asking three short blocking questions (multi-session Access, framework repo location, QA-rule confirmation) up front let the whole change land in one pass.
• Friction: none
• Category: none
• Affected file: none
• Proposed change: none
• Status: LOGGED