openspec-propose SKILL.md skillA

openspec-propose from full-aigc-plugins/blender-design-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add full-aigc-plugins/blender-design-plugin/openspec-propose@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

full-aigc-plugins/blender-design-plugin

Path

.kimi-code/skills/openspec-propose/SKILL.md

Versions recorded

2

Latest version

v1.0, committed Sep 23, 2026

First version recorded

Sep 19, 2026

Size

11,221 bytes

Repository stars

4

License

Apache-2.0

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

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

Propose a new change - create the change and generate all artifacts in one step.

**Planning boundary**: This workflow creates planning artifacts only. The user request that selected or triggered this workflow authorizes planning only, even if it asks to build or fix something. Do not edit project code. After the planning artifacts are complete, stop. Do not start implementation in the same response, even if the initial request asks for it. Wait for a new user request after the artifacts are presented; then start the apply workflow.

I'll create a change with the artifacts your schema defines. With the default spec-driven schema that is:

- proposal.md (what & why)
- `specs/<capability-path>/spec.md` (what the system must do - a delta, not the main spec)
- design.md (how)
- tasks.md (implementation steps)

`<capability-path>` is the spec directory relative to `specs/` (for example, `user-auth` or `identity/user-auth`). Preserve an existing capability's full path and follow the project's established organization for new capabilities.

When the user is ready to implement, they must start the apply workflow explicitly.

---
…

Read the whole file at its exact version.

How to install

mdr add full-aigc-plugins/blender-design-plugin/openspec-propose@sha256:43ea4a8dd24f43b4

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

Versions

The registry has recorded 2 versions of this file, between Sep 19, 2026 and Sep 23, 2026, about one every 4 days.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_mb4sbofebmytha4o
GET https://markdownregistry.com/api/v1/resolve?ref=full-aigc-plugins/blender-design-plugin/openspec-propose
GET https://markdownregistry.com/api/v1/blob/43ea4a8dd24f43b456aba73652871861faf76dce8a51d88ea4e4ec315a6314bb

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 full-aigc-plugins/blender-design-plugin

Every file in full-aigc-plugins/blender-design-plugin

Other files named openspec-propose

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