$git clone https://github.com/jcmrs/claude-code-spec-kit-subagent-pluginA 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.
| 1 | # Claude Code Spec Kit Subagent Plugin |
| 2 | |
| 3 | **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](https://github.com/github/spec-kit). |
| 4 | |
| 5 | --- |
| 6 | |
| 7 | ## Features |
| 8 | |
| 9 | - **Conversational Orchestration:** Natural, empathic dialogue management tailored to user preferences. |
| 10 | - **Multi-Role Analysis:** Dynamically identifies and embodies relevant professional perspectives for robust analysis. |
| 11 | - **Memory Graph:** Persists all insights, relationships, and synthesis steps in a queryable, file-based graph. |
| 12 | - **Adaptive Workflow:** Adjusts process phases and requirements in response to user input and context. |
| 13 | - **Transparent Logging:** All actions, analysis, and conversations are logged for auditability and recovery. |
| 14 | - **Claude Code Marketplace Compatible:** Fully supports [Claude Code plugin marketplaces](https://docs.claude.com/en/docs/claude-code/plugin-marketplaces), including a complete `.claude-plugin/marketplace.json` descriptor. |
| 15 | |
| 16 | --- |
| 17 | |
| 18 | ## Plugin Directory & File Structure |
| 19 | |
| 20 | All plugin metadata, code, and agent-generated artifacts are organized as follows: |
| 21 | |
| 22 | ``` |
| 23 | claude-code-spec-kit-subagent-plugin/ |
| 24 | ├── .claude-plugin/ |
| 25 | │ ├── plugin.json |
| 26 | │ └── marketplace.json |
| 27 | ├── agents/ |
| 28 | │ └── spec-kit-partner.md |
| 29 | ├── spec-kit-partner/ |
| 30 | │ ├── src/ |
| 31 | │ │ ├── main.py |
| 32 | │ │ ├── workflow_manager.py |
| 33 | │ │ ├── memory_graph.py |
| 34 | │ │ ├── user_profile.py |
| 35 | │ │ └── multi_role_analysis.py |
| 36 | │ └── project-data/ |
| 37 | │ ├── memory-graph.json |
| 38 | │ ├── user_profile.json |
| 39 | │ ├── workflow_state.json |
| 40 | │ ├── multi-role-analysis.json |
| 41 | │ ├── logs/ |
| 42 | │ │ ├── conversation.log |
| 43 | │ │ └── internal_monologue.log |
| 44 | │ ├── spec/ |
| 45 | │ │ ├── spec.md |
| 46 | │ │ └── state.json |
| 47 | │ └── diagrams/ |
| 48 | │ ├── system_flow.mermaid |
| 49 | │ ├── memory_graph.mermaid |
| 50 | │ ├── workflow_state_machine.mermaid |
| 51 | │ ├── multi_role_analysis_flow.mermaid |
| 52 | │ ├── agent_user_interaction.mermaid |
| 53 | │ ├── data_flow.mermaid |
| 54 | │ └── role_perspective_map.mermaid |
| 55 | ├── assets/ |
| 56 | │ ├── icon.png |
| 57 | │ ├── screenshot1.png |
| 58 | │ └── screenshot2.png |
| 59 | ├── README.md |
| 60 | ├── LICENSE |
| 61 | └── CHANGELOG.md |
| 62 | ``` |
| 63 | |
| 64 | --- |
| 65 | |
| 66 | ## Marketplace Metadata |
| 67 | |
| 68 | Marketplace and plugin metadata are defined in: |
| 69 | |
| 70 | - `.claude-plugin/plugin.json` — Main plugin manifest. |
| 71 | - `.claude-plugin/marketplace.json` — Marketplace listing fields including `display_name`, `summary`, `categories`, `icon`, `documentation_url`, `publisher`, `license`, `screenshots`, and more. |
| 72 | |
| 73 | See [Official Claude Code Marketplace Docs](https://docs.claude.com/en/docs/claude-code/plugin-marketplaces#create-the-marketplace-file). |
| 74 | |
| 75 | --- |
| 76 | |
| 77 | ## Diagram Output Types |
| 78 | |
| 79 | All diagrams are output as **Mermaid (`.mermaid`) format** for easy rendering and AI parsing. Rendered `.svg` or `.png` versions may also be exported, but `.mermaid` is canonical. |
| 80 | |
| 81 | --- |
| 82 | |
| 83 | ## Initialization Protocol |
| 84 | |
| 85 | On first run or when required files are missing: |
| 86 | |
| 87 | - Ensure all required directories exist before writing. |
| 88 | - Generate all support code and persistent data files as described in [Initialization Protocol](./agents/spec-kit-partner.md). |
| 89 | - Populate each `.json` file using provided schemas and set initial values. |
| 90 | - Log all steps and errors to `project-data/logs/conversation.log`. |
| 91 | |
| 92 | See [spec-kit-partner.md](./agents/spec-kit-partner.md) for full protocol. |
| 93 | |
| 94 | --- |
| 95 | |
| 96 | ## Usage |
| 97 | |
| 98 | 1. Install this plugin into your Claude Code environment using your plugin manager or by cloning this repository under `/plugins/`. |
| 99 | 2. On first invocation, the plugin will create and initialize all required files and directories in its workspace. |
| 100 | 3. All runtime state, logs, diagrams, and outputs are self-contained within the plugin directory. |
| 101 | 4. For more details on engine architecture, data schemas, and interaction protocols, refer to the main spec file or plugin documentation. |
| 102 | |
| 103 | --- |
| 104 | |
| 105 | ## Development & Contributing |
| 106 | |
| 107 | This repository includes automated workflows to ensure code quality: |
| 108 | |
| 109 | - **Python Linting** - Validates syntax and style of Python code |
| 110 | - **JSON Validation** - Ensures plugin manifests are valid and complete |
| 111 | - **Asset Validation** - Checks that referenced files exist |
| 112 | - **Markdown/Mermaid Linting** - Validates documentation syntax |
| 113 | - **Python Tests** - Runs automated test suite |
| 114 | |
| 115 | All workflows run automatically on pull requests. See [CONTRIBUTING.md](./CONTRIBUTING.md) for detailed development guidelines. |
| 116 | |
| 117 | --- |
| 118 | |
| 119 | ## License |
| 120 | |
| 121 | This project is licensed under the [MIT License](./LICENSE). |
| 122 | |
| 123 | --- |
| 124 | |
| 125 | ## Contact & Support |
| 126 | |
| 127 | - For questions, contributions, or collaboration, open an issue or contact the repository maintainer. |
| 128 | - For support, visit: [GitH |