Revise

Revise

Persist durable lessons from the current work into the asobi graph. /asobi end records where we are (session status); /revise records what should change future behavior.

When to use

After a meaningful discovery — a workflow worth repeating, a non-obvious project fact, or (most importantly) a dead end an agent should not re-walk. Capture while context is fresh. Not for ordinary task status; that is /asobi end.

Classify

Read the user's free-form text and classify it yourself; ask only if it is too vague to preserve. Keep each lesson short and actionable — "do X because Y", not a transcript.

Class	Means	Destination
work-experience	how work was actually done	[project] observation
finding	a non-obvious fact or gotcha (an architectural choice → a decision entity, see /asobi recall)	[project] observation
wrong-approach	something tried and rejected	[project]:pitfall:<slug> entity

Flow

1. Detect asobi: command -v asobi. If absent, use the fallback files below.
2. Derive [project] (repo basename). Use shared XDG state unless ./asobi.toml exists; never run asobi init --local.
3. Dedup first: asobi search "<topic>" --limit 10. If a matching entity exists, append seen-again YYYY-MM-DD: <evidence> rather than creating a duplicate.
4. Write — ensure the project entity exists (asobi new "[project]" "project"), then:

   asobi obs "[project]" "experience YYYY-MM-DD: <lesson>"   # work-experience
   asobi obs "[project]" "finding YYYY-MM-DD: <lesson>"      # finding
   

   For a wrong-approach, write the pitfall entity below.
5. Confirm in one line.

Pitfall entity

A pitfall warns future agents away from a rejected path — it is not an ADR (ADRs explain chosen paths). One entity per dead end; status and title are truths so /asobi start can surface active pitfalls cheaply.

asobi new "[project]:pitfall:<slug>" "concept"
asobi truth "[project]:pitfall:<slug>" status active        # active | resolved
asobi truth "[project]:pitfall:<slug>" title "<short warning>"
asobi obs "[project]:pitfall:<slug>" "tried: <approach attempted>"
asobi obs "[project]:pitfall:<slug>" "why-it-failed: <root cause / symptom>"
asobi obs "[project]:pitfall:<slug>" "do-instead: <better path, or 'open'>"
asobi obs "[project]:pitfall:<slug>" "date: YYYY-MM-DD"

When the dead end is obsolete: upsert status resolved and append obs "resolved YYYY-MM-DD: <why it no longer applies>". If the lesson belongs to an active task, link it so dispatch surfaces it — asobi link "[project]:[epic]:task-N" "[project]:pitfall:<slug>" "depends_on" (the task depends on knowing the warning). Slugs are lowercase, - inside a segment and : only between levels — e.g. harus-skills:pitfall:bump-tool-overreach.

Recall

/revise only writes; recall lives in asobi. /asobi start reports active pitfalls, and /asobi tasks dispatch queries task-relevant lessons and includes linked pitfalls. Prefer pitfall titles that read as warnings in a dispatch brief.

Fallback (asobi unavailable)

A /revise-only fallback — it does not relax asobi's requirement for session continuity. Append to repo-tracked files, creating each as needed with the header > Project-local fallback lessons captured when asobi was unavailable. Migrate into asobi when possible.

• docs/lessons/pitfalls.md — ## YYYY-MM-DD — <slug>, then Status / Tried / Why it failed / Do instead
• docs/lessons/learnings.md — ## YYYY-MM-DD — <title>, then Type (work-experience|finding) / Lesson

Confirmation

End with one terse line:

Revision saved: <class> -> <destination>.            # or: -> docs/lessons/<file>.md (asobi unavailable)