conductor-workflow

Coordinate track-based feature development from spec to task execution.

17|24|Updated Dec 29, 2018
One-click install
npx skills add https://github.com/chimon2000/good_first_issue --skill conductor-workflow
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: conductor-workflow
Source: https://github.com/chimon2000/good_first_issue/tree/main/.augment/skills/conductor-workflow
Command: npx skills add https://github.com/chimon2000/good_first_issue --skill conductor-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conductor Workflow provides a structured methodology to organize work into tracks, guiding teams with specs, plans, and disciplined commits, reducing chaos in feature development.

Core Features & Use Cases

  • Plan before you code β€” Start with a spec and an implementation plan before coding.
  • Atomic commits β€” Each task yields a single, well-scoped commit to keep history clean.
  • Track isolation β€” Tracks are independent units of work with clear boundaries.
  • Master guidance β€” Use conductor/index.md as the master manifest to navigate product structure.
  • Use Case: Teams adopt this workflow to coordinate multiple tracks from spec to plan to task execution.

Quick Start

Initialize Conductor in your project by reading conductor/index.md and starting a new track with /conductor:new-track <feature>.

Frequently Asked Questions about conductor-workflow

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

FAQPage Schema
How do I organize feature development into tracks to reduce coding chaos?β–Ό

Track-based development organizes feature work into independent tracks with clear boundaries, using specs, plans, and disciplined atomic commits. This structured methodology reduces chaos by guiding teams from spec to plan to task execution.

What is the best way to enforce plan-first and atomic commits in a software project?β–Ό

Plan-first and atomic commits are enforced by starting with a spec and implementation plan before coding, ensuring each task yields a single, well-scoped commit. This approach keeps history clean and progress structured.

How do I start a new track for a feature using Conductor?β–Ό

To start a new track, initialize Conductor in your project by reading the conductor/index.md master manifest, then use the /conductor:new-track command with your feature name to begin structured task execution.

Does this track-based workflow require a master manifest to navigate product structure?β–Ό

Yes, track-based workflow requires a master manifest at conductor/index.md to navigate product structure. This file guides teams through track specs, plans, and commit conventions across the software project.

Can I use Conductor workflow for coordinating multiple independent tracks simultaneously?β–Ό

Yes, teams adopt Conductor workflow to coordinate multiple independent tracks simultaneously. Track isolation ensures each track operates as an independent unit of work with clear boundaries from spec to execution.