vinta-migrate-plans-specs SKILL.md skillA
vinta-migrate-plans-specs from vintasoftware/vinta-ai-workflows is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vintasoftware/vinta-ai-workflows/vinta-migrate-plans-specs@git:20261003.81d5d7ePins git:20261003.81d5d7e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vintasoftware/vinta-ai-workflows
- Path
skills/vinta-migrate-plans-specs/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261003.81d5d7e, committed Oct 3, 2026
- First version recorded
- May 5, 2026
- Size
- 13,790 bytes
- Repository stars
- 12
- License
- MIT
Find existing implementation plans and feature specs scattered across a project (`docs/`, `specs/`, `plans/`, root markdown, branch-named files, etc.) and migrate them to the canonical layout `ai-plans/YYYY-MM-DD-{FEATURE_NAME}_{PLAN|SPEC}.md`. Reads each candidate, proposes a target path (date + feature name + classification PLAN vs SPEC), shows the rename diff, and only renames after the user explicitly accepts each one. Run as step 6 of…
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
# Migrate plans + specs
The Vinta convention: every implementation plan and every feature spec lives under `ai-plans/` at the repo root, named:
```
ai-plans/YYYY-MM-DD-{FEATURE_NAME}_{PLAN|SPEC}.md
```
- `YYYY-MM-DD` — date the doc was authored (use git log first-commit date when migrating, fall back to file mtime, fall back to ask).
- `FEATURE_NAME` — `UPPERCASE_WITH_UNDERSCORES`. Same prefix shared by a spec and its plan so `ls ai-plans/` groups pairs.
- `_PLAN` or `_SPEC` — classification. Spec describes *what + why*; plan describes *how + when*.
Real-world repos accumulate these docs in many other shapes:
| Shape | Examples |
|---|---|
| Per-feature folders | `docs/features/<name>/spec.md`, `docs/features/<name>/plan.md` |
| Flat docs/ | `docs/SPEC-checkout.md`, `docs/PLAN-2025-checkout.md` |
| Project root | `IMPLEMENTATION_PLAN.md`, `SPEC.md`, `ROADMAP.md` |
| Branch-named | `feature/checkout/spec.md`, `feat-checkout-plan.md` |
| Date-prefixed but off-format | `2025-11-checkout-plan.md`, `2025_11_checkout_spec.md` |
| ADR-style | `docs/adr/0007-checkout.md` (sometimes spec-shaped, sometimes not) |
…Read the whole file at its exact version.
How to install
mdr add vintasoftware/vinta-ai-workflows/vinta-migrate-plans-specs@sha256:5fcf24db6783486eThe line at the top of this page pins the label git:20261003.81d5d7e, 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_h7yghvbtuanx677c)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 5, 2026 and Oct 3, 2026, about one every 75 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261003.81d5d7e latest | 2026-10-03 | 81d5d7e | 13,790 B | A | view · diff |
| git:20260513.f57f3c6 | 2026-05-13 | f57f3c6 | 13,187 B | A | view · diff |
| git:20260505.25de2bb | 2026-05-05 | 25de2bb | 13,217 B | A | view |
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 (13790 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
vintasoftware/vinta-ai-workflows · 12 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_h7yghvbtuanx677c GET https://markdownregistry.com/api/v1/resolve?ref=vintasoftware/vinta-ai-workflows/vinta-migrate-plans-specs GET https://markdownregistry.com/api/v1/blob/5fcf24db6783486edec0df91d72572737e230aae5d405bbcab156f738bb8019d
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.