Design: Claude Code Plugin structure for nabledge-6

[kiyotis]

Summary

This PR proposes a comprehensive design for restructuring nabledge-6 skill as a proper Claude Code Plugin for distribution, based on the official Claude Code Plugin specification.

Problem

The current nabledge-6 skill structure (.claude/skills/nabledge-6/) is designed for local development but does not conform to Claude Code Plugin distribution requirements:

• ❌ No plugin.json manifest
• ❌ Components inside .claude/skills/ (not at plugin root)
• ❌ Not distributable as standalone plugin

Proposed Solution

Recommended: Option 1 - Dedicated Plugin Repository

Create a separate nabledge-6 repository with proper plugin structure:

nabledge-6/                        # Plugin root
├── .claude-plugin/
│   └── plugin.json                # Manifest
├── skills/
│   └── nabledge-6/
│       └── SKILL.md
├── workflows/                     # At root
├── assets/                        # At root
├── knowledge/                     # At root
├── docs/                          # At root
├── README.md
├── LICENSE
└── CHANGELOG.md

Key Design Decisions

1. Dedicated repository: Separate development (nabledge-dev) from distribution (nabledge-6)
2. Plugin root structure: All component directories at root level, not inside .claude-plugin/
3. Namespaced skills: Users invoke with /nabledge-6 (plugin name matches skill name)
4. Git-based distribution: Users install via /plugin marketplace add owner/nabledge-6

File Mapping

Development	Distribution
.claude/skills/nabledge-6/SKILL.md	skills/nabledge-6/SKILL.md
.claude/skills/nabledge-6/workflows/	workflows/ (at root)
.claude/skills/nabledge-6/knowledge/	knowledge/ (at root)

Implementation Options Considered

1. ✅ Option 1: Dedicated Repository (Recommended)
2. ⚠️ Option 2: Monorepo with dist/ directory
3. ⚠️ Option 3: CI/CD build pipeline

See full analysis in work/20260212/plugin-structure-design.md

Next Steps

1. Get feedback on recommended approach
2. Answer questions (repository name, license, author info)
3. Create nabledge-6 plugin repository
4. Implement plugin structure
5. Test locally with claude --plugin-dir
6. Publish to GitHub

Questions for Review

1. Repository naming: nabledge-6 or claude-plugin-nabledge-6?
2. License: Apache 2.0 or MIT?
3. Sync strategy: Manual or automated (GitHub Actions)?
4. Marketplace submission: Plan to submit to official Claude Code marketplace?

References

• Design document: work/20260212/plugin-structure-design.md
• Claude Code Plugin specification (investigated via claude-code-guide agent)

🤖 Generated with Claude Code

[kiyotis]

not existsは都度生成せずスキルの中にpluginディレクトリ作ってその中に入れて、開発時に編集しませんか？
nabledge-6/plugin/plugin.jsonといった感じです。
開発時に付随するファイルもレビューしたいですよね。

そうすれば都度生成でなく適切な場所に移動すればいいだけになります。

[kiyotis]

Fixed

Commit: e5d840d

Updated the design document to store plugin distribution files (plugin.json, README.md, LICENSE, CHANGELOG.md) in .claude/skills/nabledge-6/plugin/ directory within the development repository, rather than generating them during GitHub Action workflow.

Changes made:

• Updated development structure to include plugin/ directory
• Updated File Mapping table to show moving files instead of generating
• Simplified workflow steps (removed generation steps)
• Updated version management strategy
• Updated implementation checklist

This approach enables reviewing plugin files during development and simplifies the workflow.

Co-Authored-By: Claude (jp.anthropic.claude-sonnet-4-5-20250929-v1:0) noreply@anthropic.com

[kiyotis]

Closing this PR. New implementation approach will be submitted in a separate PR.