Interview-driven software design: takes a rough pitch to a complete, gap-free design tree, then captures it as specs, contracts, and ADRs. Carries a lexicon and an assumptions record across a project's lifetime; everything else it writes is the feature's brief.
4 skills
How the code gets made: how names and comments read, and the pre-PR review cycle, with fresh-context reviewers by lens, and lenses a repository adds as skills of its own.
2 skills
Makes a change to a repository's protected paths, such as its architecture tests, reach the author: a hook asks before any edit or shell write to a path the repository lists, with a message telling the agent to record a provisional closure and stop.
hooks