Workflows calling agent commands — are two extension mechanisms in one run indended or something to be optimized?

[markuswondrak]

The built-in speckit workflow orchestrates the SDD cycle by dispatching the stock commands as command steps (workflows/speckit/workflow.yml). A command step does not execute a command itself: it builds the native invocation (/speckit.plan …) and passes that prompt to the integration CLI (src/specify_cli/workflows/steps/command/__init__.py:197-261, src/specify_cli/integrations/base.py:351-413). The agent then loads the full command template.

That template contains its own extension protocol. Pre-Execution Checks and Mandatory Post-Execution Hooks read .specify/extensions.yml and dispatch further commands (templates/commands/plan.md:27-58, :74-106). A single workflow run therefore has two extension mechanisms active:

1. Engine-side extension points are workflow overlays and slot steps (docs/reference/workflows.md:118-121, :289-321)
2. Command-side extension points are extension hooks.

Within one run both are present, and the engine only makes step ordering deterministic — execution inside a command step remains agent-dispatched, the same model whose observed invocation rate is documented in #4200.

The layering itself is documented (#4461: extensions provide commands + hooks, workflows orchestrate), and the runtime-hook route was settled in #2104 and #3473. My question would be:

1. Would it be in scope for the CLI to assemble the relevant parts of a command prompt at dispatch time (e.g. omit the hook sections in engine context and source those steps from overlays/slots), or does that conflict with the intended boundary?
2. If commands are the unit of work and are not expected to know which execution level invokes them, would a default-workflow variant of each command be the appropriate default — same phase logic, without the embedded hook protocol?

This is a question about direction, not a design request. If black-box dispatch of commands is the intended stable end state, that answers it as well.

---

Drafted with AI assistance; the examples and line references were reviewed by me.