feature-spec SKILL.md skillA
feature-spec from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qa-aman/claude-skills/feature-spec@git:20260303.19bc151Pins git:20260303.19bc151 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qa-aman/claude-skills
- Path
skills/by-role/pm/feature-spec/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260303.19bc151, committed Mar 3, 2026
- First version recorded
- Mar 3, 2026
- Size
- 3,705 bytes
- Repository stars
- 24
- License
- MIT
Write a concise feature spec for engineering handoff. Use when the user says "write a spec", "feature spec", "one-pager for eng", "spec this out", "write up this feature", "I need to hand this off to engineering", "shape this up", or wants a concise technical brief - even if they don't say "feature spec".
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
## Overview Based on **Shape Up** by Ryan Singer (Basecamp). A feature spec is not a PRD. A PRD justifies building something. A spec tells engineers exactly what to build - but at the right altitude. Shape Up's principle: give engineers a shaped problem with clear boundaries, not a detailed recipe. Ambiguity in the spec becomes a bug in production. Over-specification kills ownership. ## Workflow ### Step 1: Write the header ``` # Feature Spec: [Feature Name] **PM:** [your name] **Eng Lead:** [engineer name] **Appetite:** [1-2 weeks / 4-6 weeks] **Status:** Draft | In Review | Approved **Related PRD / Ticket:** [link] ``` ### Step 2: Write the Problem (2-3 sentences) What is broken or missing? Who is affected? Shape Up framing: "Jobs to be done" - what job is the user hiring this feature to do? ### Step 3: Write the Solution at the right altitude Shape Up's "fat marker sketch" - describe the solution broadly. Engineers need room to make technical decisions. Write at the level of user-visible behavior, not implementation. Structure: - **Key interactions** - what users can do (not how) - **Boundaries** - explicit scope limits - **Rabbit holes** - specific traps to avoid …
Read the whole file at its exact version.
How to install
mdr add qa-aman/claude-skills/feature-spec@sha256:c10c3840e22c40a0The line at the top of this page pins the label git:20260303.19bc151, 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_nxsff7vtmlkm4qvp)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Mar 3, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260303.19bc151 latest | 2026-03-03 | 19bc151 | 3,705 B | A | view · diff |
| git:20260303.f77c189 | 2026-03-03 | f77c189 | 3,228 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 (3705 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
qa-aman/claude-skills · 24 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nxsff7vtmlkm4qvp GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/feature-spec GET https://markdownregistry.com/api/v1/blob/c10c3840e22c40a09bc40adea68dabe3cb760ffbcda15d5f3668f819124236f1
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 qa-aman/claude-skills
Every file in qa-aman/claude-skills