Kjell Tore Guttormsen
8295601965
R4-R7 of the cleanup list (decision 188): the June trial docs and fixtures, the three orchestrator reference docs, the dormant synthesis-agent, code with no caller (project-discovery, bash-normalize, fidelity-diff, test-census, the next-session prompt validator, arm B and the --workflow flag) and the fix-round chain. Living docs repointed; the reasons for in-session orchestration and the all-opus pin are now written in docs/architecture.md and docs/profiles.md. New tests/lib/living-paths.test.mjs: living tracked text names only plugin paths that exist (seen red with 22 dead pointers before this commit). docs/T1-cc26-delegated-orchestration.md and lib/review/gold-scorer.mjs stay until R-b: the frozen end-state registry names them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
57 lines
2 KiB
Markdown
57 lines
2 KiB
Markdown
# Examples
|
|
|
|
Complete kalibrerte walk-throughs of the trekplan pipeline for
|
|
realistic tasks. Each example shows the four artifacts a project
|
|
directory contains after a full run:
|
|
|
|
- `brief.md` — task brief from `/trekbrief`
|
|
- `research/*.md` — research briefs from `/trekresearch`
|
|
- `plan.md` — implementation plan from `/trekplan`
|
|
- `progress.json` — execution log from `/trekexecute`
|
|
|
|
These are **hand-calibrated**, not LLM-generated. The point is to give
|
|
a fork-er a deterministic reference — what the artifacts look like
|
|
when everything goes right, with a small but real task.
|
|
|
|
## Running pipeline yourself
|
|
|
|
For your own work, point the four commands at a real project directory:
|
|
|
|
```bash
|
|
mkdir -p .claude/projects/2026-05-01-my-task
|
|
/trekbrief
|
|
/trekresearch --project .claude/projects/2026-05-01-my-task
|
|
/trekplan --project .claude/projects/2026-05-01-my-task
|
|
/trekexecute --project .claude/projects/2026-05-01-my-task
|
|
```
|
|
|
|
The artifacts in each example mirror that flow.
|
|
|
|
## Examples
|
|
|
|
### 02-real-cli
|
|
|
|
**Task:** a runnable fixture: `tally`, an 80-line zero-dep Node.js CLI
|
|
with a passing test suite and fixture data, as the input for a real
|
|
pipeline run (`/trekresearch`, `/trekplan`, `/trekexecute`). See
|
|
`REGENERATED.md` in the example for what it demonstrates and when to
|
|
re-run it.
|
|
|
|
## Regeneration
|
|
|
|
Each example has a `REGENERATED.md` documenting the version it was
|
|
calibrated against. When the artifact format changes, the example
|
|
needs to be re-built. See the `REGENERATED.md` file in each example
|
|
for triggers and procedure.
|
|
|
|
## Adding a new example
|
|
|
|
If you have a small, realistic task (touches 1-3 files, has a clear
|
|
success criterion, finishes in under 30 minutes) and want to add it
|
|
as an example:
|
|
|
|
1. Create `examples/NN-slug-here/` with the same four artifacts.
|
|
2. Add a `REGENERATED.md` documenting the calibration date and version.
|
|
3. Add a section to this README under `## Examples`.
|
|
4. Open an issue on the marketplace describing what the example
|
|
teaches that 02 doesn't already teach.
|