Extension Hooks output tainting interaction

[youngjoel]

The skills sometimes output extension hooks output that is confusing and distracting. For example from clarify:

## Extension Hooks

**Optional Pre-Hook**: git  
Command: `/speckit-git-commit`  
Description: Auto-commit before spec clarification

Prompt: Commit outstanding changes before clarification?  
To execute: `/speckit-git-commit`

What unfinished-draft management experience should the initial release require for resumed matches?

**Recommended:** Option A - A dedicated drafts list is the safest and most testable behavior because it makes draft discovery, resumption, and explicit finalization visible across sessions without relying on implicit resume rules.

Confusing because there is no markdown delimiter between the extension hooks and the question context that begins at "What unfinished-draft".

Distracting because it is completely not clear what I should do with the pre-hook information ... and after the first time telling me about it, maybe it isn't necessary keep mentioning it?

[mnriem]

Thanks for the detailed report, @youngjoel — and you're right on both counts. This is a real rough edge in how the templates emit optional extension hooks, not something you're doing wrong.

Here's what's happening under the hood:

• The clarify command runs a "Pre-Execution Checks" step that reads .specify/extensions.yml and, for each optional hook registered under before_clarify, prints that ## Extension Hooks block. You've got the git extension installed with an optional pre-commit hook, which is why you see the /speckit-git-commit prompt.
• The missing delimiter: the template prints the hook block and then goes straight into the clarification question with nothing separating them — so "To execute: /speckit-git-commit" and "What unfinished-draft management..." run together. There's no separator emitted between the hook output and the actual question, which is exactly why it reads as confusing.
• The repetition: the hook check runs on every invocation, so the same optional-hook reminder gets re-emitted each time with no "you've already seen this" suppression.

A couple of things that should help right now:

• The git pre-hook is optional — you can ignore the prompt entirely and just answer the clarification question; it won't block anything. To run it you'd type /speckit-git-commit.
• If you'd rather not see the reminders at all, open .specify/extensions.yml and set enabled: false on the before_clarify hook (or remove it). The template skips any hook explicitly marked enabled: false.

Does disabling that hook get you what you need, or is the bigger pain the way the hook text blends into the question? Knowing which matters more to you helps me point you in the right direction.