Stats
Actions
Tags
From groundwork
Session end ritual — update working agreement and create session checkpoint commit
How this skill is triggered — by the user, by Claude, or both
Slash command
/groundwork:check-inThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Session check-in. We are wrapping up.
Session check-in. We are wrapping up.
~/.claude/groundwork-intent exists, read it. Sessions may have shifted through
multiple modes — evaluate whether the work landed somewhere useful overall, not whether
we stayed in one mode.
done: criteria exist, compare against what was actually accomplished:
--open in the session commit
and add them to Open Friction Points in WORKING_AGREEMENT.md.--open; don't manufacture
progress. The intent file is cleared at the next session start regardless.done: criteria (e.g. intent was re-declared mid-session without them),
ask one question: "Did the session accomplish what you set out to do?" and proceed.[x] — include a short resolution note after →## Domain section
in CLAUDE.md. If AGENTS.md has a matching domain section, keep it aligned.
Keep updates concise — only what changes behavior.Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub vohaha/groundwork --plugin groundwork