open/ktg-plugin-marketplace
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity Actions
ktg-plugin-marketplace/plugins/ultraplan-local/examples/01-add-verbose-flag/REGENERATED.md
Kjell Tore Guttormsen 14ecda886c feat(voyage)!: bulk content rewrite ultra -> voyage/trek prose [skip-docs] 
Sed-pipeline (16 patterns, longest-match-first) sweeper residuelle ultra*-treff
i prose, command-narrativ, agent-prompts, hook-kommentarer, doc-prosa.

Pipeline-utvidelser fra V4-prompten:
- BSD-syntax [[:<:]]ultra[[:>:]] istedenfor \bultra\b (BSD sed mangler \b)
- 6 compound-patterns for ultraplan/ultraexecute/ultraresearch/ultrabrief/
  ultrareview/ultracontinue uten -local-suffiks
- ultra*-stats glob -> trek*-stats glob
- Linje-eksklusjon redusert til ultra-cc-architect (Q8); session-state-
  eksklusjonen var over-protektiv
- File-eksklusjon utvidet til settings.json, package.json, plugin.json,
  hele .claude/-treet (gitignored + V5-territorium)

Q8-undantak holdt: architecture-discovery.mjs + project-discovery.mjs urort.
Filnavn-konvensjon holdt: .session-state.local.json + *.local.* preservert.

Manuell narrative-fix: tests/lib/agent-frontmatter.test.mjs linje 10
mangled "/ultra*-local" til "/voyage*-local" (ingen slik kommando finnes);
korrigert til "/trek*".

Residualer utenfor scope (V5 handterer): package.json + .claude-plugin/
plugin.json (Step 12-14 versjons-bump). .claude/* er gitignored
spec-historikk med tilsiktet BEFORE/AFTER-narrativ.

Part of voyage-rebrand session 3 (Wave 4 / Step 10).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-05 15:08:20 +02:00

1.8 KiB
Raw Blame History

Regeneration log — 01-add-verbose-flag

Field Value
Last regenerated 2026-05-01
trekplan version 3.1.0
Claude Code version ≥ 2.1.105 (PreCompact-hook)
Source brief author Hand-calibrated example, not LLM-generated
Plan author Hand-calibrated to demonstrate plan_version 1.7 schema + manifest YAML

What this is

A complete walk-through of the four-stage pipeline for one realistic small task: adding a --verbose flag to a hypothetical small-auth CLI parser. Every artifact is hand-calibrated, not LLM-generated, so fork-ers can study the shape without worrying about whether an LLM hallucinated something.

What "regenerate" means

If the artifact format changes (frontmatter schema, manifest YAML keys, progress.json version), this example needs to be re-built so fork-ers don't learn an obsolete shape.

Triggers for regeneration:

  • plan_version bumps
  • Frontmatter schema additions to brief.md or research/*.md
  • New required keys in manifest YAML
  • progress.json schema bump beyond schema_version: "1"

When regenerating: do not run an actual LLM-driven pipeline against this brief. Hand-calibrate against the new schema so the example stays deterministic and reviewable.

Project assumed

A fictional small-auth CLI with this layout:

small-auth/
├── package.json
├── src/
│   ├── cli.mjs                    # 80-line argv parser (hand-rolled)
│   └── commands/
│       ├── login.mjs
│       ├── logout.mjs
│       ├── whoami.mjs
│       ├── token-refresh.mjs
│       ├── users-list.mjs
│       └── users-create.mjs
└── tests/                         # 24 tests, node:test

This project is not in the plugin repo. The example artifacts reference it as if it were the cwd of an /trekexecute run.