@innotech-ai/claude-plugin
v0.1.14
Published
InnoTech SDLC workflow commands for Claude Code — native /innotech:* commands (innotech-setup, create-document, generate-image, analyze, plan, execute, fix, merge, deploy, move-to-qa) over the InnoTech MCP server.
Maintainers
Readme
@innotech-ai/claude-plugin
InnoTech SDLC workflow commands for Claude Code — native /innotech:* slash commands driven through the InnoTech MCP server.
Cloud (server Web Agent) by default; -here variants run locally in your Claude Code session. Claude reviews and corrects the result after every action.
Install (per-user)
/plugin marketplace add https://innotech.ai/plugin
/plugin install innotech@innotech-aiRestart Claude Code, approve the InnoTech OAuth sign-in on first connect (no API key), then run /innotech:innotech-setup in your repo.
Full guide: https://innotech.ai/claude
Commands
/innotech:innotech-setup · /innotech:create-document · /innotech:generate-image · /innotech:analyze · /innotech:plan · /innotech:execute · /innotech:fix · /innotech:merge · /innotech:move-to-qa · /innotech:deploy — each SDLC command also has a local -here variant.
/innotech:investigate — diagnose bugs, integrations, or env issues with a small ephemeral script (.env / staging.env / prod.env; no secrets exposed). Investigate before fixing.
/innotech:create-innotech-task — capture the current session's AI work into a reviewable task (goal, requirements, changes, PR/branch/preview) and route it to a human developer or QA. Also creates an ordinary task.
Security
- Authentication is OAuth (browser sign-in); no API keys for everyday use.
.envvalues are never shown to the model — the setup env-sync helper reads the file locally and uploads only missing keys.- Never pushes to protected branches (master/main/develop/staging).
