explaingit

lopopolo/harness-engineering

Analysis updated 2026-05-18

2,120PythonAudience · researcherComplexity · 1/5LicenseSetup · easy

TLDR

A written field guide arguing that shaping the context and tools around an AI coding agent, not the model itself, is what improves its results over time.

Mindmap

mindmap
  root((harness-engineering))
    What it does
      Field guide essays
      Agent environment design
      Context and tools
    Tech stack
      Markdown
      Python scripts
    Use cases
      Thesis index
      Playbooks
      Agent routing
    Audience
      Researchers
      Agent builders
    License
      CC BY 4.0
      Attribution required

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Read the thesis index to understand a framework for improving AI coding agent output through context and tooling.

USE CASE 2

Point a coding agent at this repository alongside a real project to have it apply the included playbooks.

USE CASE 3

Study the included essays to design an organization's own process for keeping AI agent behavior consistent over time.

USE CASE 4

Use the AGENTS.md routing file as an example of how to guide an agent to relevant documentation.

What is it built with?

MarkdownPython

How does it compare?

lopopolo/harness-engineeringyaojingang/yao-open-promptshughyau/academicforge
Stars2,1202,1222,095
LanguagePythonPythonPython
Setup difficultyeasyeasyeasy
Complexity1/51/52/5
Audienceresearcherwriterresearcher

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

This is a reading collection, not runnable software.

You may reuse the repository authored material as long as you give credit to the original author.

In plain English

This repository is a collection of writing, not a piece of software you install and run. It is Ryan Lopopolo's anthology and field guide on a practice he calls shaping the working environment around an AI coding agent to get better results from it, while treating the underlying AI model and coding tool itself as fixed. The core idea is that you improve outcomes by working on two things around the agent: the context it is given and the tools it can use, plus how that surrounding setup is organized. The writing argues that a well built working environment should carry an organization's real requirements, things like reliability, security, how maintainable something is, performance, and how much risk is acceptable, and should also carry local decisions about how to balance those requirements against each other. It also argues that because doing this kind of work happens repeatedly over time, a good environment can turn past lessons, corrections, and failures into context, boundaries, and checks that make later work more consistent, rather than starting from scratch each time. Practically, the repository is meant to be pointed at by a coding agent alongside whatever system that agent is meant to improve. An included AGENTS.md file routes the agent to the relevant essays, examples, and supporting proof. Readers who want the core argument can start with a thesis index, and those looking for a concrete application can look at a set of included playbooks. The repository also links out to related essays and sources that influenced this thinking. This is intended for people building or maintaining AI coding agents at an organizational level, especially those thinking about how to make agent behavior consistent and improvable over time rather than a one off experiment. Repository authored material is licensed under CC BY 4.0, which requires giving credit to the original author when you reuse it.

Copy-paste prompts

Prompt 1
Summarize the core argument of this repository's thesis index in plain language.
Prompt 2
Read AGENTS.md in this repo and explain how it routes a coding agent to relevant material.
Prompt 3
Pick one playbook from this repo and explain how I could apply it to my own project.
Prompt 4
Compare the ideas in this repo to other essays it links to under influences and alternate framings.
Prompt 5
Explain what nonfunctional requirements are, using the definition given in this repo's docs.

Frequently asked questions

What is harness-engineering?

A written field guide arguing that shaping the context and tools around an AI coding agent, not the model itself, is what improves its results over time.

What language is harness-engineering written in?

Mainly Python. The stack also includes Markdown, Python.

What license does harness-engineering use?

You may reuse the repository authored material as long as you give credit to the original author.

How hard is harness-engineering to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is harness-engineering for?

Mainly researcher.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.