feat: wire after_specify and after_plan hook events into command templates

[davidniu-0914]

Description

This PR aligns the extension hooks documentation and command templates for the specify and plan commands, resolving Issue #1788. It ensures that all core command templates (specify.md, plan.md, tasks.md,
implement.md) contain consistent CRITICAL execution instructions for mandatory hooks, preventing AI agents from proceeding before hook execution. Additionally, it synchronizes the project version to 0.2.1 across
pyproject.toml and all extension guides to match the upstream repository.

Testing

• Verified markdown template rendering and hook logic consistency across all modified command files.
• Confirmed version consistency in pyproject.toml and documentation.
• Tested locally with uv run specify --help
• Ran existing tests with uv sync && uv run pytest

AI Disclosure

• I did not use AI assistance for this contribution
• I did use AI assistance (describe below)

This PR was prepared with the assistance of Gemini CLI to synchronize version numbers across multiple files, standardize hook instructions in markdown templates for behavioral consistency, and ensure
documentation accuracy relative to the implemented features.

[Copilot]

Pull request overview

This PR updates the Spec Kit command templates and extension documentation so that the lifecycle hook events for before_specify/after_specify and before_plan/after_plan are represented consistently alongside existing hook points, and bumps the project/docs version to 0.2.1.

Changes:

• Add pre- and post- hook instructions for specify and plan command templates (before_* and after_* events).
• Strengthen “mandatory hook” execution instructions across core templates (add explicit CRITICAL “execute immediately” language).
• Bump version to 0.2.1 and update extension guides + changelog accordingly.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
templates/commands/specify.md	Adds before_specify and after_specify hook instructions + CRITICAL execution requirements.
templates/commands/plan.md	Adds before_plan and after_plan hook instructions + CRITICAL execution requirements.
templates/commands/tasks.md	Adds CRITICAL execution requirement wording for mandatory hooks.
templates/commands/implement.md	Adds CRITICAL execution requirement wording for mandatory hooks.
src/specify_cli/extensions.py	Updates docstrings/examples for hook event names to include specify/plan events.
pyproject.toml	Bumps package version to 0.2.1.
extensions/EXTENSION-USER-GUIDE.md	Updates stated minimum/version references and last-updated metadata.
extensions/EXTENSION-DEVELOPMENT-GUIDE.md	Expands documented hook points to include specify/plan + before_implement, updates examples.
extensions/EXTENSION-API-REFERENCE.md	Documents additional standard hook events and adds CRITICAL mandatory-hook instruction.
CHANGELOG.md	Adds an Unreleased entry for the new hook wiring.

Comments suppressed due to low confidence (2)

templates/commands/plan.md:87

• The post-plan hook filtering here will drop hooks that omit enabled (which are enabled by default in HookExecutor) and will skip all hooks that set condition, even though the codebase supports condition evaluation. This makes conditional hooks impossible to trigger from the template-driven workflow.

   - Filter to only hooks where `enabled: true`
   - For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
     - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
     - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
   - For each executable hook, output the following based on its `optional` flag:

templates/commands/specify.md:33

• Hook filtering in the template doesn’t match the actual hook config behavior in HookExecutor: hooks default to enabled when the enabled field is missing (h.get('enabled', True)), so instructing the agent to keep only enabled: true would incorrectly drop hooks without an explicit enabled key. Also, skipping hooks with a non-empty condition means conditional hooks will never run from the template flow even though the codebase supports condition evaluation; consider treating conditions as evaluatable (same rules as HookExecutor.should_execute_hook) or at least not skipping them outright.

- Filter to only hooks where `enabled: true`
- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
  - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mnriem]

Please address Copilot feedback. If not applicable, please explain why

[Copilot]

Pull request overview

This PR updates the Spec Kit command templates and extension documentation to include missing lifecycle hook events (notably after_specify / after_plan, plus corresponding before_* events) and to standardize mandatory-hook execution instructions across core commands.

Changes:

