Swarm Manager Backlog Tools

Define canonical backlog folder layouts, artifact schemas, and CLI commands.

54|7|Updated Sep 19, 2021
One-click install
npx skills add https://github.com/Vrooli/Vrooli --skill swarm-manager-backlog-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Swarm Manager Backlog Tools
Source: https://github.com/Vrooli/Vrooli/tree/main/scenarios/prompt-manager/store/skills/packs/core/swarm-manager-backlog-tools
Command: npx skills add https://github.com/Vrooli/Vrooli --skill swarm-manager-backlog-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing swarm-manager backlog items reveals so many folder layout, metadata, and CLI inconsistencies that executing or auditing work becomes error prone. This reference centralizes the canonical structure, schemas, and reading order so every agent follows the same authoritative guidance.

Core Features & Use Cases

  • Canonical Folder Layout: Documents the spec.json, plan.md, workshop, research, archive, and optional handoff structures along with who owns each artifact.
  • Artifact Schemas & CLI Guidance: Provides the spec.json schema, workshop round structure, research template guidance, and the full swarm-manager command catalog for listing, creating, updating, queuing, and inspecting backlog items.
  • Decision Authority & Troubleshooting Rules: Explains the refinement hierarchy, dependency and acceptance pattern rules, mutation permissions, and how to handle missing artifacts or unresolved decisions.

Quick Start

Use the backlog tools reference to list the expected files, allowed CLI commands, and decision hierarchy for any backlog item before beginning work.

Frequently Asked Questions about Swarm Manager Backlog Tools

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

FAQPage Schema
How do I standardize backlog artifact structure for consistent execution?

Backlog workflow inconsistencies are resolved by centralizing artifact schemas, reading order, and mutation rules into a single reference, ensuring every swarm-manager agent operates on idea, research, fix, and chore items identically.

What CLI commands are available for managing swarm-manager backlog items?

Available CLI commands for backlog workflows include listing, creating, updating, queuing, and inspecting items, operating across idea, research, fix, execute, and chore directories to manage the full backlog lifecycle.

How do I handle missing artifacts or unresolved decisions in backlog workflows?

Missing artifacts and unresolved decisions are handled by consulting the documented troubleshooting rules and refinement hierarchy, which dictate mutation permissions and decision authority across backlog item directories.

What is the correct folder layout for a backlog item directory?

A canonical backlog folder layout contains spec.json, plan.md, workshop, research, archive, and optional handoff structures, with each artifact having a clearly defined owner to maintain consistent execution.

Can I use this reference for both research and chore item workflows?

Yes, the reference applies to swarm-manager agents operating on idea, research, fix, execute, and chore item directories, providing artifact schemas and interaction patterns for all backlog types.

Why does my backlog execution fail due to metadata inconsistencies?

Backlog execution becomes error-prone when folder layout, metadata, and CLI inconsistencies exist; centralizing canonical artifact schemas and reading order prevents these execution and auditing errors.