skills.rest
DihDyyy
DihDyyyCOMMUNITY
Explore all skills by this author →
GitHub

openspec-new-change

Start a new OpenSpec change with a structured, artifact-driven workflow.

Updated Feb 3, 2026
Search Tags:#software development#change management#OpenSpec#artifact-driven#structured workflow
One-click install
npx skills add https://github.com/DihDyyy/login_app --skill openspec-new-change-dihdyyy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/DihDyyy/login_app/tree/main/.amazonq/skills/openspec-new-change
Command: npx skills add https://github.com/DihDyyy/login_app --skill openspec-new-change-dihdyyy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

This Skill helps users quickly start a new OpenSpec change by guiding them through a structured, step-by-step process, making it easier to create features, fixes, or modifications.

Core Features & Use Cases

  • Structured Workflow: Guides users through the process of creating a new change with a clear set of steps.
  • Artifact-Driven Approach: Users can create changes using an artifact-driven workflow, making it easier to manage and track progress.
  • Custom Workflows: Supports custom workflows if needed, allowing users to tailor the process to their specific needs.

Quick Start

Use the openspec-new-change skill to create a new change named 'add-user-auth'.

Frequently Asked Questions about openspec-new-change

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

FAQPage Schema
How do I start a new OpenSpec change for a software modification?▼

To start an OpenSpec change, you provide a user-defined change name to initiate a structured workflow. This guides you step-by-step through creating the necessary artifacts for your software modification.

What is an artifact-driven workflow in change management?▼

An artifact-driven workflow manages software changes by generating and tracking specific artifacts throughout the process. This approach makes it easier to structure, manage, and track progress for new features or fixes.

Can I use a custom schema when creating an OpenSpec change?▼

Yes, you can use optional custom schemas to tailor the OpenSpec change creation process. This supports custom workflows, allowing you to adapt the structured steps to your specific software development needs.

Do I need the OpenSpec CLI to initiate a structured change workflow?▼

Yes, the OpenSpec CLI is required to initiate this structured change workflow. The Skill depends on the OpenSpec CLI to guide you through the step-by-step artifact-driven creation process.

What is the best way to track progress for new software features using OpenSpec?▼

The best way to track progress is using an artifact-driven approach within a structured workflow. By generating specific artifacts during change creation, you can easily manage and monitor the development progress of new features.

Related Skills

Explore More Software Engineering Skills→
kuchida1981kuchida1981

openspec-continue-change

Create the next required OpenSpec artifact after checking change status and dependencies.

Community
Advanced
mrkhachaturovmrkhachaturov

receiving-code-review

Verify code-review feedback against the codebase before implementing changes.

Community
Advanced
zthxxxzthxxx

openspec-new-change

Initialize OpenSpec change scaffolds and monitor artifact status.

Community
Basic
AuroraWebSoftwareAuroraWebSoftware
41

openspec-new-change

Create a new change directory in the OpenSpec framework.

Official
Intermediate