harness-scaffold

Regenerate the structural skeleton of a harness — agent role stubs, KB layout, and per-stack rule files — for a repository's stack, in seconds. Use when a harness structure must be (re)created from artifacts on disk, after the roles and contract are already understood and never before. Produces structure only: every stub is intentionally empty, and the scaffold grants no authority.

Jump to install

Repository: luanmorenommaciel/uc-transact-co
Last source activity: August 15, 2026 at 00:51
Detected SKILL.md language: English
Stars: 49
Forks: 48

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/luanmorenommaciel/uc-transact-co --skill harness-scaffold

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Harness Scaffold

One run regenerates the harness structure the team already understands: agents/ role stubs, kb/<stack>/ knowledge-base placeholders, and rules/<stack>.md rule stubs, plus a manifest. It is the automation of the hand-written work from sessions/d2/03-agent-pair.md — faster, never smarter.

Day 2 of Semana Engenharia Agêntica delivers this skill. It follows Day 1's interview-the-system, which supplies the evidence and the owned questions the harness is built around, and it precedes Day 3's spec-before-build, which writes the units that execute inside the authority this structure holds.

Boundaries

Writes ONLY under tmp/harness-scaffold/. Never touches AGENTS.md, CLAUDE.md, dbt/, src/, or storage/.

Grants no authority. The harness contract does that; this skill only lays out where the pieces of a harness live.

Every generated file is a stub, empty by design. What fills a stub — grounded KB content, tuned doctrine — is human work measured in hours, not a generator's output.

Requires no chat memory: everything it needs is on disk.

Method

Read the stack from the request (default for this repo: dbt,duckdb,fastapi,mcp).

Run the generator:

uv run python skills/harness-scaffold/scripts/scaffold_harness.py \
  --stack dbt,duckdb,fastapi,mcp --dest tmp/harness-scaffold

Validate the structure:

uv run python skills/harness-scaffold/scripts/scaffold_harness.py \
  --stack dbt,duckdb,fastapi,mcp --dest tmp/harness-scaffold --check

Report: the generated tree, the manifest summary, and the reminder that every stub is empty. Open one stub if asked — show, do not narrate.

Human stop

The scaffold is structure, not content, and it is not authorization. Building anything inside it still requires the confirmed harness contract, and every semantic decision (Revenue included) stays with its named owner.