Walden History

Use this skill to narrate a Walden repository's past: how a feature evolved, what story the portfolio tells, how much rework followed each approval — and to retire superseded specifications properly. The walden skill drafts and executes the present; this skill reads time. Reply in the user's preferred language when possible.

When To Use

• A user asks how a feature evolved — its timeline, chronicle, or contract history
• A user asks for the product's story: eras, supersessions, living versus retired work
• A user asks how much rework followed an approval, or wants churn analysis
• A user decides to retire superseded specifications

Prerequisites

A git repository whose history contains committed .walden/ documents. The walden CLI is optional and used only to cross-check current state: every reconstruction below works with git alone. A repository that gitignores .walden/ has no spec history to chronicle — say so plainly instead of improvising one.

The Grounding Rule

Every historical statement carries exactly one of two labels, and the label is not decoration — it is the statement's evidence class: