Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Operator-led delivery: keep coding agents shipping

    1

    Use it to install the workflow in an existing repository, resume a bounded task, prepare operator review or coordinate independent agents without two writers editing the same file.

    $3

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Operator-led delivery: keep coding agents shipping

    Operator-led delivery: keep coding agents shipping

    Example session with this skill installed

    Set up operator-led delivery in this repository. Keep our existing architecture and commands. Our first approved outcome is that a user can create a record, edit it, close the app and reopen the saved result. Turn that into one active delivery slice, park unrelated ideas, and leave clear instructions so another agent can continue next session. Ask me before deciding any remaining release scope.

    • Read your context and instructions
    • Compiled the operator-led delivery

    Changed

    Installed operator-led delivery without changing the existing CLI architecture, application code, tests or README commands.

    • docs/roadmap.json contains exactly one approved slice:

    S01 — create, edit, close and reopen a local record. Its task,

    S01.1, is now needs_review, not complete.

    • Collaboration and cloud sync are parked under LATER; neither is an approved release slice.
    • Merged delivery rules and exact verification commands into the existing AGENTS.md, and installed the packaged validator at tools/validate_plan.py.
    • Added local .agent/ memory and a next-session handoff. A continuing agent is directed to review S01’s evidence, not start unapproved work.

    Verified

    All commands exited 0:

    • python3 tools/validate_plan.py docs/roadmap.json --root . → PLAN OK.
    • python3 records.py --help, the documented syntax compilation and the disposable-store smoke command succeeded.
    • python3 -m unittest -v test_records.RecordPersistenceTests and python3 -m unittest discover -v each ran

    2 tests, reporting OK.

    I also ran separate CLI processes

    python3 records.py --store .scratch/reopen.json create Original
    python3 records.py --store .scratch/reopen.json edit 1 Updated
    python3 records.py --store .scratch/reopen.json show 1
    

    After the earlier processes exited, the reopened result was:

    {"id": "1", "text": "Updated"}
    

    Commands, observations and source hashes are recorded in docs/playtests/S01/play-note.md. Application and test hashes were unchanged.

    Limits and next decision

    This run used an authored disposable example repository and isolated stores. It verified the existing source-run CLI behavior; it did not newly implement the feature, publish a release or establish your acceptance.

    Does the observed S01 outcome meet your expectations, and should the release contain only this outcome? I have left any additional release scope undecided pending your direction.

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

    About this skill

    Long-running coding-agent projects need more than a long instruction file. They need a bounded plan, proof that the product works for its user, and an accurate next-session handoff. This skill teaches your agent to work one slice at a time, keep product-design decisions with you, limit test/document churn, verify the changed path, and separate implemented, validated, delivered and accepted work. It includes durable-memory templates and a standard-library Python validator for slice order, work-in-progress, stable IDs and proof/evidence paths. Use it to install the workflow in an existing repository, resume a bounded task, prepare operator review or coordinate independent agents without two writers editing the same file. It is language-neutral; it does not provide a test runner for your language.

    Optional OpenWolf and Graphify integrations are HIGHLY RECOMMENDED but are not required or bundled.

    Suggested tags: coding-agents, project-workflow, delivery, planning, handoff, multi-agent. Choose the closest categories the submission form actually offers.

    Example prompt: “Install this protocol in my repository, retaining the existing spec and commands. Ask me to choose the release slices before writing the plan.”

    Expected result: a reviewed plan, memory/instruction pointers and a runnable local plan check; subsequent sessions identify the active task and its observable next action.

    Highly dependent on Python 3.10+ for plan validation. Does not provide language-specific test runners. Relies on operator-defined commands for builds and smoke tests.

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

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Listed26 days ago
    Updated22 days ago

    What's inside

    Frequently Asked Questions

    This skill prevents 'agent amnesia' and scope creep by enforcing strict Work-In-Progress (WIP) limits and a roadmap-driven execution flow, ensuring agents stay focused on user-visible outcomes rather than aimless refactoring.

    The protocol is framework-agnostic and works with any LLM-based coding agent that can read and write to a file system; it only requires Python 3.10+ for the plan validation script.

    You receive the core delivery protocol, the automated roadmap validation script, standardized templates for roadmaps and bug logs, and the integration guide for setting up the `.agent/` control directory.

    It is designed for rapid setup: you simply initialize the control directory and adapt the provided roadmap template, allowing the agent to begin structured execution immediately.

    The skill focuses on process enforcement and delivery flow; you will still need to define your own language-specific test runners and security policies within the project's environment.

    Updates to the validation schema and status templates are released periodically to support new agent capabilities, and buyers receive notifications for these improvements through the marketplace dashboard.

    New in Agents & Orchestration