openspec-new-change SKILL.md skillA

openspec-new-change from taskless/cli is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add taskless/cli/openspec-new-change@v1.0

Pins v1.0 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

taskless/cli

Path

.agents/skills/openspec-new-change/SKILL.md

Versions recorded

1

Latest version

v1.0, committed Jul 27, 2026

Size

2,889 bytes

Repository stars

239

License

MIT

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.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

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**

   ```bash
   openspec new change "<name>"
   ```

   Add `--schema <name>` only if the user requested a specific workflow.
…

Read the whole file at its exact version.

How to install

mdr add taskless/cli/openspec-new-change@sha256:cdaa388d36d27cc4

[![mdr](https://markdownregistry.com/badge/art_jltygd5wlpeusuwq.svg)](https://markdownregistry.com/a/art_jltygd5wlpeusuwq)

Versions

The registry has recorded 1 version of this file, committed on Jul 27, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_jltygd5wlpeusuwq
GET https://markdownregistry.com/api/v1/resolve?ref=taskless/cli/openspec-new-change
GET https://markdownregistry.com/api/v1/blob/cdaa388d36d27cc4b29a6a96d748671dc39e7484bab2025828606fee4d16190a

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from taskless/cli

Every file in taskless/cli

Other files named openspec-new-change

Browse by kind, by grade A, or by owner.