Menu
Parse specs to extract IDs, titles, and traceability metadata (repo, path, hash).
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Generic BAML patterns for type-safe LLM prompting. Covers schema design, DTO generation, client wrappers, and cross-language codegen. Framework-agnostic.
Browser automation for documentation discovery. Use when curl fails on JS-rendered sites, when detecting available browser tools, or when configuring browser-based documentation collection.
C4 architectural modeling for documenting software architecture. Use when creating architecture diagrams, planning new systems, communicating with stakeholders, or conducting architecture reviews.
Debug and analyze web applications using Chrome DevTools MCP. Use for console log inspection, network request monitoring, performance analysis, and debugging authenticated sessions. For basic browser automation (screenshots, form filling), use browser-discovery skill instead.
Patterns and techniques for analyzing brownfield codebases. Use when onboarding to unfamiliar code, preparing for refactoring, conducting architecture reviews, or identifying technical debt.
Detect new imports in modified files and auto-install missing dependencies. Works with npm, uv, pip, cargo, go mod, and other package managers. Triggers after code implementation to keep manifests in sync.
| name | spec-discovery |
| description | Parse specs to extract IDs, titles, and traceability metadata (repo, path, hash). |
Locate specs and external request headers, extract IDs (e.g., REQ-NOTIFY-001), and return traceable metadata for downstream agents.
| 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 |
specs/, specs/external-requests/, skip specs/templates/^#+\s*(REQ-[A-Za-z0-9_-]+)\s*:?\s*(.*)$source_repo, path, hashnotes fieldspecs/ directory → report empty result rather than failing{
"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>"
}
]
}
/ai-dev-kit:specs-find or spec traceability.