DustinVK
UserThe why behind your code, as plain markdown in your repo. Agent skill to capture decisions, dashboard to browse them.
Categories
Indexed Skills (4)
ask
Answer questions about past technical discussions, user stories, and why things were implemented a certain way by searching the team's wherefore log. Use this whenever the user asks why a feature was built the way it was, what was decided about a particular user story, topic, or component, or wants to recall an earlier conversation -- e.g. "why did we...", "what did we decide about...", "is there anything in the log about...", "how were we planning to implement...". Trigger even when the user doesn't name the wherefore explicitly but is clearly asking about a prior decision or its rationale. If nothing relevant is found, say so plainly rather than guessing.
capture
Capture a technical discussion or meeting summary into the team's wherefore log. Use whenever the user wants to log, record, save, or archive the outcome of a discussion, Slack huddle, design conversation, standup, or meeting, including when they paste a raw or AI-generated summary and say things like "log this", "add this to the discussion log", "record this discussion", "save this for later". Trigger even if the user only pastes a chunk of conversation and asks to capture the important parts; this skill distills it rather than storing it verbatim.
resolve
Mark an open question in the team's wherefore log as resolved. Use whenever the user wants to close out an open question, e.g. "mark Q-042 resolved", "we figured out Q-007", "close Q-015", "we have an answer for Q-003". Works both when resolution comes from a new wherefore entry and when it's a standalone answer with no new entry.
supersede
Mark a past decision in the wherefore log as superseded or obsolete. Use whenever the user explicitly wants to retire an existing entry without capturing a new discussion -- e.g. "mark 2026-01-15-graphql-caching obsolete", "supersede the RLS entry with the schema-per-tenant one", "we dropped GraphQL, mark that decision dead". Does NOT capture a new discussion; that belongs to the capture skill.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.