Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    Conductor

    1

    A workflow orchestrator that sequences specialized agent roles through a rigid product development lifecycle.

    $10

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned
    Conductor

    Conductor

    Example session with this skill installed

    Run the product crew on the 'Vault' project. Goal: build the local-first vault creation flow. vision is in ./brief.txt. No UI needed. Hosting is local-first. Stop at the planner.

    • Read your context and instructions
    • Compiled the conductor
    • Generated the document

    I have initialized the product crew sequence for

    Vault. The process stopped after the senior planning phase as requested. I have coordinated the Business Analyst, Software Architect, and Senior Planner roles to produce the necessary documentation and task breakdown.

    Phase Plan: Vault Local-First Creation

    phase_idowner_rolewritesreadsstatus
    babusiness-analystdocs/requirements.mdvision_pathdone
    uxux-designerdocs/ux.mddocs/requirements.mdskipped: no UI
    sw-archsoftware-architectdocs/architecture.mddocs/requirements.mddone
    infrasystem-architectdocs/infrastructure.mddocs/architecture.mddone
    plansenior-plannerplans/tasks.mddocs/arch, docs/reqsdone
    tddjunior-tddsrc/*plans/tasks.mdqueued
    qaqa-engineerqa/report.mdtdd artifactsqueued

    Handoff Index

    • docs/requirements.md: P0 stories for local vault initialization and master key setup.
    • docs/architecture.md: SQLite with AES-256-GCM encryption strategy defined.
    • docs/infrastructure.md: Local-only storage spec, no cloud persistence.
    • plans/tasks.md: 4 discrete TDD tasks (Init DB, Key Gen, Vault Schema, Write Ops).

    Stop Conditions Met

    • Planner phase complete. Implementation spine (TDD/QA) is queued but not started.
    • Conductor residual: implemented: no.

    Next steps

    1. Review the task estimates in plans/tasks.md.
    2. Increase wip_limit if you want to run parallel TDD tasks for non-overlapping files.
    3. Call the junior-tdd skill to begin the build spine.

    conductor.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Enforce a rigid sequence of operations across multiple specialized agent roles.Prevent implementation until requirements and architecture gates are passed.Maintain a physical audit trail of handoff files and role statuses.Scale complex builds by limiting WIP and enforcing TDD task boundaries.

    About this skill

    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.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 1 day ago

    • Passed all security checks, Safe to install

    Listed1 day ago

    Frequently Asked Questions