conductor

Plan, track, and execute software work using project context and tracks.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/quanhavn/workflow-skills --skill conductor-quanhavn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conductor
Source: https://github.com/quanhavn/workflow-skills/tree/main/conductor
Command: npx skills add https://github.com/quanhavn/workflow-skills --skill conductor-quanhavn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Conductor provides a context-aware framework to plan, track, and execute software work by loading project context, organizing work into tracks and specs, and coordinating with a memory layer for cross-session continuity.

Core Features & Use Cases

  • Context loading: automatically pulls product vision, tech stack, workflow guidelines, and track data to align AI reasoning with the current project state.
  • Track orchestration: creates and manages specs, plans, learnings, and patterns to enable phased delivery and institutional knowledge.
  • Beads integration: optionally connects with the Beads memory system to persist task state across sessions and support cross-track context.
  • Parallel execution: coordinates parallel tasks with dependency awareness to improve throughput.

Quick Start

Use the conductor skill to bootstrap a new project context and prepare an initial track plan.

Frequently Asked Questions about conductor

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

FAQPage Schema
How do I coordinate parallel code execution with context-driven tracks?

Parallel code execution is coordinated by organizing work into tracks with dependency awareness, ensuring clear task ownership and improved throughput while aligning AI reasoning with current project state.

How does spec-first planning work for software project setup?

Spec-first planning works by creating and managing specs, plans, and patterns within tracks to enable phased delivery and institutional knowledge, pulling product vision and tech stack data to align AI reasoning with the project.

Can I use TDD workflows with the Beads memory system for cross-session continuity?

Yes, TDD workflows are supported through active implementation phases, while Beads integration optionally connects to persist task state across sessions and support cross-track context continuity.

What's the best way to bootstrap a new project context and prepare an initial track plan?

Bootstrapping a new project context involves loading product vision, tech stack, workflow guidelines, and track data, then organizing work into tracks and specs to prepare an initial plan for phased delivery.

Does context-driven development require loading artifacts from product and tech-stack sources?

Yes, context-driven development requires automatically pulling product, tech-stack, workflow, and track artifacts to align AI reasoning with the current project state before orchestrating tracks and executing software work.

Why use tracks and patterns for software work coordination instead of standard task lists?

Tracks and patterns enable institutional knowledge retention and phased delivery by organizing specs and learnings, whereas standard task lists lack integrated context loading and dependency-aware parallel execution coordination.