workflow-new-skill

Automating scaffolding for new Volon plugin skills involves generating idempotent markdown artifacts, SKILL.md drafts, and task files across ideation, requirements, spec, plan, and bootstrap finalization stages. It ensures consistent plugin directory structures without manual file creation.

Idempotent task creation in plugin development workflows means skipping existing artifacts and validating plugin.json registration updates to prevent duplicate or overwritten files. This ensures repeated executions produce the same state without corrupting previously generated skill specifications or plans.

Generating SKILL.md and task files for Volon plugins requires running a guided workflow with a quoted skill name and target plugin. The process drafts specifications, creates execution-ready task files, updates plugin registration, and refreshes the Project Context Cache (PCC).

Skill authoring works with existing plugin.json registrations by validating updates rather than overwriting them. The workflow enforces idempotency, skipping existing artifacts and safely integrating new skill capabilities into current plugin configurations while respecting disable-model-invocation settings.

The best way to onboard contributors to Volon plugin development is using a guided workflow that automates ideation through bootstrap finalization. It produces standardized requirements, specs, plans, and task files, ensuring all contributors follow identical scaffolding processes.

Your new skill workflow skips existing markdown artifacts to enforce idempotency, preventing accidental overwrites of prior ideation, requirements, or specification files. This design safeguards completed workflow stages during repeated plugin development executions.