Stats
Actions
Tags
From ideaspaces
Propose a coherence check on the space after a significant commit, or when direction drifts — milestone completes, focus shifted, Now stale, or tree structure outgrown. Offered as a readiness check (both sides decide whether to reflect now). Triggers at natural breaks or after state updates, not mid-task.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ideaspaces:is-reflectThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Full protocol: read `${CLAUDE_PLUGIN_ROOT}/reference/awareness.md` and `${CLAUDE_PLUGIN_ROOT}/reference/guide.md`.
Full protocol: read ${CLAUDE_PLUGIN_ROOT}/reference/awareness.md and ${CLAUDE_PLUGIN_ROOT}/reference/guide.md.
Reflection is the trigger; recalibration is what it runs. Offered as a readiness check — both sides decide whether to reflect now or defer.
If is_write isn't in your palette when an update is agreed, load it with ToolSearch (select:mcp__plugin_ideaspaces_core__is_write).
After a significant commit. State just updated — propose a coherence check. "We just committed the repo lifecycle and thread vocabulary. Want to check the space still feels coherent now that state updated?" Both sides agree whether to reflect now or defer. Offered, not imposed. Skip for tiny commits (typo fixes, formatting, minor edits).
Now completed. "We shipped agent shared access. The Now's first bullet is done. Update?"
Focus shifted. "Now says billing, but we've been on skill packages for two sessions. Has the focus moved?"
Now stale. No activity toward it in several sessions. "Still the right target?"
Purpose drifted. Rare — surface the observation, let the user decide. Don't challenge lightly.
Structure outgrown. Tree doesn't match content. Branch README describes something that's no longer what's there.
Read current state first — Read _agent/purpose.md and _agent/now.md. If either doesn't exist yet, that's the first reflection: the contract names them, so absence means direction hasn't been captured. Surface it and propose capturing the missing file before reflecting on what's there. Glob recent activity if needed.
Be specific: "The Now says 'build skill packages.' We've defined three. Update the bullets?" Not "should we update Now?"
Propose the update. Let the user confirm. Write with is_write.
| Signal | Update |
|---|---|
| Target completed | Now — new target or remove done bullets |
| Focus shifted | Now — rewrite to match actual work |
| Understanding deepened | Purpose — sharpen (user must own this) |
| Structure outgrown | Directories, READMEs |
Mid-task. Every session. When the user is in a hurry. Natural breaks only.
If Purpose needs a major rethink, that's /is-setup territory — re-elicit, don't patch.
npx claudepluginhub ideaspaces-xyz/claude-code-plugin --plugin ideaspacesCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.