The why behind your code, as plain markdown in your repo. Agent skill to capture decisions, dashboard to browse them.
Skill Claude CodeCodex
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…
Skill Claude CodeCodex
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…
Skill Claude CodeCodex
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…
Skill Claude CodeCodex
Operate the wherefore plan collection: the forward-looking work items in wherefore/plan/. Use whenever the user wants to open a new plan item, move one along (todo to doing to done), drop one, or see what is in flight, e.g. "add a plan item for X", "open a plan item to migrate auth", "start on P-011", "mark P-012…
Skill Claude CodeCodex
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…