Home / intent-driven-dev / intent-driven-template · GitHub

openspec-propose SKILL.md skillA

openspec-propose from intent-driven-dev/intent-driven-template is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add intent-driven-dev/intent-driven-template/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: intent-driven-dev/intent-driven-template
Path: .opencode/skills/openspec-propose/SKILL.md
Versions recorded: 2
Latest version: v1.0, committed Oct 3, 2026
First version recorded: May 10, 2026
Size: 16,252 bytes
Repository stars: 194
License: MIT

Propose a new OpenSpec 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. Also use when the user says "openspec propose" or "opsx propose".

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

The exact contents, by fingerprint

mdr add intent-driven-dev/intent-driven-template/openspec-propose@sha256:452fdba515e1d03f

The 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.

Badge

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

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, between May 10, 2026 and Oct 3, 2026, about one every 146 days.

version	committed	commit	size	audit
v1.0 latest	2026-10-03	98cac1f	16,252 B	A	view · diff
v1.0	2026-05-10	a8b8231	4,646 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (16252 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

GitHub

intent-driven-dev/intent-driven-template · 194 stars · license MIT · pushed 2026-10-15 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_mff4wv4xyjbge5w5
GET https://markdownregistry.com/api/v1/resolve?ref=intent-driven-dev/intent-driven-template/openspec-propose
GET https://markdownregistry.com/api/v1/blob/452fdba515e1d03f4c5c392f82b59ffe56b03a10742448eda4c9f0dbe8fe02b1

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 intent-driven-dev/intent-driven-template

acceptance-test-authoring SKILL.md skill

intent-driven-dev/intent-driven-template · .agents/skills/acceptance-test-authoring/SKILL.md · Use when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step…

git:20260815.02a4647 · audit A · 194 stars

architectural-decision-records SKILL.md skill

intent-driven-dev/intent-driven-template · .agents/skills/architectural-decision-records/SKILL.md · Use when documenting, drafting, reviewing, or updating architectural decisions, ADRs, decision logs, tradeoffs…