to-spec SKILL.md skillA

This file is byte-identical to the first copy the registry indexed, one of 9 indexed copies. Same content hash, so the same checks give both the same grade.

to-spec from j-star-films-studios/vibecode-protocol-suite is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add j-star-films-studios/vibecode-protocol-suite/to-spec@git:20260821.1b830a3

Pins git:20260821.1b830a3 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

j-star-films-studios/vibecode-protocol-suite

Path

assets/.agent/skills/agent-engineering/conversation-to-spec/SKILL.md

Versions recorded

1

Latest version

git:20260821.1b830a3, committed Aug 21, 2026

Size

3,043 bytes

Repository stars

26

License

ISC

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

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

This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user; just synthesize what you already know.

The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `/setup-matt-pocock-skills`.

## Process

1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.

2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.

Check with the user that these seams match their expectations.

3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.

<spec-template>

## Problem Statement

The problem that the user is facing, from the user's perspective.

## Solution
…

Read the whole file at its exact version.

How to install

mdr add j-star-films-studios/vibecode-protocol-suite/to-spec@sha256:43ad9cf318e5e7d3

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

Versions

The registry has recorded 1 version of this file, committed on Aug 21, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_uugisngxbuwmo4xz
GET https://markdownregistry.com/api/v1/resolve?ref=j-star-films-studios/vibecode-protocol-suite/to-spec
GET https://markdownregistry.com/api/v1/blob/43ad9cf318e5e7d3d1fa360253a37021796dc87a0c2e595ad262661a10f85088

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 j-star-films-studios/vibecode-protocol-suite

Every file in j-star-films-studios/vibecode-protocol-suite

Other files named to-spec

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