openspec-new-change

OpenSpec change scaffolding creates a structured directory for your software modification using a default schema. It establishes the correct workflow structure and presents the first artifact template to guide your planning process.

Start planning by describing the feature, fix, or modification you need. The workflow scaffolds the change, applies artifact sequencing, and provides status-driven guidance to show exactly what planning step to do next.

Yes, you need access to the openspec CLI to create a new change scaffold. The Skill relies on the CLI to generate the directory structure, apply schema selection, and manage the artifact sequencing required for your planning workflow.

Yes, you can use a custom schema when scaffolding an OpenSpec change. The workflow uses the default schema automatically unless you explicitly request a different one during the change creation process.

The best way to manage artifact sequencing is using a status-driven scaffolding workflow. It creates the change directory, tracks the current status, and presents the first ready artifact so you know exactly what to build next.

Your OpenSpec change requires a kebab-case name to ensure consistent directory naming and workflow structure. If you provide a clear build description instead, the system can still scaffold the change correctly.