inferspec 0.2.0a0

Reverse-infer OpenSpec specs from code + multi-source context

English | 繁體中文 | 简体中文 | 日本語

InferSpec

Reverse-infer OpenSpec specs from your codebase + git history + docs — designed for legacy code that has no spec.

From Code & Context to Clear Specs

Why InferSpec?

You inherit a 50K-line Flask service. There is no spec. There is a Jira board from three years ago, a Confluence wiki nobody updates, and the git log.

InferSpec reads all of it and produces a structured OpenSpec spec — one spec.md per capability — with each Requirement cited back to file:line or a ticket ID. Ambiguities are marked [GAP]/[TBD] so you can fill them interactively in a follow-up pass.

How it works

┌─────────────────────────────────────────────────────────────┐
│  Layer 1 — uvx Python package: installer + CLI               │
│  (never calls an LLM API)                                   │
└─────────────────────────────────────────────────────────────┘
                       │ installs skills into
                       ▼
┌─────────────────────────────────────────────────────────────┐
│  Layer 2 — Skills run inside Claude Code / Codex / Gemini   │
│  / Copilot / OpenCode and use the host's subscription AI    │
└─────────────────────────────────────────────────────────────┘

InferSpec leans on your existing AI subscription. No API keys, no cloud endpoints to configure.

Install

uvx inferspec init --platform claude-code

That drops /inferspec-scan into .claude/skills/ for the current directory. See inferspec platforms for the full list.

Usage

Open your AI agent in the target repo. Two skills are available:

/inferspec-scan — bulk-infer specs for every capability:

/inferspec-scan

It runs graphify to cluster files into capabilities, then for each cap reads code + git log + docs/ + (if available) Jira/Confluence via MCP + URLs via the host's WebFetch, and drafts openspec/specs/<cap>/spec.md in OpenSpec format. Drafts may contain [GAP] / [TBD] markers where the AI was unsure.

/inferspec-cap <slug> — single-capability deep dive with interactive Q&A:

/inferspec-cap user-auth
/inferspec-cap "rate limiting"       # fuzzy match
/inferspec-cap                       # interactive picker
/inferspec-cap new-feature --new     # bootstrap a brand-new cap

For one capability, the skill solicits Jira/Confluence/URLs you have, then asks one focused question per [GAP] marker until the spec converges. On exit it offers to commit the result for you.

Multi-source artefacts are picked up automatically — InferSpec detects MCP servers in your host environment rather than shipping its own clients.

Output format

Same convention as OpenSpec:

## Purpose

User authentication for the order portal — replaced the legacy SSO bridge
after incident-1234. See AUTH-456.

## Requirements

### Requirement: Rate Limiting
The system SHALL reject login attempts after 5 failures within 60 seconds.

**Source:** auth.py:18-21, [JIRA AUTH-456]

#### Scenario: Lockout after repeated failures
- **GIVEN** 5 failed attempts in the last minute
- **WHEN** another POST /auth/login arrives
- **THEN** server returns 429

Status

v0.2 alpha. Ships /inferspec-scan (bulk mode) + /inferspec-cap (interactive single-cap mode). /inferspec-refine is under evaluation for v0.3.

License

MIT