spec-discovery

Parse specs to extract IDs, titles, and SHA-256 hashes into a JSON or TOON manifest.

8|1|Updated Jul 11, 2025
One-click install
npx skills add https://github.com/Consiliency/treesitter-chunker --skill spec-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-discovery
Source: https://github.com/Consiliency/treesitter-chunker/tree/main/.ai-dev-kit/skills/spec-discovery
Command: npx skills add https://github.com/Consiliency/treesitter-chunker --skill spec-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams locate specs across repositories and generate a traceable manifest of IDs, titles, and hashes to support governance, auditing, and downstream automation.

Core Features & Use Cases

  • Spec discovery across multiple repos by scanning specs/ and specs/external-requests/.
  • ID/title extraction from spec headings following a standardized format.
  • Traceability generation by recording repository, relative path, and SHA-256 hash; emits a machine-friendly manifest for downstream agents.

Quick Start

Load ROOT pointing to your primary repository; optionally set EXTRA_REPOS to include additional roots containing specs. Run the spec-discovery workflow to scan specs/ and specs/external-requests/, excluding specs/templates/, normalize paths to anchors, compute hashes, and emit a manifest in JSON or TOON.

Frequently Asked Questions about spec-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract spec IDs and metadata across multiple repositories?

Spec discovery scans specs/ and specs/external-requests/ directories across a primary repository and optional additional repositories, extracting spec IDs, titles, and recording repository source, file path, and SHA-256 hash for each spec into a structured manifest.

What metadata does spec discovery capture for traceability?

Spec discovery records the spec ID, title, source repository, relative file path, and SHA-256 hash for each discovered spec, enabling auditing, governance, and downstream automation workflows to track specs across codebases.

Can I scan specs across multiple repositories at once?

Yes. Set ROOT to your primary repository and optionally configure EXTRA_REPOS to include additional repositories containing specs. The workflow scans all configured roots in a single pass and combines results into one manifest.

Does spec discovery skip template files?

Yes. Spec discovery automatically excludes specs/templates/ from scanning, focusing only on actual spec files in specs/ and specs/external-requests/ to avoid processing template boilerplate.

What output formats does spec discovery support?

Spec discovery emits structured manifests in JSON or TOON format, making the traceability data machine-readable for integration with downstream agents and automation tools.

How is spec content integrity verified?

Spec discovery computes SHA-256 hashes for each discovered spec and records them in the manifest, allowing teams to verify spec integrity, detect changes, and maintain a chain of custody for governance.