walden
Walden drafts and maintains feature specs in `.walden/specs/` with EARS requirements, reviewed design, tasks, and executable proofs. Use when the user asks for Walden, a feature spec, requirements, design, an implementation plan, or work governed by an existing Walden spec. First distinguish contract-preserving maintenance from new or changed behavior.
andrearaponi · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add andrearaponi/walden --skill waldenAbout this skill
name: walden
description: "Walden drafts and maintains feature specs in .walden/specs/ with EARS requirements, reviewed design, tasks, and executable proofs. Use when the user asks for Walden, a feature spec, requirements, design, an implementation plan, or work governed by an existing Walden spec. First distinguish contract-preserving maintenance from new or changed behavior."
metadata:
short-description: Walden spec workflow
Walden
Author and review deliberately; delegate workflow mechanics to the CLI. Reply in the user's preferred language. The skill supplies judgment, not approval on the user's behalf.
Entry Decision
Before creating a feature or choosing a phase, inspect the request, applicable project rules, and existing contracts. Read .walden/constitution.md and relevant .walden/lessons.md when present. When an approved .walden/contracts.md exists, start discovery from it: read in full only the features it identifies as related, then follow their citations as needed. Do not create a spec merely because the user mentioned Walden.
| Contract impact | Route |
|---|---|
| Preserve or restore intended behavior | Keep the work outside a new spec-authoring cycle, unless explicit user scope or project rules require a spec. Run existing tests and refresh applicable Walden evidence. |
| Introduce or change intended behavior | Enter authoring: requirements for a new feature, or the earliest affected phase of an existing spec. |
| Unclear | Ask a focused question about intended behavior before selecting a lane or creating speculative documents. |
A bugfix can restore an approved contract without changing it. A refactor can preserve it. Neither route bypasses tests, evidence checks, or execution authorization. An explicit request to implement a maintenance fix authorizes that work; approval of a planning document alone does not.
Before closing maintenance, identify the applicable current contract, run existing tests, and refresh the selected affected evidence with walden verify <feature> at the declared checkpoint. Use --all only for a justified forced check. Inspect the CLI outcome; raw test output alone does not refresh evidence. If no spec covers the change, state that limitation without creating a spec merely to obtain a checkbox.
For an existing portfolio, establish applicability within the user's requested scope before proposing adoption or replay:
| Proposed applicability | Review action |
|---|---|
| Current | Retain the required behavior in the selected verification scope. |
| Superseded | Cite the replacing/removing decision and successor; propose retirement, never perform it automatically. |
| Mixed | Identify surviving requirements and their agreed destination before discarding obsolete design/tasks. |
| Unresolved | Ask the specific business/scope question; do not invent conformity. |
Ground proposals in decision sources. Age, missing fingerprints and completed checkboxes do not establish obsolescence. Requirements can survive an outdated implementation plan. A current requirement does not make its historical bootstrap/deployment task a current regression check: inspect the actual proof before proposing replay. If it records one-time delivery work, propose the needed current baseline/regression contract for review, not automatic backfill plus execution merely because the CLI reports a re-prove count. Code describes observed behavior, not authority to rewrite intent; a newer draft does not automatically supersede an approved contract. If sources conflict, ask before retiring or changing the contract. A case-study request yields general findings for the product being improved, not unsolicited operations in the example repository.
For existing specs, use CLI status and validation rather than guessing freshness. For a new spec, use CLI-generated scaffolds as the canonical document templates. Do not reconstruct full templates from memory.
CLI Prerequisite
Requires Walden CLI v0.10.4 or a newer compatible release. Before the first CLI operation, check command -v walden and that executable's version --json. If PATH has no usable compatible CLI, check $HOME/.local/bin/walden too (on Windows: Get-Command walden and %USERPROFILE%\go\bin\walden.exe). Reuse a compatible binary by its verified path or a session-only PATH correction; do not downgrade it or edit persistent shell configuration. An unclear version is not assumed compatible.
If the CLI is missing or incompatible, stop the dependent Walden operation. This guide never installs the CLI: do not run an installer, fetch a script or binary, or write install commands for the agent to execute; installation is the user's action in their own terminal. Determine the platform (uname -s on POSIX shells; PowerShell, $env:OS, MSYS/MINGW mean Windows) and run command -v go (PowerShell: Get-Command go) so the branch below is a lookup, not a question to the user. Then name one path:
goresolves (any platform):go install github.com/andrearaponi/walden/cmd/walden@v0.10.4as a single command block, then make sure$(go env GOPATH)/bin(Windows:%USERPROFILE%\go\bin) is on PATH.godoes not resolve, macOS/Linux: open https://github.com/andrearaponi/walden — the README has the one-line installer and the releases page has the binary. No command block: you do not carry that installer line.godoes not resolve, Windows: downloadwalden-v0.10.4-windows-<arch>.exefrom https://github.com/andrearaponi/walden/releases, rename it towalden.exeand place it on PATH.
If the user then asks you to install anyway, restate once that you do not install and repeat the same single pointer or block — exactly one block per reply, never the other branch, never a fetched script. Do not repeat the refusal a third time; do not fetch anything. Do not substitute manual workflow metadata for the missing CLI.
This guide is distributed through the Skills CLI and
Read the complete source ↗