Conductor

The problem

Large language models often skip critical planning phases, jumping straight to implementation and creating "spaghetti" architectures or missing core requirements. Coordinating multiple specialized agent roles without a strict operational sequence leads to scope creep and inconsistent file handoffs.

What it does

• Sequences a product crew through a specific build slice using a rigid phase plan.
• Enforces gates between Business Analyst, UX, Architecture, Infra, and TDD roles.
• Generates a phase-plan.md scoreboard to track role status, artifact writes, and stop conditions.
• Prevents the conductor from authoring application code, ensuring role separation and quality control.
• Validates handoff artifacts against a strict contract before allowing the next phase to trigger.

Frameworks & tools

Works with any agent capable of file system operations. Specifically designed to orchestrate siblings like business-analyst, ux-designer, software-architect, senior-planner, and junior-tdd.

Why this beats prompting it yourself

DIY prompting often fails to maintain state across complex multi-step workflows, leading to "hallucinated" progress. This skill provides a structured state machine that requires physical artifact verification at every gate, preventing the model from skipping boring but essential steps like requirements gathering or infrastructure planning.

Use cases

• Orchestrate a full product team from vision to task list without writing a single line of code.
• Ensure a Junior TDD agent only works on tasks pre-approved by a Senior Planner and Architect.
• Audit a development workflow by forcing agents to document handoffs in a standardized index.
• Stop a build immediately when a requirement is missing or architecture is blocked.

Known limitations

Does not perform implementation itself. Requires sibling skills to be present in the workforce directory to function. Cannot manage external SaaS trackers like Jira.