[Extension Proposal] ADIK SDK Generator — multi-language SDK generation from Spec Kit implementations

[mateors1]

Hi Spec Kit team and community 👋

I'd like to propose ADIK (Agentic Development and Implementation Kit) as a Spec Kit extension that fills the SDK generation layer — the step after /speckit.implement that turns your working application into publish-ready SDK packages.

What ADIK Does

ADIK is an open-source framework (repo, website) that produces self-sustaining agentic SDKs. A team of cooperating AI agents:

1. Scans source code and OpenAPI contracts → builds a language-agnostic symbol Registry
2. Validates the Registry with a 14-rule, three-level gate (structural, type, semantic)
3. Generates complete, publish-ready SDK packages in TypeScript, Python, C#, and optionally Go, Java, Kotlin
4. Generates framework-idiomatic integration code — DI wiring, retry wrappers, usage examples
5. Self-embeds into AI context files so any assistant knows the SDK exists
6. Self-maintains — the adik carries its own agents and re-generates on every commit

Why It Fits Spec Kit

The integration is architecturally native:

• Handoff point: Spec Kit's /speckit.plan emits contracts/api-spec.json. ADIK's Codebase Analyst already parses OpenAPI specs as a first-class input. One includePatterns config entry bridges the path convention.
• Layer separation: Spec Kit operates at Layer 0 (intent → code). ADIK operates at Layer 1-2 (code → registry → SDK). Zero feature overlap.
• Context coexistence: Both frameworks write to .github/copilot-instructions.md and CLAUDE.md. ADIK uses <!-- ADIK:START/END --> guard markers that don't conflict with Spec Kit's content. Tested and verified.
• Traceability: Registry symbols can carry tags: ["spec:001-feature"] linking SDK methods back to Spec Kit feature specs.

Proposed Extension Commands

Command	When	What
/speckit.adik.registry	After /speckit.implement	Scan source + api-spec.json → populate Registry.md
/speckit.adik.sdk	After registry	Validate → generate SDK packages
/speckit.adik.boilerplate	After SDK	Detect framework → DI wiring, examples, retry logic
/speckit.adik.status	Any time	Report SDK sync status

What I've Built So Far

• ✅ Full extension structure (extension.yml, 4 templates, agent commands for Claude/Copilot/Gemini/generic)
• ✅ Integration guide with step-by-step Spec Kit workflow
• ✅ 10-part technical analysis comparing the two frameworks (docs/ecosystem/spec-kit.md)
• ✅ Codebase Analyst updated to scan .specify/ contract paths
• ✅ Configuration docs showing Spec Kit includePatterns and partitionMappings

Next Steps

I'd love to:

1. Get feedback on the extension design from the Spec Kit team and community
2. Build a community walkthrough using Spec Kit's Taskify demo as the base project
3. Submit a PR to add the extension to extensions/catalog.community.json

The extension source and all documentation are at:
https://github.com/mateors1/adik.md-agentic-development-and-implementation-kit-Framework/tree/main/docs/ecosystem/spec-kit-adik

Happy to answer any questions about the architecture, the handoff mechanics, or anything else.

— Mateo (@mateors1)

[mnriem]

Go for it!