spec SKILL.md skillA

spec from epicsagas/epic-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add epicsagas/epic-harness/spec@git:20261102.34d225c

Pins git:20261102.34d225c in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
epicsagas/epic-harness
Path
skills/spec/SKILL.md
Versions recorded
4
Latest version
git:20261102.34d225c, committed Nov 2, 2026
First version recorded
Jun 25, 2026
Size
5,071 bytes
Repository stars
20
License
Apache-2.0

Spec phase. Converts user requirements into a numbered Requirements + Acceptance Criteria document saved as SPEC-{timestamp}.md. Prompts /team suggestion when 3+ requirements are detected.

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 — Define What to Build

**CRITICAL**: Run `HARNESS_DIR=$(epic-harness path)` first. NEVER use `.harness/` in the project directory.

## Process

1. **Understand the request**
   - Read any existing context (CLAUDE.md, README, codebase structure)
   - If `.epic/team.md` (or `.epic/team.local.md`) has a `## spec` section, each of its bullets is required spec content, not advice. Missing one is a `GAP:` in the readiness gate.
   - If the request is vague, ask focused questions (max 3 at a time)
   - Never assume — clarify ambiguity before proceeding

2. **Produce the spec**
   Write a concise spec covering:
   - **Goal**: One sentence — what does this achieve?
   - **Scope**: What's included and explicitly excluded
   - **Requirements**: Numbered list (`R1`, `R2`, ...) of concrete, testable behaviors
   - **Acceptance criteria**: Numbered list (`AC1`, `AC2`, ...) — observable outcomes that prove each requirement is met
   - **Technical notes**: Constraints, dependencies, edge cases
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_35menpou6ox2fudu/ddbed3e5b112e21590f060f15201e4b1655f7e73b809d7f8bb575b9be972e5e7.json

Then /plugin install spec@markdownregistry-35menpou6ox2fudu in Claude Code. It installs git:20261102.34d225c, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add epicsagas/epic-harness/spec@sha256:ddbed3e5b112e215

