sidequest

Coordinate agent-driven software work through tickets, routing, and verified commits.

15|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Eigenwise/eigenwise-toolshed --skill sidequest-eigenwise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sidequest
Source: https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/sidequest/skills/sidequest
Command: npx skills add https://github.com/Eigenwise/eigenwise-toolshed --skill sidequest-eigenwise

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Sidequest solves the problem of coordinating substantial development work across one or more agents without losing track of scope, ownership, verification, or integration status.

Core Features & Use Cases

  • Ticket-based execution: Create, classify, claim, update, and close tickets for bugs, features, investigations, and releases.
  • Parallel orchestration: Split larger work into waves, link dependencies, and dispatch independent executors safely.
  • Board-first workflow: Use the dashboard, comments, stories, reminders, assignments, and attachments to keep execution durable and visible.
  • Routing and verification: Route work to the correct model and effort, then submit verified commits for later integration.
  • Use case: A developer needs to refactor several files and ship them safely; Sidequest can break the work into scoped tickets, route each piece, track progress, and publish the integrated result.

Quick Start

Use the sidequest skill to create and route a ticket for the requested change, then dispatch the right executor and verify the result on the board.

Frequently Asked Questions about sidequest

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

FAQPage Schema
How do I orchestrate multi-step development work across multiple agents without losing track of scope?

Software work routing is handled by classifying tickets and directing them to the correct model and effort level. The system then submits verified commits for later integration, ensuring exact verification commands are met before publishing results.

How do I route development tickets to the right executor and verify the commits?

Development tickets are routed by classifying the requested change and directing it to the correct model and effort level. The system then submits verified commits for later integration, ensuring exact verification commands are met before publishing results.

Can I split a large refactoring task into parallel waves with dependency tracking?

Yes, large refactoring tasks can be split into parallel execution waves. The orchestration system links dependencies between scoped tickets, dispatches independent executors safely, and tracks progress on a board to publish the integrated result.

What is the best way to track bug fixes and feature investigations using a kanban board?

Tracking bug fixes and investigations is best handled through a board-first workflow with tickets, comments, stories, and assignments. This keeps execution durable and visible, allowing agents to claim, update, and close work items efficiently.

Does agent-driven ticket orchestration work for release workflows that require integration control?

Yes, agent-driven ticket orchestration applies to release workflows needing integration control. It coordinates routing projections and verified commits, ensuring durable scope and dependency tracking are maintained throughout the investigation, review, and release process.