specky

Generate or update functional documentation for a domain/module of the current codebase, keeping specs/MODULES.md and specs/GLOSSARY.md in sync. Use when asked to document a domain, module, feature, or write/update specs.

Answer questions about how this project behaves from its specky docs and git history, before reading source code. Use when the user asks what a feature does, how a flow or workflow works, what its rules, statuses, limits or edge cases are, whether something is supported, or why something changed. For example "how do refunds work?", "what happens when a payment fails?", "do we support X?", "why did we change Y?". Not for finding where a function, class or file is defined.

Before using a piece of this project's functionality, find out what it is meant to do. Use when about to call, depend on, extend or integrate with a feature, endpoint, command or module and asking for its intended use, inputs and outputs, guarantees or limits — "before I call X, what is it meant to do?", "what are the rules for X?", "is X allowed to do Y?". Answers from the repo's specky docs with citations, without reading source. Not for broad "how does X work?" or "why did it change?" questions (use explore-docs), and not for finding where code lives.

Build and open the specky HTML doc viewer, with its Spec Assistant chat, for the current repo. Use when asked to launch, open, start, preview or browse the specky viewer, site or docs, or to run specky serve.

Set specky up in the current repo, so every commit gets documented and the docs become searchable. Checks the specky CLI is installed, chooses and configures an AI provider (specky init), picks the model specky's skills run on, installs the git hooks, and builds the first index. Use when asked to set up, install, configure, enable or get started with specky in a repo, or when specky reports it has no config (specky.toml) here.