ChindanaiNaKub
UserA strategic intent layer for one person building with agents. Markdown intent graph + coherence checker + Claude Code skills.
Categories
Indexed Skills (4)
autopilot
Run an unattended openthought session — pick work from the intent graph with coherence next, build it, gate it, commit it, and keep going until the graph runs dry, escalating questions to the inbox instead of stopping. Use when the user says to keep going, work through the backlog, run on autopilot, ship whatever is next, or leaves you to work without further instructions.
coherence-check
Run the coherence checks over the intent graph and answer the judgment queue — find work standing on abandoned premises, plans that were never decomposed, stories that restate their parent, goals whose measure nothing addresses, and artifacts that are active on paper but dead in practice. Use when the user asks what's stale, what's drifted, what to clean up, whether the plan still holds, or after editing anything under intent/.
intent-graph
Read or write the repo's intent graph under intent/ — the mission, bets, goals, problems, projects and stories that say why this code exists. Use when the user asks what something is for, why a decision was made, or what to work on next; when starting work whose purpose is not obvious from the diff; or when they want to record a decision, plan, problem, or piece of scope. Also use before writing code if no artifact is in focus.
ship-check
Gate a diff against the intent it claims to serve before committing, pushing, or opening a PR — check that changed files trace to an artifact, that the story's acceptance criteria are actually met, and that the change didn't quietly widen beyond what was asked. Use before any commit or PR, when the user asks "is this ready", "does this match what I asked for", or after finishing a chunk of agent-written work.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.