Home / nevenincs / vaultspec-core · GitHub

vaultspec-write SKILL.md skillA

vaultspec-write from nevenincs/vaultspec-core is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add nevenincs/vaultspec-core/vaultspec-write@git:20260908.af390dd

Pins git:20260908.af390dd in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: nevenincs/vaultspec-core
Path: src/vaultspec_core/builtins/skills/vaultspec-write/SKILL.md
Versions recorded: 6
Latest version: git:20260908.af390dd, committed Sep 8, 2026
First version recorded: Jun 13, 2026
Size: 2,389 bytes
Repository stars: 2
License: MIT

Write a proportionate implementation plan when scope or progress needs durable sequencing, after assessing decision coverage.

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

# Plan (vaultspec-write)

Produces the sequence execution can resume across sessions. Apply the vaultspec system
section's routing and approval contract. A plan may reuse governing ADRs or have none
when no costly decision is involved. Drafting does not authorize execution.

## Steps

- Discover governing decisions across features and read the relevant ADRs and evidence.
  Reuse accepted decisions unchanged. Route uncovered costly choices to `vaultspec-adr`;
  a draft may link proposed decisions, but dependent execution waits for acceptance.
- Discover the affected code and exact paths. Expected new files are identified as
  creation work. Record the coverage assessment and authorized scope in the Description,
  particularly when no ADR governs.
- Scaffold:
  `vaultspec-core vault add plan --feature {feature} --tier <L1..L4> [--related <adr-stem> ...]`
  (or `create`). Link each governing ADR; inherit its evidence transitively. Optional
  direct evidence links do not replace governing ADRs.
- Read `.vaultspec/templates/plan.md` for tiers, identifiers, row syntax, and cohesive
  granularity. Build structure with `plan_edit` or the `vaultspec-core vault plan`
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add nevenincs/vaultspec-core/vaultspec-write@sha256:cb5ce968eaae94d7

The line at the top of this page pins the label git:20260908.af390dd, 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_ic2fl3bzomg3sdz3.svg)](https://markdownregistry.com/a/art_ic2fl3bzomg3sdz3)

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

Versions

The registry has recorded 6 versions of this file, between Jun 13, 2026 and Sep 8, 2026, about one every 17 days.

version	committed	commit	size	audit
git:20260908.af390dd latest	2026-09-08	af390dd	2,389 B	A	view · diff
git:20260905.f755314	2026-09-05	f755314	2,703 B	A	view · diff
git:20260723.7fc2f3b	2026-07-23	7fc2f3b	7,535 B	A	view · diff
git:20260714.4266e8c	2026-07-14	4266e8c	7,516 B	A	view · diff
git:20260626.475d40c	2026-06-26	475d40c	6,739 B	A	view · diff
git:20260613.68b0c19	2026-06-13	68b0c19	6,034 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 (2389 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

nevenincs/vaultspec-core · 2 stars · license MIT · pushed 2026-10-27 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ic2fl3bzomg3sdz3
GET https://markdownregistry.com/api/v1/resolve?ref=nevenincs/vaultspec-core/vaultspec-write
GET https://markdownregistry.com/api/v1/blob/cb5ce968eaae94d77581e47b9b68bfa86bb4bef09149a7a365df53b3ad2ab071

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 nevenincs/vaultspec-core

vaultspec-adr SKILL.md skill

nevenincs/vaultspec-core · .vaultspec/skills/vaultspec-adr/SKILL.md · Record a costly decision, place it within accepted decision coverage, and reconcile affected ADR wording.