openspec-ff-change

OpenSpec artifact generation can be fast-forwarded for a single change by automatically scaffolding tasks and plans from instruction templates until all required artifacts reach done status. This eliminates manual step-by-step work by processing all implementation-ready outputs in one go.

Dependency order handling queries the OpenSpec CLI status JSON to determine applyRequires and artifact dependencies. It then generates each artifact sequentially from instruction templates, ensuring prerequisite dependency artifacts are read for context before downstream artifacts are created.

Yes, change-first scaffolding creates an OpenSpec change directory directly from a user-provided change name or a description-derived kebab-case name. This allows you to quickly initialize the required directory structure for feature work or bug fixes.

Automating OpenSpec task and plan creation is best handled by fast-forwarding the artifact creation workflow. By querying the CLI for the correct build order and applying schema-provided templates, you can generate all implementation-ready artifacts without manual intervention.

Yes, the OpenSpec CLI is required because the workflow uses its status JSON output to determine applyRequires and artifact dependencies. This status data is essential for correctly ordering and generating each artifact until the apply-ready state is achieved.

Manual OpenSpec artifact generation slows down implementation planning because it requires creating tasks, plans, and other artifacts individually. Fast-forwarding this workflow queries the correct build order and generates all required artifacts automatically, bypassing the step-by-step bottleneck.