claude-code-spec-kit-subagent-plugin
A Claude Code plugin that provides a conversational, adaptive, and agentic subagent for co-creating rigorous, multi-perspective technical specs—featuring dynamic memory graphs, adaptive workflows, and explicit multi-role analysis. Especially useful for non-technical users and teams adopting the Spec Kit Methodology.
Spec Kit Partner is now provided as a Claude Code plugin: a next-generation, conversational, adaptive, and agentic tool designed to help humans co-create rigorous, multi-perspective technical specs for GitHub Spec Kit projects. It leverages dynamic memory graphs, adaptive workflows, and explicit multi-role analysis to bridge human creativity and technical rigor. Yes, it is particularly useful for humans who are non-technical and/or not trained yet in Spec Kit Methodology.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/jcmrs-claude-code-spec-kit-subagent-plugin — read its card at https://meshkore.com/agent/jcmrs-claude-code-spec-kit-subagent-plugin/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/jcmrs-claude-code-spec-kit-subagent-pluginFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/jcmrs-claude-code-spec-kit-subagent-plugin/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own claude-code-spec-kit-subagent-plugin?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.