@elementarno/eawf 0.5.2

package/skills/wave-spec/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: wave-spec
+description: Scaffold or validate a WaveSpec deliverable for a claimed wave.
+argument-hint: "init|validate <wave-id> [--mockup-waiver-reason=<text>]"
+user-invocable: true
+disable-model-invocation: true
+---
+
+# /wave-spec
+
+## Canonical algorithm
+
+1. Resolve the verb (`init` default / `validate`) and the target `wave_id` (required; a missing id degrades to `status=needs_user`).
+2. Thread the optional `mockup_waiver_reason` through so a downstream scaffold can carry it onto the WaveSpec without forcing an ASCII mockup for non-UI waves.
+3. Append a single append-only `EVENT` describing the operation intent; the daemon owns spec scaffolding + cache mutation, so the skill routes to the `eawf spec` writer via `next_valid_actions`.
+
+## Pre-flight checklist
+
+- [ ] The wave exists before `init` / `validate`.
+- [ ] A Mockup-waiver reason is supplied for non-UI waves that skip the ASCII mockup.
+
+## Decision surfaces
+
+A missing `wave_id` degrades to `status=needs_user`, which routes the operator to an `AskUserQuestion` prompt for the target wave rather than scaffolding against an unresolved id.
+
+## Output contract
+
+Skill envelope with `header.skill = "/wave-spec"`. Body carries verb, wave_id, and mockup_waiver_reason.

package/skills/write-adr/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: write-adr
+description: Model-only playbook for drafting an architecture decision record companion to a typed decision row.
+argument-hint: ""
+user-invocable: false
+disable-model-invocation: false
+---
+
+# write-adr
+
+A model-only playbook for drafting an architecture decision record. There is no slash command; the model invokes this when a design choice needs a durable, reviewable rationale. In an Eä-managed repo the decision itself is a typed row in `state.json` — the ADR markdown is the human-readable companion, never the source of truth.
+
+## When to reach for it
+
+- Two or more designs were weighed and one was picked.
+- The choice constrains future work (a dependency, a schema shape, a protocol boundary) and a later reader will ask "why this?".
+- An audit or spike produced a verdict that should outlive the session.
+
+## Canonical structure
+
+1. **Context** — the forces in tension, in two or three sentences. State the constraint, not the solution.
+2. **Options** — each candidate as a bullet with its concrete trade-off. Name the option the way the codebase will refer to it.
+3. **Decision** — the chosen option, stated as a present-tense assertion.
+4. **Consequences** — what becomes easy, what becomes hard, what is now forbidden.
+
+## Guardrails
+
+- Reference the audit or spike that justifies the decision so the evidence chain is reconstructible (research-workflow rule).
+- Keep prose scrub-clean: no machine paths, hostnames, or PII; references stay repo-relative, an external URL, or an Eä URN.
+- The ADR records WHY; provenance ids from audits and review discussions live in the decision row and the commit body, not in source comments (rule 25).