workgate

    1

    Gate every change behind a claimed work item: file-backed items, per-item worktrees, a verified merge flow, and hooks that keep sessions on the rails.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    workgate

    Example session with this skill installed

    /wg-run 5 --parallel 2

    • Read your context and instructions
    • Compiled the workgate

    I will process the backlog. There are 12 items ready, I will run up to 5 items, 2 at a time.

    #104 done - Fixed null pointer in upload handler.
    #105 done - Added unit tests for retry logic.
    #108 blocked - worker stopped unfinished: Gate failed with exit code 1.
    #110 done - Updated README documentation for CLI.
    #112 skipped - No changes detected in worktree.

    Workgate Run Report

    • Done: 3
    • Blocked: 1
    • Skipped: 1

    Current Stats:

    • Total items: 42
    • Open: 8
    • Blocked: 4
    • Done (unverified): 15

    Items waiting on owner:

    • #108: worker stopped unfinished: Gate failed with exit code 1. (Needs: Investigate test failure in tests/upload_test.go)

    Verification Queue:
    The following items are finished and ready for wg verify:

    • #104: Fixed null pointer in upload handler.
    • #105: Added unit tests for retry logic.
    • #110: Updated README documentation for CLI.

    Next steps

    • Run wg review to see detailed outcomes for verified items.
    • Run wg unblock 108 "<fix_instructions>" to return the failed item to the queue.
    • Run /wg review to start the verification process for finished work.

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

    About this skill

    Developer workflows often collapse when context switching between feature branches, untracked tasks, and manual merge checks. Workgate forces discipline by gating every change behind a claimed work item, providing a file-backed backlog and isolated worktrees for every task.

    What it does

    • Backlog Management Provides a CLI-driven entry point to track, categorize, and prioritize bugs, features, and reworks without leaving the terminal.
    • Automated Worktrees Automatically claims items and switches the agent session into isolated worktrees to prevent dependency leakage.
    • Unattended Dispatching Loops through the backlog to dispatch multiple items to fresh subagents for autonomous execution.
    • Verified Merge Flow Enforces a strict wg done protocol that runs gates and handles integration branch merges automatically.
    • Context Preservation Uses file-backed state so sessions can be resumed, compacted, or restarted without losing progress.

    How it works

    1. Initialize Run wg init to set up the repository configuration and work item index.
    2. Backlog Triage Use /wg to view blocked, stale, or next-up items and pick a task to claim or resume.
    3. Task Execution Work within the provided worktree path, using wg body --set to update plans and wg check for targeted validation.
    4. Batch Processing Invoke /wg-run with optional --parallel flags to let subagents clear the ready queue unattended.

    Frameworks & tools

    This skill works with the wg CLI and any repository structure. It integrates with workgate:wg-worker subagents and requires a .workgate/config.json file.

    Why this beats prompting it yourself

    Manual prompting lacks the state persistence and architectural guardrails required for multi-task autonomy. This skill prevents "context drift" by isolating tasks into discrete worktrees and enforcing a standardized merge gate that an LLM would otherwise bypass.

    Use cases

    • Backlog Clearing Dispatch subagents to fix a batch of S3/S4 bugs while you focus on architecture.
    • Isolated Feature Dev Switch between multiple feature branches instantly without git stash or manual branch management.
    • Standardized PRs Ensure every change is linked to a verified item with a recorded outcome and plan.
    • Unattended Refactoring Run a parallelized session to apply linting or rework patterns across the entire repository.

    Known limitations

    Requires the wg CLI to be installed in the environment. Parallel execution is limited to 3 workers to avoid rebase conflicts on the integration branch.

    Requires wg CLI and .workgate/config.json. Parallel limit of 3 workers. Automated worktrees outside project root may require additional directory permissions.

    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 8 days ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed8 days ago

    What's inside

    Frequently Asked Questions

    Workgate automates the lifecycle of a task by isolating every backlog item into its own dedicated git worktree, preventing context leakage and ensuring that agents can work on multiple tasks simultaneously without manual branch management.

    The skill is designed to work with the `wg` CLI and is optimized for the `workgate:wg-worker` subagent, though it can be integrated into any agentic workflow that supports file-system access and CLI execution.

    You will receive the core Workgate skill package, the `wg` CLI tool, the subagent definitions for unattended dispatching, and a set of configuration templates to get your repository ready.

    While Workgate supports parallel task execution through its dispatching system, it currently limits active workers to 3 to prevent complex rebase conflicts and ensure stable merges into your integration branch.

    Yes, Workgate uses a file-backed state system within the `.workgate/` directory, allowing you to stop a session and resume exactly where the agent left off without losing the task history or the execution plan.

    New in Agents & Orchestration