spec-discovery
Parse specs to extract IDs, titles, and traceability metadata (repo, path, hash).
Best use case
spec-discovery is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Parse specs to extract IDs, titles, and traceability metadata (repo, path, hash).
Parse specs to extract IDs, titles, and traceability metadata (repo, path, hash).
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "spec-discovery" skill to help with this workflow task. Context: Parse specs to extract IDs, titles, and traceability metadata (repo, path, hash).
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/spec-discovery/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How spec-discovery Compares
| Feature / Agent | spec-discovery | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Parse specs to extract IDs, titles, and traceability metadata (repo, path, hash).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# 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)
1. **Load repositories**: ROOT + EXTRA_REPOS
2. **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 + title
5. **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.Related Skills
sprint-retrospective
Facilitate effective sprint retrospectives for continuous team improvement. Use when conducting team retrospectives, identifying improvements, or fostering team collaboration. Handles retrospective formats, action items, and facilitation techniques.
terraform-specialist
Expert Terraform/OpenTofu specialist mastering advanced IaC automation, state management, and enterprise infrastructure patterns. Handles complex module design, multi-cloud deployments, GitOps workflows, policy as code, and CI/CD integration. Covers migration strategies, security best practices, and modern IaC ecosystems. Use PROACTIVELY for advanced IaC, state management, or infrastructure automation.
search-specialist
Expert web researcher using advanced search techniques and synthesis. Masters search operators, result filtering, and multi-source verification. Handles competitive analysis and fact-checking. Use PROACTIVELY for deep research, information gathering, or trend analysis.
openapi-spec-generation
Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.
claude-win11-speckit-update-skill
Windows 11 system management
bullmq-specialist
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.
laravel-specialist
Use when building Laravel 10+ applications requiring Eloquent ORM, API resources, or queue systems. Invoke for Laravel models, Livewire components, Sanctum authentication, Horizon queues.
specs-creator
Use PROACTIVELY this skill when you need to create comprehensive PRDs, tech specs, and ux specs based on feature description. If the user specify "Create PRD", "Create Tech Specs", or "Create UX Specs", this skill must be triggered.
notion-spec-to-implementation
Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
api-integration-specialist
Expert in integrating third-party APIs with proper authentication, error handling, rate limiting, and retry logic. Use when integrating REST APIs, GraphQL endpoints, webhooks, or external services. Specializes in OAuth flows, API key management, request/response transformation, and building robust API clients.
openspec-daem0n-bridge
Bridges OpenSpec (spec-driven development) with Daem0n-MCP memory - auto-imports specs, informs proposals with past outcomes, converts archived changes to learnings
design-spec-extraction
Extract comprehensive JSON design specifications from visual sources including Figma exports, UI mockups, screenshots, or live website captures. Produces W3C DTCG-compliant output with component trees, suitable for code generation, design documentation, and developer handoff.