Skip to content
Back to skills

Workflow New Plugin

ASecurity

Guided workflow for creating a new Volon plugin — ideation, requirements, spec, plan, tasks.

  • 57 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 17, 2026
toolsshell

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add diegosouzapw/awesome-omni-skill --skill workflow-new-plugin --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Workflow New Plugin?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Workflow New Plugin
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/diegosouzapw-workflow-new-plugin/badge)](https://www.skillsdirectory.com/skills/diegosouzapw-workflow-new-plugin)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: workflow-new-plugin
description: Guided workflow for creating a new Volon plugin — ideation, requirements, spec, plan, tasks.
argument-hint: ""plugin-name""
disable-model-invocation: true
---

# 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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.