How do I install the Spec Discovery skill?

Run npx skillmds@latest add aiskillstore/spec-discovery in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Spec Discovery skill do?

Parse specs to extract IDs, titles, and traceability metadata (repo, path, hash). It is listed under Product & Planning on SkillMD.

Is Spec Discovery safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spec Discovery?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spec Discovery free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spec Discovery?

aiskillstore (@aiskillstore) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spec Discovery by aiskillstore — Agent Skill

Name: Spec Discovery
Rating: 4.2 (5 reviews)
Author: aiskillstore

File contents

Spec Discovery Skill

Locate specs and external request headers, extract IDs (e.g., REQ-NOTIFY-001), and return traceable metadata for downstream agents.

Variables

Variable	Default	Description
ROOT	.	Primary repository root
EXTRA_REPOS	[]	Additional repo roots containing `specs/`
INCLUDE_EXTERNAL_REQUESTS	true	Scan `specs/external-requests/`
OUTPUT_FORMAT	json	json or toon manifest output

Workflow (Mandatory)

Load repositories: ROOT + EXTRA_REPOS
Walk specs: specs/, specs/external-requests/, skip specs/templates/
Parse headings: match ^#+\s*(REQ-[A-Za-z0-9_-]+)\s*:?\s*(.*)$
Normalize: path relative to repo root, anchor from ID + title
Traceability: compute SHA-256 of file content; record source_repo, path, hash
Emit manifest: sorted by repo → path → ID in JSON/TOON (see Output Schema)

Red Flags (Stop & Verify)

No IDs detected in a spec file → confirm heading format before skipping
Duplicate spec IDs across repos → flag in the manifest notes field
Missing specs/ directory → report empty result rather than failing

Output Schema

{
  "format": "spec-manifest/v1",
  "generated_at": "<ISO-8601 UTC>",
  "sources": [
    {"repository": "<repo-name>", "root": "<abs-path>"}
  ],
  "specs": [
    {
      "id": "REQ-NOTIFY-001",
      "title": "Email Sending Endpoint",
      "source_repo": "ai-dev-kit",
      "path": "specs/external-requests/notify.md",
      "link": "specs/external-requests/notify.md#req-notify-001-email-sending-endpoint",
      "hash": "<sha256-of-file>"
    }
  ]
}

Provider Notes

Use this skill when other commands request /ai-dev-kit:specs-find or spec traceability.
Prefer JSON for machine workflows; use TOON for compact prompt embedding.
Preserve ID/title casing; anchors should be lowercase + hyphenated.

---name: spec-discoverydescription: Parse specs to extract IDs, titles, and traceability metadata (repo, path, hash).---# Spec Discovery SkillLocate specs and external request headers, extract IDs (e.g., `REQ-NOTIFY-001`), and return traceable metadata for downstream agents.## Variables| Variable | Default | Description ||----------|---------|-------------|| ROOT | . | Primary repository root || EXTRA_REPOS | [] | Additional repo roots containing `specs/` || INCLUDE_EXTERNAL_REQUESTS | true | Scan `specs/external-requests/` || OUTPUT_FORMAT | json | json or toon manifest output |## Workflow (Mandatory)1. **Load repositories**: ROOT + EXTRA_REPOS2. **Walk specs**: `specs/`, `specs/external-requests/`, skip `specs/templates/`3. **Parse headings**: match `^#+\s*(REQ-[A-Za-z0-9_-]+)\s*:?\s*(.*)$`4. **Normalize**: path relative to repo root, anchor from ID + title5. **Traceability**: compute SHA-256 of file content; record `source_repo`, `path`, `hash`6. **Emit manifest**: sorted by repo → path → ID in JSON/TOON (see Output Schema)## Red Flags (Stop & Verify)- No IDs detected in a spec file → confirm heading format before skipping- Duplicate spec IDs across repos → flag in the manifest `notes` field- Missing `specs/` directory → report empty result rather than failing## Output Schema```json{ "format": "spec-manifest/v1", "generated_at": "<ISO-8601 UTC>", "sources": [ {"repository": "<repo-name>", "root": "<abs-path>"} ], "specs": [ { "id": "REQ-NOTIFY-001", "title": "Email Sending Endpoint", "source_repo": "ai-dev-kit", "path": "specs/external-requests/notify.md", "link": "specs/external-requests/notify.md#req-notify-001-email-sending-endpoint", "hash": "<sha256-of-file>" } ]}```## Provider Notes- Use this skill when other commands request `/ai-dev-kit:specs-find` or spec traceability.- Prefer JSON for machine workflows; use TOON for compact prompt embedding.- Preserve ID/title casing; anchors should be lowercase + hyphenated.

Frequently asked questions

Spec Discovery