openspec-new-change SKILL.md skillA
openspec-new-change from justinjdev/fellowship is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add justinjdev/fellowship/openspec-new-change@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- justinjdev/fellowship
- Path
.claude/skills/openspec-new-change/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0, committed Mar 7, 2026
- Size
- 2,880 bytes
- Repository stars
- 5
- License
- Apache-2.0
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 justinjdev/fellowship/openspec-new-change@sha256:7a9e54256ebae75bThe line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_dvchl2ea66ej2tmc)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 7, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2880 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
justinjdev/fellowship · 5 stars · license Apache-2.0 · pushed 2026-10-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dvchl2ea66ej2tmc GET https://markdownregistry.com/api/v1/resolve?ref=justinjdev/fellowship/openspec-new-change GET https://markdownregistry.com/api/v1/blob/7a9e54256ebae75b84e974ebd67c8e8ae83c83932629d702881ecf402fbd6aca
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 justinjdev/fellowship
Every file in justinjdev/fellowship