spec

Conduct codebase-grounded interviews to generate versioned SpecKit-compatible specifications.

Updated Aug 23, 2026

Search Tags:#codebase #specification #requirements #interview #feature #speckit #codegraph

Ready to run

npx skills add https://github.com/thethirdorigin/skills --skill spec-thethirdorigin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/thethirdorigin/skills/tree/main/plugins/thethirdorigin-skills/skills/spec
Command: npx skills add https://github.com/thethirdorigin/skills --skill spec-thethirdorigin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires codegraph.

What problem does it solve?

Elicit clear, testable requirements by conducting a codebase-grounded interview and producing a SpecKit-compatible specification that aligns with real modules, patterns, and domain terms discovered in the project.

Core Features & Use Cases

Codebase-grounded interview flow that references concrete modules, patterns, and domain terms.
Generates a versioned SpecKit specification artifact ready for the pipeline (constitution → spec → plan → tasks → code).
Fallback discovery support (grep/glob) when CodeGraph is unavailable, ensuring robust spec generation across repos.

Quick Start

Initiate a codebase-grounded interview to generate a ready-to-use SpecKit specification artifact.

Frequently Asked Questions about spec

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

FAQPage Schema

How do I generate feature specifications grounded in my existing codebase?▼

Codebase-grounded feature specifications are produced through an interview-led elicitation process that references real modules, patterns, and domain terms discovered in your project. This generates a versioned SpecKit specification artifact ready for integration.

What is the best way to extract testable requirements from a codebase interview?▼

The best way to extract testable requirements from a codebase interview is to use a guided elicitation flow that aligns questions with concrete code patterns. This yields a SpecKit-compatible specification artifact with concrete references to your modules.

Do I need CodeGraph to generate SpecKit specifications from my repository?▼

You do not need CodeGraph to generate SpecKit specifications. While CodeGraph provides codebase grounding for the interview, the system falls back to traditional grep and glob discovery methods when CodeGraph is unavailable, ensuring robust spec generation across repos.

Can I use an interview-led approach to create versioned spec artifacts for any codebase?▼

Yes, you can use an interview-led approach to create versioned spec artifacts for any codebase. The specification generation process applies to repositories with or without CodeGraph, utilizing fallback discovery support to ensure continuous spec management.

What are the limitations of using traditional code search for codebase-grounded requirement extraction?▼

The limitation of using traditional code search for codebase-grounded requirement extraction is that it relies on basic grep and glob fallback discovery rather than deep structural analysis. This fallback activates when CodeGraph is unavailable, providing robust but less graph-aware spec generation.