feat: scaffold redsen-lean-harness v0.1.0
Recovered from crashed session (Node OOM). Repo contains full P0-P6 scaffold: plugin.json/marketplace.json, AGENTS.md, ADRs 0001-0006, lh CLI (init/index/graph/lane/run/memory/host/report/doctor), 10 .github/agents, 12 CLI skills, instructions, context7 mcp.json, and unit/e2e test suite. Fixed: run.mjs read --in-tokens/--out-tokens but tests and CLI docs use --input-tokens/--output-tokens, so telemetry totals were always 0. Now accepts both forms. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
@@ -0,0 +1,15 @@
|
||||
---
|
||||
name: build
|
||||
description: Use when executing planned read and write lanes through lh host and the Ralph loop.
|
||||
---
|
||||
|
||||
# build skill
|
||||
|
||||
1. Invoke `.github/agents/conductor.agent.md`.
|
||||
2. Run `lh host` first through the conductor.
|
||||
3. Obey parallel or sequential strategy printed by `lh host`.
|
||||
4. Use `lh lane create` for write lanes.
|
||||
5. Run builder ⇄ verifier Ralph loops.
|
||||
6. Record failures with `lh memory put --shard failures`.
|
||||
|
||||
Stop on max Ralph iterations and escalate.
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: design
|
||||
description: Use when starting gated design discovery before planning, especially when requirements are incomplete or ambiguous.
|
||||
---
|
||||
|
||||
# design skill
|
||||
|
||||
1. Invoke `.github/agents/interrogator.agent.md`.
|
||||
2. Require numbered questions with numbered recommended answers.
|
||||
3. Mark one answer as recommended.
|
||||
4. Persist final answers to `.agents/specs/<slug>/decisions.md`.
|
||||
5. Stop until every required question is answered.
|
||||
|
||||
Do not infer decisions. Do not start planning before the user gate.
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: doctor
|
||||
description: Use when checking harness environment, configuration, host capabilities, or broken setup.
|
||||
---
|
||||
|
||||
# doctor skill
|
||||
|
||||
1. Run `lh doctor`.
|
||||
2. Run `lh host` when orchestration capability matters.
|
||||
3. Run `lh graph --brief` when repository structure matters.
|
||||
4. Report failures with exact commands and exit status.
|
||||
5. Suggest the smallest next fix.
|
||||
|
||||
Do not mutate project state unless the user asked for repair.
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
name: fast-track
|
||||
description: Use for a small brownfield change that can skip spec and DAG but still needs Ralph and journal discipline.
|
||||
---
|
||||
|
||||
# fast-track skill
|
||||
|
||||
1. Confirm the change is small and brownfield.
|
||||
2. Use a single write lane.
|
||||
3. Keep the same Ralph loop: builder ⇄ verifier.
|
||||
4. Keep the same journal in `.agents/runs/<id>/journal.md`.
|
||||
5. Run `lh graph`.
|
||||
6. Request reviewer approval before completion.
|
||||
|
||||
Do not fast-track ambiguous or cross-cutting work.
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: index
|
||||
description: Use when needing repository understanding under a token budget before reading files by hand.
|
||||
---
|
||||
|
||||
# index skill
|
||||
|
||||
1. Run `lh index --budget <N> --focus <glob>`.
|
||||
2. Add `--stats` when onboarding or sizing work.
|
||||
3. Prefer index output before raw reads.
|
||||
4. Follow with `lh graph --brief` when structure matters.
|
||||
5. Read files by hand only after narrowing scope.
|
||||
|
||||
Return paths and facts, not dumps.
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: init
|
||||
description: Use when initializing lean harness state in a repository or repairing missing .agents baseline files.
|
||||
---
|
||||
|
||||
# init skill
|
||||
|
||||
1. Invoke `lh init`.
|
||||
2. Confirm `.agents/harness.config.json` exists.
|
||||
3. Confirm `.agents/memory/INDEX.md` exists.
|
||||
4. Run `lh doctor` after initialization.
|
||||
5. Report created paths and blockers only.
|
||||
|
||||
Delegate orchestration to `.github/agents/conductor.agent.md` when initialization is part of a full run.
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
name: integrate
|
||||
description: Use when planned lane branches are complete and must be merged sequentially with final verification.
|
||||
---
|
||||
|
||||
# integrate skill
|
||||
|
||||
1. Invoke `.github/agents/integrator.agent.md`.
|
||||
2. Merge lanes one at a time with `lh lane merge`.
|
||||
3. Resolve local conflicts only when safe.
|
||||
4. Escalate conflicting acceptance criteria.
|
||||
5. Run one final full verify.
|
||||
6. Request final reviewer approval.
|
||||
|
||||
Never merge lanes in parallel.
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: memory
|
||||
description: Use when retrieving, writing, compacting, or scanning lean harness memory shards.
|
||||
---
|
||||
|
||||
# memory skill
|
||||
|
||||
1. Use `lh memory list` to inspect shards.
|
||||
2. Use `lh memory get --shard <name>` to read one shard.
|
||||
3. Use `lh memory put --shard <name>` to write durable facts.
|
||||
4. Use `lh memory scan` before risky writes.
|
||||
5. Use `lh memory compact` when shards grow noisy.
|
||||
|
||||
Never write secrets to memory.
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: onboard
|
||||
description: Use when a new contributor or agent needs a concise map of harness state, commands, and memory.
|
||||
---
|
||||
|
||||
# onboard skill
|
||||
|
||||
1. Run `lh doctor`.
|
||||
2. Run `lh index --stats --budget 4000`.
|
||||
3. Read `.agents/memory/INDEX.md` only.
|
||||
4. Run `lh graph --brief`.
|
||||
5. Summarize commands, state paths, conventions, and blockers.
|
||||
|
||||
Pull shards only when the user asks for deeper history.
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: plan
|
||||
description: Use when decisions are complete and the harness must produce a spec plus lane DAG before build.
|
||||
---
|
||||
|
||||
# plan skill
|
||||
|
||||
1. Read `.agents/specs/<slug>/decisions.md`.
|
||||
2. Invoke `.github/agents/architect.agent.md` for `.agents/specs/<slug>/spec.md`.
|
||||
3. Invoke `.github/agents/splitter.agent.md` for `.agents/specs/<slug>/plan.dag.json`.
|
||||
4. Run `lh graph --brief`.
|
||||
5. Report spec path, DAG path, acceptance ids, and blockers.
|
||||
|
||||
Do not build before the DAG passes structural gates.
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: telemetry
|
||||
description: Use when starting, recording, ending, or reporting a harness run and its phase events.
|
||||
---
|
||||
|
||||
# telemetry skill
|
||||
|
||||
1. Start with `lh run start`.
|
||||
2. Record phase changes with `lh run event`.
|
||||
3. End with `lh run end`.
|
||||
4. Read `.agents/runs/<id>/board.md` for current state.
|
||||
5. Run `lh report <runId>` for a markdown summary.
|
||||
|
||||
Keep event messages short and machine-readable.
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
name: verify
|
||||
description: Use when checking configured commands, lh graph, acceptance criteria, and lane scope compliance.
|
||||
---
|
||||
|
||||
# verify skill
|
||||
|
||||
1. Invoke `.github/agents/verifier.agent.md` for command checks.
|
||||
2. Run configured verify commands.
|
||||
3. Run `lh graph`.
|
||||
4. Check acceptance ids individually.
|
||||
5. Check scope globs.
|
||||
6. Return a terse pass/fail table only.
|
||||
|
||||
Do not edit files during verification.
|
||||
Reference in New Issue
Block a user