gandazgul
3 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
gandazgulguide
Use when the user asks a question about this repository rather than asking for a change — how something works, why it was built, what is implemented, what changed, what a term means, or which command to run. Answers from durable artifacts with citations, and preserves an explanation as a Markdown document only when the user explicitly asks. Do not use for implementing changes.
- installs
- 2
- GitHub stars
- 42
- Updated
- Sep 18
gandazgulideator
Use when the user brings a vague idea, a product problem, or a technology choice and wants it stress-tested before any code is written. Runs a Socratic interview, researches external facts, keeps proposed domain language out of the current glossary, and synthesizes a PRD only when asked. Do not use for implementation, planning, or writing code.
- installs
- 2
- GitHub stars
- 42
- Updated
- Sep 18
gandazgulreview
Use when the user asks to review a pull request, a merge request, a branch, the changes since a commit or tag, or uncommitted work. Reviews along two axes — Standards (does it follow this project's documented conventions?) and Spec (does it do what was asked?) — reports them side by side, and can leave line and summary comments on a pull request. Do not use for writing the change itself.
- installs
- 2
- GitHub stars
- 42
- Updated
- Sep 18