DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to draft a task-specific harness in Claude Code with Jev Harness

Install the Jev Harness plugin and have Claude Code draft a Jev decision harness for your task.

Who it is forA developer on a support or operations team who needs incoming items routed to the right team and uses Claude Code.

The problemWriting decision logic and Jev instructions and criteria by hand takes time and expertise.

The outcomeA clarified plan for your inputs, legal actions, examples, success criteria, and budget, ready for the authoring LLM to turn into a harness.

What you need first

  • Claude Code or Codex installed
  • Git, and Node.js for the local archive viewer
  • Access to Jev model calls, since plugin installation does not configure model keys
  • A Python environment if you plan to build and run a harness yourself

Steps

  1. Run /plugin marketplace add https://github.com/TianyuCodings/JevHarness.git inside Claude Code.
  2. Run /plugin install jev-harness@jevharness.
  3. Run /reload-plugins.
  4. Run /jev-harness:jev-harness with your task, and answer its questions about inputs, legal actions, examples, success criteria, and budget.

Prompt for your agent

Using the JevHarness repo at https://github.com/TianyuCodings/JevHarness, invoke the jev-harness skill to draft a harness that routes <ticket type> to the right team. Ask for inputs, legal actions, examples, success criteria, and budget before writing any code. Expected output: a plan listing those items. Verify that every legal team action appears in the plan.

Caveat. Installing the plugin does not install Python dependencies or configure model keys, so Jev access must be set up separately.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page