跳到正文
cccskills
免费在 GitHub 公开

openspec-new-change

Set up a new OpenSpec change for a feature, fix, or modification. Create its working directory, show the document sequence and current status, and present the first template so drafting can begin.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

查看安装方法

适用场景

  • Start a new feature change in OpenSpec
  • Set up a change for a bug fix
  • Start a change with a chosen workflow
  • Review the first template before drafting

包含的文件(1)

  • SKILL.md2.8 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Start a new change using the experimental artifact-driven approach.

Input: The user's request should include a change name (kebab-case) OR a description of what they want to build.

Steps

  1. If no clear input provided, ask what they want to build

    Use the AskUserQuestion tool (open-ended, no preset options) to ask:

    "What change do you want to work on? Describe what you want to build or fix."

    From their description, derive a kebab-case name (e.g., "add user authentication" → add-user-auth).

    IMPORTANT: Do NOT proceed without understanding what the user wants to build.

  2. Determine the workflow schema

    Use the default schema (omit --schema) unless the user explicitly requests a different workflow.

    Use a different schema only if the user mentions:

    • A specific schema name → use --schema <name>
    • "show workflows" or "what workflows" → run openspec schemas --json and let them choose

    Otherwise: Omit --schema to use the default.

  3. Create the change directory

    openspec new change "<name>"
    

    Add --schema <name> only if the user requested a specific workflow. This creates a scaffolded change at openspec/changes/<name>/ with the selected schema.

  4. Show the artifact status

    openspec status --change "<name>"
    

    This shows which artifacts need to be created and which are ready (dependencies satisfied).

  5. Get instructions for the first artifact The first artifact depends on the schema (e.g., proposal for spec-driven). Check the status output to find the first artifact with status "ready".

    openspec instructions <first-artifact-id> --change "<name>"
    

    This outputs the template and context for creating the first artifact.

  6. STOP and wait for user direction

Output

After completing the steps, summarize:

  • Change name and location
  • Schema/workflow being used and its artifact sequence
  • Current status (0/N artifacts complete)
  • The template for the first artifact
  • Prompt: "Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue."

Guardrails

  • Do NOT create any artifacts yet - just show the instructions
  • Do NOT advance beyond showing the first artifact template
  • If the name is invalid (not kebab-case), ask for a valid name
  • If a change with that name already exists, suggest continuing that change instead
  • Pass --schema if using a non-default workflow

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Implement pending tasks from an OpenSpec change, a planned set of development work. The skill reads relevant specifications and design files, makes focused code changes, and updates task completion as work progresses.

中文简介正在准备中。当前显示英语简介。

  • Start implementing a planned change
  • Resume partially completed implementation
  • Work through pending tasks and track progress
alibaba/druid2.8万2026年8月1日 更新

Archive an OpenSpec change after checking its documents, task completion, and specification differences. The skill offers a choice about updating the main specifications, then moves the change into a dated archive and reports the result.

中文简介正在准备中。当前显示英语简介。

  • Archive an implemented change
  • Check unfinished documents and tasks before archiving
  • Review specification differences before updating the main specifications
alibaba/druid2.8万2026年8月1日 更新

Archive several OpenSpec changes together after reviewing their documents, task completion, and specification conflicts. The agent checks actual code to decide which specification updates to apply, asks for confirmation, and reports successes, skipped changes, and failures.

中文简介正在准备中。当前显示英语简介。

  • Archiving several completed changes together
  • Reviewing incomplete documents and tasks before archiving
  • Resolving overlapping specifications using implementation evidence
alibaba/druid2.8万2026年8月1日 更新

Continue an existing OpenSpec change by creating one next document. Check progress and dependencies, follow the workflow's template, and report what was completed and which documents are now available to create.

中文简介正在准备中。当前显示英语简介。

  • Resume documentation for an existing change
  • Create and review one document at a time
  • Draft specifications or design from earlier documents
alibaba/druid2.8万2026年8月1日 更新

Explore development ideas and problems through conversation, code investigation, diagrams, and comparisons. The skill helps clarify requirements, weigh approaches, and surface risks before or during a change, with optional documentation of decisions when requested.

中文简介正在准备中。当前显示英语简介。

  • Clarify a vague feature idea and its requirements
  • Investigate existing code to understand a problem
  • Compare technical approaches and their tradeoffs
alibaba/druid2.8万2026年8月1日 更新

Create the OpenSpec documents needed to begin implementing a feature or fix. Follow the workflow's dependency order and templates, using completed documents as context until all prerequisites for implementation are ready.

中文简介正在准备中。当前显示英语简介。

  • Prepare implementation documents for a new feature
  • Turn a fix description into the required documents
  • Generate related documents in dependency order
alibaba/druid2.8万2026年8月1日 更新

查看 alibaba 的全部技能

报告此技能的问题