workflow-new-plugin
Guided workflow for creating a new Volon plugin — ideation, requirements, spec, plan, tasks.
Best use case
workflow-new-plugin is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Guided workflow for creating a new Volon plugin — ideation, requirements, spec, plan, tasks.
Teams using workflow-new-plugin should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/workflow-new-plugin/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How workflow-new-plugin Compares
| Feature / Agent | workflow-new-plugin | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Guided workflow for creating a new Volon plugin — ideation, requirements, spec, plan, tasks.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Workflow: New Plugin Drive an agent through the full new-plugin definition lifecycle. Produces a spec artifact and implementation tasks including the plugin scaffold and `plugin.json`. Idempotent: skip any stage whose output artifact already exists. Stage protocols live in `stages/stage-N-*.md`. --- ## Arguments - `$0` (required): plugin name — quoted string, e.g. `"integrations"` --- ## Step 1 — Preflight Run: !`cat volon.yaml 2>/dev/null || cat .volon/volon.yaml 2>/dev/null || echo "NO_CONFIG"` Extract and note: - `project.name` → used in all artifact frontmatter - `workflows.new_plugin.enabled` → if `false`: output `workflow-new-plugin is disabled in volon.yaml.` and stop. If `$0` is absent: output `ERROR: plugin name is required.` and stop. Invoke `pcc-refresh` (scope=all). Read `plugins/` directory listing to check for name collision. If `plugins/<SLUG>/` already exists: output `ERROR: plugin directory plugins/<SLUG>/ already exists.` and stop. Run: !`date +%Y-%m-%d` Capture today's date as `TODAY`. **Derive slug:** Run: !`echo "$0" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/-\+/-/g' | sed 's/^-\|-$//g'` Capture result as `SLUG`. Artifact ID = `plugin-<TODAY>-<SLUG>`. Execute stages in sequence: - Stage 2: `stages/stage-2-ideation.md` - Stage 3: `stages/stage-3-requirements.md` - Stage 4: `stages/stage-4-spec.md` - Stage 5: `stages/stage-5-plan.md` - Stage 6: `stages/stage-6-tasks.md` --- ## Step 7 — Finalize Invoke `/bootstrap-update`. Ensure `.volon/bootstrap.md` and a history copy exist before completing. Output `DONE`. --- ## Invariants - Never create an artifact or plugin directory that already exists — check first, skip if present. - All artifact frontmatter must use the schema from `docs/03_workflow-contracts.md`. - All shell commands use `!` prefix. - Output `DONE` only after Step 7 completes.
Related Skills
writing-opencode-plugins
Guides development of OpenCode plugins including project structure, testing patterns, and publishing. Use when creating or modifying OpenCode plugins.
workflow-status
Display project workflow progress by reading handoff documents in .docs/ directory. This skill should be used when users want to check their workflow status, see what phase they're in, or when other workflow skills need to verify prerequisites. Provides reusable prerequisite-checking templates for integration with other workflow skills.
workflow-integration-git
Git commit workflow with conventional commits, artifact cleanup, and optional push/PR creation
workflow-guide
Provides guidance on Cursor ↔ Claude Code 2-agent workflow. Use when user mentions ワークフローについて, Cursorとの連携, 作業の流れ, 2-agent workflow, collaboration. Do NOT load for: 実装作業, ワークフロー設定, ハンドオフ実行.
workflow-creator
Create complete Claude Code workflow directories with curated skills. Use when user wants to (1) create a new workflow for specific use case (media creator, developer, marketer, etc.), (2) set up a Claude Code project with pre-configured skills, (3) download and organize skills from GitHub repositories, or (4) generate README.md and AGENTS.md documentation for workflows. Triggers on phrases like "create workflow", "new workflow", "set up workflow", "build a xxx-workflow".
update-tool-plugin
Update an existing LNAI tool plugin
testing-workflow
Integrated testing workflow combining all testing tools and MCPs. Use when deciding which testing tools to use, planning testing strategy, or executing tests in different environments and phases. Tags official skills: wallaby-testing, web-browser, agent-browser. Triggers on "testing workflow", "which test tool", "testing strategy", "run tests", "test combination".
spec-workflow-orchestrator
Orchestrate comprehensive planning phase from ideation to development-ready specifications using 4 specialized agents
setup-workflow
Initial setup workflow for claude-pilot plugin - directory creation, statusline configuration, documentation sync, GitHub star request
rollback-workflow-builder
Creates safe rollback procedures for deployments with automated workflows, rollback runbooks, version management, and incident response. Use for "rollback automation", "deployment recovery", "incident response", or "production rollback".
raw-workflow-creator
Create and run RAW workflows. Use this skill when the user asks to create a workflow, automate a task, build a data pipeline, generate reports, or asks "How do I build X with RAW?".
pytest-plugins
Use when pytest plugin ecosystem including pytest-cov, pytest-mock, and custom plugin development.