conductor

Automate project initialization, spec creation, and plan formation for software tracks.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/edithatogo/conductor-next --skill conductor-edithatogo
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: conductor
Source: https://github.com/edithatogo/conductor-next/tree/main/skill
Command: npx skills add https://github.com/edithatogo/conductor-next --skill conductor-edithatogo

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes scripts (resource) components.

What problem does it solve?

Conductor provides a structured, repeatable workflow for AI agents to manage software projects: establish context, craft a precise spec and plan, and execute implementations with governance. It reduces miscommunication, accelerates delivery, and enforces a disciplined development lifecycle.

Core Concepts

  • Track: A unit of work (feature or bug fix) with its own spec.md and plan.md
  • Spec: Detailed requirements document (spec.md)
  • Plan: Phased task list with checkboxes (plan.md)
  • Workflow: Rules for task lifecycle, TDD, commits, and quality gates

Directory Structure

conductor/ β”œβ”€β”€ product.md β”œβ”€β”€ product-guidelines.md β”œβ”€β”€ tech-stack.md β”œβ”€β”€ workflow.md β”œβ”€β”€ tracks.md β”œβ”€β”€ code_styleguides/ β”œβ”€β”€ tracks/ β”‚ └── <track_id>/ β”‚ β”œβ”€β”€ metadata.json β”‚ β”œβ”€β”€ spec.md β”‚ └── plan.md └── archive/

Quick Start

Initialize Conductor in your project to create a new track with a spec and plan.

Frequently Asked Questions about conductor

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

FAQPage Schema
How do I automate project initialization and spec creation for AI coding tracks?β–Ό

Automate project initialization and spec creation by defining a context-driven track with metadata, a detailed spec.md, and a phased plan.md. This establishes a structured workflow enforcing task lifecycle governance and TDD for software delivery.

What is context-driven project management for software tracks?β–Ό

Context-driven project management structures AI coding into tracks containing specs and plans. It governs the development lifecycle through automated initialization, status checks, and reverts, reducing miscommunication and enforcing disciplined execution.

Can I use this context-driven workflow to manage both feature development and bug fixes?β–Ό

Yes, the workflow applies to both feature development and bug fixes. It treats each unit of work as a track with its own spec.md and plan.md, applying governance rules and quality gates across the entire software development lifecycle.

What's the best way to structure plans and specs for AI coding agents?β–Ό

Structure specs and plans using a dedicated directory hierarchy containing product.md, workflow.md, and track-specific folders. Each track requires metadata.json, spec.md for requirements, and plan.md for phased task lists.

Do I need a specific file format to set up context-driven project management?β–Ό

You need a SKILL.md frontmatter containing the name and description to initialize. The system then generates the required directory structure, including metadata.json, spec.md, and plan.md files, optionally referencing scripts to extend functionality.

Why does context-driven track management require separate spec and plan documents?β–Ό

Separate spec and plan documents isolate detailed requirements from phased task lists. This separation ensures AI coding agents execute implementations with precise context, applying governance rules and quality gates without miscommunication.