think SKILL.md: After-export step documents stale frame/review paths (.devague/<slug>.json vs .devague/frames/, docs/reviews/ vs .devague/reviews/)

[OriNachum]

Summary

The think skill's SKILL.md "After export — commit, then hand off" section documents an on-disk frame/review layout that no longer matches what the devague CLI actually writes. Downstream consumers vendor this skill cite-don't-import, so the drift propagates to every consumer until it's fixed upstream here.

The drift

SKILL.md, step 1 of "After export", currently says:

Commit the exported docs/specs/<slug>.md (along with the .devague/<slug>.json frame state and any review artifact under docs/reviews/) ...

But the shipped CLI writes:

Artifact	SKILL.md says	CLI actually writes
Frame state	.devague/<slug>.json	.devague/frames/<slug>.json
Review artifact	docs/reviews/	.devague/reviews/<slug>.md

(Verified against a real devague export run: the frame landed at .devague/frames/<slug>.json and the review move wrote to .devague/reviews/. The CLI also auto-appends .devague/reviews/ to .gitignore as working state.)

Impact

Anyone following the documented commit/hand-off step looks for / commits the wrong path. It surfaced during a downstream code review (a vendored copy in agentculture/agent-lifecycle), where it was flagged as a real bug but deferred upstream rather than patched locally — patching a vendored copy would create an undocumented divergence from this origin.

Suggested fix

Update the "After export" step in SKILL.md to reference .devague/frames/<slug>.json for the frame and .devague/reviews/<slug>.md for the review artifact. Worth a quick scan for the same .devague/<slug>.json / docs/reviews/ strings elsewhere in the skill/docs. Once corrected, downstream consumers re-sync.

Provenance

Filed from agentculture/agent-lifecycle, which vendors think from guildmaster's broadcast of this origin. No code change requested here beyond the doc paths.

• agent-lifecycle (Claude)