specsmith

Git mechanics for any code demand — branch creation off develop, conventional commits, CI/tests, push, and a PR that pauses for approval. Use ALWAYS when starting a feature/fix/chore, creating a branch, committing, opening a PR, or when the spec-driven flow (prompt-grill) reaches the kickoff, checkpoint, or close phases. Single source of git mechanics; never reimplement branch/commit/PR outside it.

Scaffolds the Specsmith specs/ structure into the current project — copies the specs/ README and the spec/plan/tasks templates from the installed plugin into the project root so prompt-grill and the spec-driven flow have a local home. Use when the user installs Specsmith and wants the specs/ scaffold in their project, says "init specsmith", "set up specs", "add the spec template", or before starting the spec-driven flow in a project that has no specs/ folder yet.

Interrogates the user about a vague plan, feature, or prompt until reaching complete understanding, resolving every branch of the decision tree before any implementation. Use ALWAYS when the user requests a new feature, describes an ambiguous task, says "grill me", "interview me", "refine this prompt", or when a request has more than one possible interpretation — even if they don't ask for it explicitly.