The Project I Inherited Had No Memory Either

Description and use

A new teammate struggled to understand why authentication was split across three places due to missing documentation. Using KMS, decisions were recovered, guardrails added, and a refactor plan generated, speeding up onboarding.

Problem

New team members struggled to understand why authentication was handled in three different places due to missing documentation and inconsistent decision records.

Outcome

New hires quickly understood project decisions, the knowledge base was enriched with missing artifacts, and a concrete refactor plan was produced to unify authentication logic.

Workflow

• Run /kms:bootstrap to extend existing docs and generate decision stubs
• Run /kms:onboard to create a 5‑day role‑specific ramp‑up plan
• Use /kms:refactor-plan to map auth split, identify guardrails, and produce phased refactor steps

Evidence

It found our existing docs/decisions folder and extended it instead of replacing it

Source

The auth-in-three-places thing was one of them.

Source

Phase 3 came back with ordered phases, each carrying concrete steps, a verification checkpoint, and a rollback strategy specific to that phase

Source