speckit-opsmill-extract

Extracts ADRs, knowledge, and guidelines from completed spec directories into project documentation.

9|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/opsmill/infrahub-solution-ai-dc --skill speckit-opsmill-extract-opsmill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-opsmill-extract
Source: https://github.com/opsmill/infrahub-solution-ai-dc/tree/main/.agents/skills/speckit-opsmill-extract
Command: npx skills add https://github.com/opsmill/infrahub-solution-ai-dc --skill speckit-opsmill-extract-opsmill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed spec directories in a spec-kit project accumulate valuable architectural decisions and implementation patterns that are lost unless manually distilled into durable documentation. This Skill automates that distillation, moving decisions into ADRs, system knowledge, and coding guidelines. ## Core Features & Use Cases - Multi-spec batch processing: Resolve and process several spec directories in one run, with per-spec validation and extraction-status checks. - Classified extraction: Parse research.md, spec.md, data-model.md, and contracts/ to classify content into ADRs, knowledge updates, and prescriptive guidelines. - Interactive review gate: Present a numbered extraction plan and write nothing until the user approves, skips, edits, or groups items. - Use Case: After finishing a feature spec like specs/042-graphql-name-lookup, run the extraction to generate numbered MADR files in dev/adr/, update dev/knowledge/ and dev/guidelines/, then archive the spec under specs/archive/ with an EXTRACTED.md record. ## Quick Start Extract all durable knowledge, guidelines, and ADRs from the completed spec directory specs/042-graphql-name-lookup into the dev documentation folders.

Frequently Asked Questions about speckit-opsmill-extract

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

FAQPage Schema
How do I extract ADRs from a completed spec-kit spec?▼

Run the extraction with the spec identifier as an argument, such as the spec directory name or number. The Skill parses research.md R# entries, drafts ADR titles, presents an approval plan, and writes numbered MADR files into dev/adr/.

Can I process multiple spec directories at once?▼

Yes, pass multiple space-separated spec identifiers and they are processed sequentially. The extraction plan groups findings by spec with global item numbering, and ADR numbering continues sequentially across all specs.

What project structure does this extraction workflow require?▼

It requires a spec-kit project with a .specify/ directory, specs/ folders containing spec.md and research.md, and target documentation directories dev/knowledge/, dev/guidelines/, and dev/adr/.

What happens if a spec was already extracted?▼

The Skill checks for an EXTRACTED.md file or an existing location under specs/archive/ and warns you. Re-extraction requires explicit confirmation, and the default action is to abort.

Does the extraction write files automatically without review?▼

No, nothing is written until you approve the extraction plan in the interactive review phase. You can approve all items, approve by spec or category, skip or edit individual items, or group multiple ADR candidates into one.