• Add before_specify/after_specify and before_plan/after_plan hook-check instructions to the specify and plan command templates.
• Strengthen “CRITICAL: execute immediately” instructions for mandatory hooks in tasks and implement templates.
• Update extension docs (hook event lists/examples) and add a CHANGELOG entry; bump pyproject.toml version.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
templates/commands/tasks.md	Adds stronger mandatory-hook execution wording for pre/post task hooks.
templates/commands/specify.md	Adds pre- and post- hook checking instructions for before_specify/after_specify.
templates/commands/plan.md	Adds pre- and post- hook checking instructions for before_plan/after_plan.
templates/commands/implement.md	Adds stronger mandatory-hook execution wording for pre/post implement hooks.
src/specify_cli/extensions.py	Updates docstrings to reference additional hook event examples.
pyproject.toml	Bumps the package version.
extensions/EXTENSION-USER-GUIDE.md	Updates stated Spec Kit version and last-updated footer.
extensions/EXTENSION-DEVELOPMENT-GUIDE.md	Expands documented standard hook points and updates hook examples.
extensions/EXTENSION-API-REFERENCE.md	Documents additional hook events and adds “CRITICAL” mandatory-hook instruction.
CHANGELOG.md	Adds an Unreleased entry for the new hook wiring and adjusts indentation of nested bullets.

Comments suppressed due to low confidence (2)

templates/commands/specify.md:220

• This post-hook section instructs the agent to ignore condition entirely and treat all non-disabled hooks as executable candidates. That diverges from HookExecutor.check_hooks_for_event, which filters by should_execute_hook() and will skip hooks when conditions are not met or cannot be evaluated. To avoid executing hooks unexpectedly, this should either (1) mirror HookExecutor behavior for conditions, or (2) explicitly state that conditional hooks must not be auto-executed by the agent.

   - From the discovered hooks, ignore only those where `enabled` is explicitly set to `false`. If `enabled` is omitted, treat the hook as enabled.
   - Do **not** attempt to interpret or evaluate hook `condition` expressions, and do **not** filter hooks based on the presence or contents of `condition`. Condition evaluation is handled by the `HookExecutor.should_execute_hook` implementation.
   - Treat all hooks that are not explicitly disabled (that is, all hooks where `enabled` is not `false`) as executable candidates.
   - For each executable hook, output the following based on its `optional` flag:

templates/commands/plan.md:85

• This post-hook guidance tells the agent not to filter on condition, but HookExecutor’s check_hooks_for_event() does apply condition filtering via should_execute_hook(). Without condition evaluation, the agent can execute hooks that are supposed to be gated off. Recommend updating the template to avoid auto-executing conditional hooks unless their conditions can be evaluated consistently with HookExecutor.

   - From the discovered hooks, ignore only those where `enabled` is explicitly set to `false`. If `enabled` is omitted, treat the hook as enabled.
   - Do **not** attempt to interpret or evaluate hook `condition` expressions, and do **not** filter hooks based on the presence or contents of `condition`. Condition evaluation is handled by the `HookExecutor.should_execute_hook` implementation.
   - Treat all hooks that are not explicitly disabled (that is, all hooks where `enabled` is not `false`) as executable candidates.
   - For each executable hook, output the following based on its `optional` flag:

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mnriem]

Please address additional Copilot feedback.

[Copilot]

Pull request overview

This PR updates Spec Kit’s AI command templates and extension documentation so the full lifecycle hook events (including after_specify and after_plan) are explicitly represented in the templates, and documentation reflects the expanded hook event set and current versioning.

Changes:

• Add before_* / after_* hook handling instructions to specify.md and plan.md, including mandatory “CRITICAL” execution requirements.
• Strengthen mandatory hook execution instructions in tasks.md and implement.md templates for consistency.
• Update extension guides / API reference / changelog and bump pyproject.toml version.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
templates/commands/tasks.md	Adds CRITICAL “execute immediately” language for mandatory hook blocks.
templates/commands/specify.md	Adds pre-/post- hook sections for before_specify and after_specify in the command template.
templates/commands/plan.md	Adds pre-/post- hook sections for before_plan and after_plan in the command template.
templates/commands/implement.md	Adds CRITICAL “execute immediately” language for mandatory hook blocks.
src/specify_cli/extensions.py	Updates docstrings/examples to include the newer hook event names.
pyproject.toml	Bumps project version.
extensions/EXTENSION-USER-GUIDE.md	Updates minimum version guidance and footer metadata.
extensions/EXTENSION-DEVELOPMENT-GUIDE.md	Expands documented lifecycle hook points and updates examples.
extensions/EXTENSION-API-REFERENCE.md	Documents the additional standard hook events and adds CRITICAL execution language.
CHANGELOG.md	Adds an Unreleased entry for the hook-template wiring and fixes list indentation.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mnriem]

Please address Copilot feedback. If not applicable explain why. Please avoid whitespace only changes