Rsc Harness

rsc-harness

You build the product. rsc-harness builds its harness.

Keep your project knowledge, skills and working rules together across the assistants you already use.
Start with your goal. Review what rsc proposes to install. Accept the plan before it changes your project.

MIT licensed · project-local setup · 18 assistant targets

Give this URL to your agent and paste the request in the chat:

Or start from the terminal:

Your project has a way of working. Give it to your agent.

A new chat should not make you reconstruct the stack, explain yesterday's decision and remember which
files must stay untouched. Putting every instruction into one giant prompt creates a different problem:
the important details compete with rules that have nothing to do with today's task.

Hand-built setups can become a Frankenstein harness: duplicated instructions, unrelated skills,
premature hooks and unnecessary MCP connections. Open standards cover individual pieces
(Agent Skills, MCP,
AGENTS.md). Your project still needs someone to choose and maintain the right pieces.

rsc-harness makes that choice explicit. It reads evidence within your project root, asks about your goal
and assistants, and prepares a plan you can inspect before applying it.

See the plan before you install

Every component has a disposition:

You accept the exact plan. If project evidence changes before acceptance, rsc asks you to review a
fresh plan. Later, rsc reassess reports new needs without silently installing them.

Why documentation comes first

The decisions your agent needs should have a place to live outside the chat.

The mechanism is practical: keep the decision, make it discoverable, and have the next task consult it.
That gives the agent a maintained source to work from. It does not make an outdated…