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.

Ir para a instalação

Repositório: luanmorenommaciel/uc-transact-co
Última atividade na origem: 15 de agosto de 2026 às 00:51
Idioma detectado do SKILL.md: inglês
Estrelas: 49
Forks: 48

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

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

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

2 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

spec-before-build

Turn one reasonable-looking plan item into a single atomic Task-Spec that states its goal, the behaviour a named human signs, and the machine-runnable proof that answers "am I done?" without asking. Use when a backlog item, plan row, or ticket permits more than one defensible implementation; before handing work to an agent; when "done" is still a matter of opinion; or when a graph of small units must be derived from a large plan. Refuses to invent a definition for any term whose meaning is owned by someone else.

2026-08-14

interview-the-system

Turn an ambiguous question about an unfamiliar or brownfield system into a bounded, read-only, evidence-backed investigation with a confirmed investigation contract, deliberate context manifest, claim ledger, ontology, owned open questions, and reviewable technical brief. Use when asked to investigate a repository, database, service, business metric, or existing system before building; grill a vague request; distinguish physical data from business meaning; or produce grounded upstream context for later specification and planning.

2026-08-13

Ver todas deste repositório

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.