workflow-new-agent

Automate Volon agent role artifact creation with idempotent stage-based steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the manual, error-prone process of designing and documenting new Volon agent roles by producing consistent, stage-based artifacts (purpose, scope, context, interface, plan, tasks) and integrating them into the project's PCC and bootstrap state.

Core Features & Use Cases

  • Produces one artifact per lifecycle stage with idempotent checks to avoid overwriting existing work.
  • Reads project metadata (volon.yaml, .volon/agent-boot.md) and updates bootstrap/state via PCC refresh and bootstrap-update.
  • Generates role addenda, interface specs, implementation plans, and task files following the project's workflow contracts.
  • Use case: onboarding a new automated worker or reviewer agent with standardized documentation, task breakdowns, and orchestrator-ready outputs.

Quick Start

Run the workflow-new-agent skill with the agent name in quotes to generate staged artifacts and tasks for a new Volon agent.

Frequently Asked Questions about workflow-new-agent

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

FAQPage Schema
How do I define new agent roles in Volon workflows?

To define new agent roles in Volon workflows, you generate stage-based artifacts for purpose, scope, context, interface, plan, and tasks. This automated approach ensures reproducible role design by applying idempotent steps that conform to project workflow contracts.

What are idempotent agent artifacts and why do they matter?

Idempotent agent artifacts are documentation and task files generated safely without overwriting existing work. They matter because applying idempotent checks during stage-based generation prevents duplicate artifacts when defining or updating automated worker roles in a Volon development workflow.

How do I create an automated worker agent with standardized documentation?

You create an automated worker agent by running a stage-based generation process that produces role addenda, interface specs, implementation plans, and task files. This yields orchestrator-ready documentation while automatically refreshing the PCC and updating bootstrap state.

Does defining a new Volon agent require updating bootstrap state manually?

Defining a new Volon agent does not require updating bootstrap state manually. The generation process automatically reads project metadata like volon.yaml and updates the bootstrap state via PCC refresh, ensuring the new role integrates seamlessly without manual state tracking.

What is the best way to avoid duplicate artifacts when onboarding a reviewer agent?

The best way to avoid duplicate artifacts when onboarding a reviewer agent is using idempotent, stage-based generation. This method checks existing work before producing purpose, scope, and task files, ensuring artifacts are never overwritten and the PCC remains clean.