openspec-new-change

Initialize feature or fix directories using artifact-driven workflows and openspec CLI.

6|Updated May 25, 2026
One-click install
npx skills add https://github.com/zhentingWu-wzt/wgenty-code --skill openspec-new-change-zhentingwu-wzt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/zhentingWu-wzt/wgenty-code/tree/main/.wgenty-code/skills/openspec-new-change
Command: npx skills add https://github.com/zhentingWu-wzt/wgenty-code --skill openspec-new-change-zhentingwu-wzt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the ambiguity and manual setup overhead associated with starting new development tasks by enforcing a standardized, artifact-driven workflow.

Core Features & Use Cases

  • Structured Scaffolding: Automatically creates a consistent directory structure for new features or fixes.
  • Workflow Integration: Supports custom schema-based development, ensuring that every change follows the required project lifecycle.
  • Use Case: When starting a new feature, use this skill to initialize the change directory, verify the status of required artifacts, and retrieve the exact templates needed to begin development.

Quick Start

Ask the agent to start a new change for the user authentication feature to initialize the project structure and retrieve the first artifact instructions.

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 feature directory with a standardized development workflow?

To scaffold a new feature directory with a standardized development workflow, initialize a new change using an artifact-driven process that automatically creates the required structure and retrieves template instructions.

What is an artifact-driven workflow for starting new development changes?

An artifact-driven workflow for new development changes enforces a standardized project schema, guiding you step-by-step to generate required artifacts and verify change lifecycle status.

How do I create standardized project schemas for new code changes?

You create standardized project schemas by initializing a feature or fix directory, which validates development paths and provides guided instructions for artifact generation.

Do I need the openspec CLI to manage change lifecycles and validate schemas?

Yes, you need the openspec CLI to manage change lifecycles and validate schema-based development paths when initializing new development tasks.

Can I use this scaffolding workflow for both new features and bug fixes?

Yes, you can use this scaffolding workflow for both new features and bug fixes, as it creates a consistent directory structure and verifies required artifacts for any development change.

What are the limitations of automating development task scaffolding with custom schemas?

The limitation of automating development task scaffolding is that it requires strict adherence to custom schema-based development paths and depends on the openspec CLI to validate the change lifecycle.