volon-task

Operate the volon task CLI to manage markdown-based tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures reliable, deterministic management of repo-scoped tasks by standardizing how agents and humans create, transition, and inspect tasks while keeping markdown files as the single source of truth. It prevents unsafe direct edits to supporting caches and enforces guardrails around single-writer transitions and repository-aware command execution.

Core Features & Use Cases

  • Create canonical task files: Use the CLI to generate new .volon/tasks markdown files with the required frontmatter.
  • Deterministic state transitions: Move tasks through lifecycle states (todo → doing → done) with idempotent commands and appended update history.
  • Listing and inspection: Query and show tasks without manually grepping the tasks directory.
  • Cache maintenance: Rebuild or reindex the SQLite cache after manual edits, schema changes, or corruption.
  • Use Case: An agent finishing a task runs volon task done <id> from the repo root, which appends the update and avoids touching the underlying Nanite databases.

Quick Start

Run the volon task create "Your Task Title" command from the repository root to add a new markdown task with canonical frontmatter.

Frequently Asked Questions about volon-task

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

FAQPage Schema
How do I manage markdown-based task lifecycles in a repository workflow?

Manage markdown-based task lifecycles by using a task command-line tool to create, start, and complete tasks. It enforces deterministic state transitions while keeping markdown files as the single source of truth for repository-scoped task state.

Can I edit the SQLite task cache directly to update task states?

You should not edit the SQLite task cache directly. Direct database edits bypass safety guardrails; instead, use the command-line tool to perform single-writer state transitions and run the reindex command after manual or schema changes to rebuild the cache.

What is the best way to create canonical task files with required frontmatter?

The best way to create canonical task files is running the task creation command from the repository root. This generates new markdown files under the tasks directory automatically populated with the required frontmatter for deterministic tracking.

How do I rebuild the SQLite task cache after manual markdown edits?

Rebuild the SQLite task cache by running the reindex command from the repository root. This synchronizes the supporting cache with manual markdown changes, schema updates, or corruption while preserving markdown as the authoritative source.

Why does single-writer task transition matter for deterministic task management?

Single-writer task transitions matter because they enforce deterministic state changes and prevent race conditions. By standardizing how agents move tasks through lifecycle states, the system appends update history reliably without conflicting direct edits.

Does the task CLI need to run from the repository root?

The task CLI requires running from the repository root to correctly locate the task files, or you must explicitly pass the repository path. This ensures the command operates on the correct repository-scoped markdown files for task management.