Skip to content

ericrisco/rsc-harness / skills/harness

harness

Flagged

Use when governing a workspace's control plane, code or not — the `01-TOOLS/` tooling layer, the `02-DOCS/` chaos→knowledge wiki, the root Knowledge map. Audits it, migrates legacy `XX-*` folders, scaffolds provider tooling, sweeps the inbox, eats a file the person hands over ("cómete este fichero", "guárdalo en la documentación": moved into 02-DOCS/raw/ and documented), writes root CLAUDE.md/AGENTS.md. NOT the bootstrap front door (that is `init`, which hands off here).

references/wiki-worklog-template.md

View on GitHub
# Worklog raw template — `raw/worklog/<YYYY-MM-DD>-<slug>.md`

The **work-driven on-ramp**. A Worklog Sweep writes one of these per meaningful
unit of work — what we *did*, not what someone dropped in `inbox/`. It is `raw`
(evidence: preserved, never edited after the fact) and is Compiled into `wiki/`
like any other source. The session is just another source of chaos.

**Throttle — do NOT write a worklog for:** pure read/answer turns, questions with
no file change, no decision, and no commit. Capture only durable signal. Never
manufacture a worklog "to look busy."

```yaml
---
# OKF v0.1: `type` is the only required field. The rest is the standard surface
# (title/description/timestamp) plus rsc custom fields (topic/status/sources).
type: worklog
title: {What we did, one line}
description: {One-sentence summary of the session.}
timestamp: {YYYY-MM-DDTHH:MM:SSZ}
topic: {inferred-topic}
status: unprocessed
sources: []
---
```

## What we did

{Concrete changes / features / fixes — one bullet each. Plain, factual.}

## Why

{Intent and the decisions taken. Every *significant* decision is ALSO appended to
`wiki/harness/decisions.md` (append-only, with the 3-options shape) during Compile.}

## Files touched

- `{path}:{line}` — {what changed}

## Outcome

{Verdict: shipped & verified / partial / blocked. Include the evidence — test
output, command result, screenshot path. No "done" without proof.}

## Open questions / next

- {What remains, what to pick up next session.}

## Commands

- `{command}` — {result}

<!--
LIFECYCLE: written by the Worklog Sweep → status: unprocessed. The Compile step
distills durable points into wiki/<topic>/ articles (update existing before
creating new), cross-links, cascades, appends decisions to decisions.md, then
flips this file's status to processed (the raw stays as evidence; it is not
deleted or rewritten). Triggers that fire a Worklog Sweep: a PreCompact/SessionEnd
hook (Claude Code), an explicit milestone (a commit / a shipped feature), and the
daily curation automation. See `wiki-protocol.md` → "Worklog Sweep".
-->
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall