speckit-plan

To generate design artifacts from a plan template, execute the structured implementation planning workflow which outputs research.md, data-model.md, contracts/, and quickstart.md using your project context and plan template.

The implementation planning workflow requires a .specify directory containing a memory/constitution.md file, a FEATURE_SPEC, and an IMPL_PLAN template to function correctly and generate artifacts.

Yes, you can run custom hooks before and after generating design artifacts by defining them in the .specify/extensions.yml file, specifying whether each hook is automatic or optional during the planning workflow.

The planning workflow ensures artifact alignment by re-evaluating constitution checks from the .specify/memory/constitution.md file and updating the agent context to reference the created IMPL_PLAN after generation.

The best way to automate implementation planning for data models and contracts is to use a structured workflow that loads a plan template to automatically produce artifacts like data-model.md and contracts/ directories.

No, this workflow generation does not work without a pre-existing .specify directory, as it specifically requires the .specify folder structure to load the constitution, extensions, and plan templates needed for artifact generation.