voyage/examples

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:

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.