Home / attilaszasz / sdd-pilot · GitHub

spec-authoring SKILL.md skillA

spec-authoring from attilaszasz/sdd-pilot is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add attilaszasz/sdd-pilot/spec-authoring@git:20260811.ebf539e

Pins git:20260811.ebf539e in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: attilaszasz/sdd-pilot
Path: .github/skills/spec-authoring/SKILL.md
Versions recorded: 5
Latest version: git:20260811.ebf539e, committed Aug 11, 2026
First version recorded: Mar 27, 2026
Size: 9,771 bytes
Repository stars: 98
License: MIT

Reference material for writing product, technical, and operational specifications (work-item priorities, requirement families, success criteria). Loaded on demand by `specify-feature`; not directly invokable.

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

# Spec Authoring Guide

## Spec Writing Process

### 1. Parse the Feature Description
- Determine `spec_type` from workflow context or spec frontmatter; default to `product` if absent.
- Extract: actors, actions, data, constraints, dependencies, deliverables.
- Empty normalized description → ERROR "No feature description provided".

### 2. Fill the Template
Use [assets/spec-template.md](assets/spec-template.md). Replace all placeholders; remove sections that don't apply to the chosen `spec_type`.

### 3. Product Specs (`spec_type: product`)
- Assign P1–P3+. Each user story independently testable; P1 alone yields viable MVP.
- Action-noun format for story titles.
- Include Given/When/Then acceptance scenarios.
- **"Why this priority"**: required for ALL priorities including P1. One-line rationale. Use priority criteria: P1 = core value proposition / blocks everything else / security-critical; P2 = significant value but MVP works without / enhances P1 flows; P3 = nice-to-have / future foundation / polish.
- "Independent Test": one sentence — what to demo/test.
- Max **200 words** per story excluding acceptance scenarios.

### 4. Technical Specs (`spec_type: technical`)
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add attilaszasz/sdd-pilot/spec-authoring@sha256:c0ecc3ed5478a11e

The line at the top of this page pins the label git:20260811.ebf539e, 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_jrjenaphkrwp52z4.svg)](https://markdownregistry.com/a/art_jrjenaphkrwp52z4)

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

Versions

The registry has recorded 5 versions of this file, between Mar 27, 2026 and Aug 11, 2026, about one every 34 days.

version	committed	commit	size	audit
git:20260811.ebf539e latest	2026-08-11	ebf539e	9,771 B	A	view · diff
git:20260811.46fe327	2026-08-11	46fe327	9,187 B	A	view · diff
git:20260504.206dd76	2026-05-04	206dd76	9,136 B	A	view · diff
git:20260408.ebb0ea9	2026-04-08	ebb0ea9	9,242 B	A	view · diff
git:20260327.b3bb054	2026-03-27	b3bb054	9,184 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 (9771 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

attilaszasz/sdd-pilot · 98 stars · license MIT · pushed 2026-10-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_jrjenaphkrwp52z4
GET https://markdownregistry.com/api/v1/resolve?ref=attilaszasz/sdd-pilot/spec-authoring
GET https://markdownregistry.com/api/v1/blob/c0ecc3ed5478a11e3b8d43b4faeeeda43aefaa8a27de00e28056c92cfdae4b4c

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 attilaszasz/sdd-pilot

sddp-amend SKILL.md skill

attilaszasz/sdd-pilot · .agents/skills/sddp-amend/SKILL.md · Propagate a bootstrap change across canonical project artifacts and the project plan. Direct command-bar dispatch only…