openspec-ff-change

To generate all OpenSpec change artifacts in one run, provide a change name or description to the skill. It scaffolds the change and creates required artifacts in dependency order until apply-ready items are complete.

Automating OpenSpec CLI artifact scaffolding is best handled by parsing openspec status and instructions JSON to determine readiness. This removes repetitive CLI orchestration overhead by producing tasks, specs, and implementation scaffolding automatically.

Yes, creating apply-ready change artifacts requires the OpenSpec CLI. The workflow depends on parsing JSON output from openspec status and openspec instructions, alongside file read/write access to the openspec/changes/<name> directory.

Yes, you can use this automated change-management workflow for new feature onboarding. It accelerates the process by generating tasks, specs, and implementation scaffolding in a single run without manual step-through.

Artifact generation prompts for clarification during OpenSpec workflows to avoid incorrect artifact creation. When input is unclear, the skill interactively requests more information to ensure accurate dependency parsing and scaffolding.

Dependency handling for OpenSpec artifacts works by parsing openspec status and instructions JSON. This determines artifact readiness and generates subsequent items in the correct dependency order until all apply-required artifacts are produced.