From the StackShift repository directory:
./install-local.shOr manually:
# Create local plugins directory
mkdir -p ~/.claude/plugins/local
# Symlink this directory
ln -s $(pwd) ~/.claude/plugins/local/stackshift
# Restart Claude Code- Restart Claude Code completely
- Navigate to a project you want to analyze
- Start a new conversation
- Say:
"Analyze this codebase" - The
analyzeskill should auto-activate!
Try these trigger phrases:
# Step 1
"Analyze this codebase"
"Run initial analysis"
# Step 2
"Reverse engineer the codebase"
"Extract business logic"
# Step 3
"Create specifications"
"Set up GitHub Spec Kit"
# Step 4
"Analyze gaps"
"Run speckit analyze"
# Step 5
"Complete the specification"
"Resolve clarifications"
# Step 6
"Implement missing features"
"Use speckit to implement"
# See current progress (which gear you're in)
node ~/.claude/plugins/local/stackshift/plugin/scripts/state-manager.js status
# See detailed progress
node ~/.claude/plugins/local/stackshift/plugin/scripts/state-manager.js progress
# Check which route you chose
node ~/.claude/plugins/local/stackshift/plugin/scripts/state-manager.js get-pathOnce the repository is public and configured:
# Add the marketplace
> /plugin marketplace add jschulte/claude-plugins
# Install StackShift
> /plugin install stackshift
# Restart Claude Code> /plugin list
# Should show: stackshift (installed)To make your plugin available to all Claude Code users:
- GitHub repository must be public
- Repository must have proper structure ✅ (already done)
- README with clear documentation ✅ (already done)
- License file (need to add)
- Working plugin ✅ (already done)
# Choose a license (MIT is common for open source)
cat > LICENSE <<'EOF'
MIT License
Copyright (c) 2024 Jonah Schulte
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
EOF
git add LICENSE
git commit -m "docs: add MIT license"
git push origin mainOn GitHub:
- Go to repository Settings
- Scroll to "Danger Zone"
- Click "Change visibility" → "Make public"
- Confirm
# Tag the current version
git tag -a v1.0.0 -m "Release v1.0.0: Reverse Engineering Toolkit Claude Code Plugin
Features:
- 6 interactive skills for reverse engineering
- Dual workflow (greenfield/brownfield)
- GitHub Spec Kit integration
- State management and progress tracking
- Auto-activation based on natural language"
# Push the tag
git push origin v1.0.0On GitHub:
- Go to "Releases" → "Create a new release"
- Choose tag:
v1.0.0 - Title:
v1.0.0 - Initial Release - Description:
/plugin marketplace add jschulte/claude-plugins /plugin install reverse-engineering-toolkit
## Reverse Engineering Toolkit v1.0.0 Transform any partially-complete application into a fully-specified, enterprise-grade, spec-driven codebase using GitHub Spec Kit. ### Features - 🎯 Two paths: Greenfield (tech-agnostic) or Brownfield (tech-prescriptive) - 🤖 6 interactive skills with auto-activation - 📊 Progress tracking and state management - 🔗 Full GitHub Spec Kit integration - 📝 3,400+ lines of comprehensive documentation ### Installation
See README for detailed usage instructions. - Publish release
The official submission process typically involves:
-
Fork the Claude Code marketplace repository (if there is one)
- Check: https://github.com/anthropics/claude-code-marketplace (or similar)
-
Add your plugin to the registry
- Add entry pointing to your repository
- Include marketplace.json metadata
-
Submit Pull Request
- PR to marketplace repository
- Wait for review and approval
Alternative: Check Claude Code documentation for official marketplace submission:
# In Claude Code
> /help pluginsOr visit: https://code.claude.com/docs (check for marketplace submission process)
# Check if symlink exists
ls -la ~/.claude/plugins/local/
# Should show: stackshift -> /path/to/your/repo
# If not there, re-run install
./install-local.sh- Restart Claude Code completely (not just new conversation)
- Check plugin loaded:
> /plugin list - Try explicit phrases:
"Run the analyze skill" "Use the reverse-engineer skill"
# Make sure it's executable
chmod +x plugin/scripts/state-manager.js
# Test it
node plugin/scripts/state-manager.js initIf skills don't auto-activate, use the prompts manually:
# After choosing path
cat prompts/greenfield/02-reverse-engineer-business-logic.md
# or
cat prompts/brownfield/02-reverse-engineer-full-stack.mdOnce installed:
-
Navigate to a project:
cd /path/to/your/project -
Start Claude Code
-
Begin the process:
"I want to reverse engineer this application" -
Choose your route:
- Greenfield: Shift to new tech stack
- Brownfield: Take the wheel on existing code
-
Shift through the gears!
StackShift will guide you through all 6 gears automatically.
Before publishing to marketplace:
- Plugin structure complete
- Skills documented
- README comprehensive
- LICENSE file added
- v1.0.0 release created
- Repository is public
- Tested locally
- Submitted to marketplace
- Repository: https://github.com/jschulte/reverse-engineering-toolkit
- Issues: https://github.com/jschulte/reverse-engineering-toolkit/issues
- Claude Code Docs: https://code.claude.com/docs
- GitHub Spec Kit: https://github.com/github/spec-kit
Want me to help you:
- Add the LICENSE file?
- Create the v1.0.0 release?
- Make the repository public?
- Test the plugin locally first?