The line at the top of this page pins the label git:20261102.34d225c, 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 badge

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

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

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in epicsagas/epic-harness/spec since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of spec from somewhere else? Ask it: where did my spec come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 4 versions of this file, between Jun 25, 2026 and Nov 2, 2026, about one every 43 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261102.34d225c latest2026-11-02 34d225c 5,071 BA view · diff
git:20261102.c8090a02026-11-02 c8090a0 4,339 BA view · diff
git:20261102.ac98b852026-11-02 ac98b85 4,158 BA view · diff
git:20260625.1c5e8072026-06-25 1c5e807 3,122 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

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 (5071 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

epicsagas/epic-harness · 20 stars · license Apache-2.0 · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_35menpou6ox2fudu
GET https://markdownregistry.com/api/v1/resolve?ref=epicsagas/epic-harness/spec
GET https://markdownregistry.com/api/v1/blob/ddbed3e5b112e21590f060f15201e4b1655f7e73b809d7f8bb575b9be972e5e7

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 epicsagas/epic-harness

benchmark SKILL.md skill
epicsagas/epic-harness · .claude/skills/benchmark/SKILL.md · Executes Bare-vs-Epic A/B benchmarking, Ring 0 Guard 50 challenge, and full golden set evaluation for epic-harness…
git:20260904.0573d85 · audit A · 20 stars
AGENTS.md AGENTS.md file
epicsagas/epic-harness · AGENTS.md
git:20261117.d9269a2 · audit A · 20 stars
CLAUDE.md CLAUDE.md file
epicsagas/epic-harness · CLAUDE.md
git:20260625.1c5e807 · audit B · 20 stars
_critic SKILL.md skill
epicsagas/epic-harness · skills/_critic/SKILL.md · HarnessX Critic (Tier 2.1) — adversarial review of evolved-skill proposals against trace evidence. Detects reward…
git:20260625.1c5e807 · audit A · 20 stars
_dispatch SKILL.md skill
epicsagas/epic-harness · skills/_dispatch/SKILL.md · Core router. Always active. Auto-invokes matching skill before every response. Runs confusion protocol on high-risk…
git:20261102.ac98b85 · audit A · 20 stars
agent-introspection SKILL.md skill
epicsagas/epic-harness · skills/agent-introspection/SKILL.md · Loop-breaking self-diagnosis. Use when 3+ consecutive failures occur, circular retries persist, or context overwhelms…
git:20260625.1c5e807 · audit A · 20 stars
audit SKILL.md skill
epicsagas/epic-harness · skills/audit/SKILL.md · Audit phase. Parallel review: code quality + security + tests. Semantic dedup of cross-mode findings. Outputs…
git:20261103.eb4d20b · audit A · 20 stars
commit SKILL.md skill
epicsagas/epic-harness · skills/commit/SKILL.md · Conventional Commits 1.0 generator. Stages relevant files, infers type(scope): description, never uses --no-verify.
git:20260625.1c5e807 · audit A · 20 stars
context SKILL.md skill
epicsagas/epic-harness · skills/context/SKILL.md · Working-state snapshot guidance. Restates task/files/decisions in one block so state survives context compaction…
git:20260831.ed1879c · audit A · 20 stars
council SKILL.md skill
epicsagas/epic-harness · skills/council/SKILL.md · 4-voice parallel deliberation (Architect · Skeptic · Pragmatist · Critic) for architecture, tech selection, or design…
git:20260625.1c5e807 · audit A · 20 stars
debug SKILL.md skill
epicsagas/epic-harness · skills/debug/SKILL.md · Systematic root-cause isolation for test failures, runtime errors, or unexpected behavior. Narrow hypothesis → verify →…
git:20260625.1c5e807 · audit A · 20 stars
discover SKILL.md skill
epicsagas/epic-harness · skills/discover/SKILL.md · Trigger: vague/unfocused request or solution-without-problem. Also invoked via /discover command. Reframes goal before…
git:20260625.1c5e807 · audit A · 20 stars

Every file in epicsagas/epic-harness

Other files named spec

spec SKILL.md skill
garrytan/gstack · spec/SKILL.md · Turn vague intent into a precise, executable spec in five phases. (gstack)
v0.1.0 · audit A · 141,854 stars
spec SKILL.md skill
snowflake-labs/cocoplus · .cortex/skills/cocobrew/spec/SKILL.md · Enter the Spec phase of CocoBrew. Guides the developer through structured requirements capture: goal, success criteria…
v1.0.4 · audit A · 729 stars
spec SKILL.md skill
strands-agents/box · .agents/skills/spec/SKILL.md · Walk through spec-driven development, design then requirements, producing a local .spec.md and .requirements.md for one…
git:20261007.158dade · audit A · 548 stars
spec SKILL.md skill
atelier-fashion/adlc-toolkit · spec/SKILL.md · Write requirement specs from feature requests
git:20261030.c4e119a · audit A · 174 stars
spec SKILL.md skill
moonlight-lupin/agent-skills · plugins/dev-pipeline/skills/spec/SKILL.md · Use when pinning intent before code — capture a spec (user stories, acceptance criteria, [NEEDS CLARIFICATION]…
v2.1.0 · audit A · 131 stars
spec SKILL.md skill
kerberosclaw/kc_ai_skills · spec/SKILL.md · Use when the user wants a spec-driven development workflow for implementing a feature in the current codebase, from…
v1.10.0 · audit A · 80 stars
spec SKILL.md skill
renzrollon/interlock · skills/spec/SKILL.md · Take a rough intent to a reviewed, implementation-ready OpenSpec change — explore first, generate proposal, design…
git:20261113.435be27 · audit A · 62 stars
spec SKILL.md skill
rjmurillo/ai-agents · src/claude/skills/spec/SKILL.md · Turn a problem into testable requirements with acceptance criteria, through a first-principles gate, a memory-first…
v1.0.0 · audit A · 49 stars

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