Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Conductor

    1

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

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security 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

    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_id | owner_role | writes | reads | status | | :--- | :--- | :--- | :--- | :--- | | ba | business-analyst | docs/requirements.md | vision_path | done | | ux | ux-designer | docs/ux.md | docs/requirements.md | skipped: no UI | | sw-arch | software-architect | docs/architecture.md | docs/requirements.md | done | | infra | system-architect | docs/infrastructure.md | docs/architecture.md | done | | plan | senior-planner | plans/tasks.md | docs/arch, docs/reqs | done | | tdd | junior-tdd | src/* | plans/tasks.md | queued | | qa | qa-engineer | qa/report.md | tdd artifacts | queued | ### 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.

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

    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.

    Does not author application code. Requires sibling skills (BA, UX, Architect, etc.) to be present. Limited to one product slice at a time.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Permissions

    Read Files
    Write Files
    Listed2 months ago

    What's inside

    Frequently Asked Questions

    No, Conductor is a pure orchestrator. It manages the sequence, validates artifacts, and enforces role separation, but it requires specialized sibling agents (like Architects or TDD roles) to perform the actual development work.

    Conductor creates a physical 'phase-plan.md' scoreboard in your directory, acting as a state machine that tracks role status and artifact verification to ensure the LLM never skips critical planning phases.

    It is designed to work with any agent capable of file system operations and is optimized for workflows involving Business Analysts, UX Designers, Architects, and TDD agents.

    Conductor enforces a 'strict contract' validation, meaning it checks for the physical existence and quality of required artifacts before the next phase in the product development lifecycle can trigger.

    You receive the Conductor skill logic, the standardized contract templates for role handoffs, and the phase-plan state management system to integrate into your workforce directory.

    Yes, while it follows a rigid SDLC sequence, it is designed to orchestrate the build of any specific product slice, from visioning to task list generation, regardless of the tech stack.

    New in Workflow Automation