openspec-new-change

Scaffold new OpenSpec changes with an artifact-driven workflow.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/MaplumeX/Blockwise --skill openspec-new-change-maplumex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/MaplumeX/Blockwise/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/MaplumeX/Blockwise --skill openspec-new-change-maplumex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec change initialization can be tedious without a repeatable, guided process. This skill provides a structured, artifact-driven workflow to scaffold a new change without creating artifacts prematurely.

Core Features & Use Cases

  • Guided change creation: initiates a new OpenSpec change scaffold with a default or requested workflow.
  • Workflow-driven artifacts: presents statuses and step-by-step instructions without committing artifacts.
  • Guardrails and prompts: ensures user input is clarified before proceeding.

Quick Start

Describe the desired change in kebab-case name, and I will guide you through scaffolding a new OpenSpec change without creating artifacts yet.

Frequently Asked Questions about openspec-new-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new OpenSpec change without committing artifacts prematurely?

You can scaffold an OpenSpec change without committing artifacts by providing a kebab-case name, which triggers a guided workflow for naming and schema selection while enforcing guardrails against premature artifact creation.

What is an artifact-driven workflow for OpenSpec change management?

An artifact-driven workflow for OpenSpec change management is a structured scaffolding process that guides users through naming and schema selection while enforcing guardrails that prevent premature artifact creation.

How do I select a schema when creating a new OpenSpec change?

You select a schema during OpenSpec change creation through optional user prompts provided by the guided workflow, which clarifies your input to ensure the correct schema is chosen before scaffolding proceeds.

Does the OpenSpec change scaffolding workflow support custom naming conventions?

Yes, the OpenSpec change scaffolding workflow supports custom naming by requiring you to describe the desired change using a kebab-case name, which initializes the guided scaffolding process.

Why does my OpenSpec change scaffold stop before creating files?

Your OpenSpec change scaffold stops before creating files because the workflow enforces strict guardrails that prevent artifact creation until you explicitly provide direction to commit them.

Can I use this guided workflow for both features and fixes in OpenSpec projects?

Yes, you can use this guided workflow for both features and fixes in OpenSpec projects, as the scaffolding process applies to teams creating either type of change while enforcing the same artifact creation guardrails.