Add comprehensive 8-phase roadmap for spec-kit to Claude Code plugin conversion

[Copilot]

Establishes actionable plan to adapt the spec-kit repository into a Claude Code plugin for the retso-marketplace, following the standard plugin creation workflow.

Architecture Decisions

Plugin Structure

• Name: spec-kit, namespace: /spec-kit:
• Commands: init, plan, create, validate, sync
• Agents: spec-analyzer, spec-generator, doc-syncer
• Quality rules: completeness, clarity, consistency
• Config: .claude/spec-kit/config.json with JSON Schema validation

Technical Stack

• TypeScript-based Bun/Node.js CLI in scripts/
• Compiled distribution via dist/ (committed)
• Model selection: Sonnet for complex analysis, Haiku for fast validation
• Cross-platform support (Windows, macOS, Linux)

Implementation Phases

Phase 1-3: Discovery & Design (Weeks 1-2)

• Audit spec-kit CLI commands, dependencies, AI logic
• Define agent I/O contracts (JSON schemas)
• Document command workflows and error handling

Phase 4-5: Structure & Core (Weeks 3-4)

• Create plugins/spec-kit/ directory with plugin.json manifest
• Implement 5 core commands with YAML frontmatter
• Build agents with structured output for aggregation
• Define rule templates and spec templates

Phase 6: CLI Refactoring (Weeks 5-6)

• Consolidate to unified CLI architecture
• Isolate AI logic for portability
• Configure build pipeline (TypeScript → dist/)

Phase 7-8: Validation & Launch (Weeks 7-8)

• Unit tests (80%+ coverage) and integration tests
• Comprehensive README with examples
• Register in .claude-plugin/marketplace.json

Success Criteria

• All 5 commands functional with proper error handling
• 2+ agents operational with JSON contracts
• Cross-platform CLI with committed dist/
• Schema-validated configuration system
• Complete documentation with troubleshooting guide

Risk Mitigation

• Incompatibility: Incremental refactoring, thorough spec-kit analysis
• Scope creep: MVP-first, defer code generation to v2.0
• Performance: Appropriate model selection, caching strategies

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Roadmap: Claude Code Plugin Adaptation from spec-kit</issue_title>
<issue_description>## Objective
Create a plan to convert the GitHub spec-kit repository into a Claude Code plugin, with actionable steps for integration and refactoring in the retsohuang/retso-marketplace repository.

Proposed Steps

1. Analyze Claude Code Plugin System

   • Review official Claude Code plugin documentation for implementation standards.
   • Identify plugin lifecycle, required files, and integration constraints.

2. Audit Existing CLI & Logic

   • Catalog the workflows, commands, and dependencies of spec-kit.
   • Flag any platform-specific or agent logic for refactor.

3. Map Command Set to Plugin Actions

   • List which CLI commands will become plugin actions—prioritize planning/spec creation and documentation sync.
   • Suggest Claude plugin commands (e. g., /specify, /spec-plan).

4. Refactor & Unify CLI Module

• Consolidate scripts to a unified Bun/Node.js CLI as future-proof architecture.
• Isolate AI/agent-specific logic for portability.

5. Manifest & Metadata Implementation

• Create plugin manifest and descriptors for Claude recognition.
• Ensure all plugin actions are testable and discoverable.

6. Testing, Docs, Feedback

• Draft installation, usage and troubleshooting docs for marketplace users.
• Create validation tests and seek community input for iterative improvement.

Notes

• Tag as enhancement, add documentation if repository conventions suggest this.
• Assignee: retsohuang
• Aligns with prior plans and marketplace refactor initiatives.

---

For more details, see original discussions in spec-kit and Claude plugin docs.</issue_description>

Comments on the Issue (you are @copilot in this section)

Custom agent used: create-plugin
Guide users through creating Claude Code plugins with commands, agents, hooks, and MCP configurations following best practices.

• Fixes Roadmap: Claude Code Plugin Adaptation from spec-kit #2

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[retsohuang]

@copilot Start implement

[Copilot]

@copilot Start implement

I've created a comprehensive 8-phase roadmap for converting spec-kit into a Claude Code plugin. However, to begin implementation, I'll need:

1. Access to the spec-kit repository - To audit existing CLI commands, workflows, and dependencies (Phase 1.2)
2. Additional tools - File system operations (creating directories, files) and command execution capabilities

The roadmap is complete and ready in the PR description. The next actionable steps are:

Immediate Next Steps:

• Phase 1.2: Audit spec-kit repository (need repo access)
• Phase 4.1: Create plugins/spec-kit/ directory structure
• Phase 4.2: Generate plugin.json manifest

What I can provide now:
I can create the detailed content for plugin files (plugin.json, command.md files, agent.md files, config-schema.json, etc.) if you'd like me to specify them in comments or documentation.

Would you like me to:

1. Provide the complete file content specifications for all plugin components?
2. Wait for additional tooling/repository access to create the files directly?
3. Create a detailed implementation guide document you can follow manually?