workflow-new-slash-command

Generate specification and task artifacts for new Volon slash commands.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/hollis-labs/volon --skill workflow-new-slash-command
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-new-slash-command
Source: https://github.com/hollis-labs/volon/tree/main/plugins/workflows/skills/workflow-new-slash-command
Command: npx skills add https://github.com/hollis-labs/volon --skill workflow-new-slash-command

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides developers through the end-to-end definition, specification, and tasking of a new user slash command so teams can consistently design, document, and implement commands without manual checklist drift.

Core Features & Use Cases

  • Structured lifecycle: Idempotent stages for ideation, requirements, spec, plan, and task creation that produce repository-local artifacts.
  • Safe integration: Checks for name collisions in docs/09_commands.md, refreshes project context (PCC), and finalizes changes with a bootstrap update.
  • Use case: A contributor needs to add /task-search to the Volon plugin ecosystem; this workflow produces the spec, updates docs, and creates implementation tasks.

Quick Start

Run the workflow-new-slash-command skill with the desired command name to generate ideation, requirements, spec, plan, and tasks for that slash command.

Frequently Asked Questions about workflow-new-slash-command

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a specification for a new slash command?

To create a specification for a new slash command, you need a structured workflow that generates ideation, requirements, specs, plans, and tasks. This process produces repository-local artifacts to design and implement commands without manual checklist drift.

What is the best way to add a new command to a Volon plugin repository?

The best way to add a new command to a Volon plugin repository is using an end-to-end workflow that finalizes changes with a bootstrap update. It refreshes project context and orchestrates safe integration into the existing ecosystem.

How do I check for slash command name collisions in project documentation?

Checking for slash command name collisions involves verifying new command names against docs/09_commands.md. This prevents naming conflicts during command specification and ensures safe integration into the repository-maintained plugin ecosystem.

Can I generate implementation tasks for slash commands with structured frontmatter?

Yes, you can generate implementation tasks for slash commands with structured frontmatter. The workflow creates structured task artifacts complete with required frontmatter metadata during the task creation stage of the lifecycle.