Idea
The most convincing pitch for cc-tree is its output. Collect a handful of real runs (one per preset) into docs/gallery.md — each with the input, a trimmed tree.md, the final report, and the rendered diagram.
Suggested seeds:
brainstorm — a research/eng topic with a non-obvious winnerattack — critique of a short public document or RFCdesign — an option × trade-off × reversibility decisioncode-audit — a deliberately buggy sample file
This is both documentation and the basis for "showcase" social posts.
What's involved
Run the presets, trim the outputs for readability, and assemble docs/gallery.md with links from the README. No code changes.
Good first issue?
Yes — especially for someone learning the plugin who wants to contribute their first run.
Idea
The most convincing pitch for cc-tree is its output. Collect a handful of real runs (one per preset) into
docs/gallery.md— each with the input, a trimmedtree.md, the final report, and the rendered diagram.Suggested seeds:
brainstorm— a research/eng topic with a non-obvious winnerattack— critique of a short public document or RFCdesign— an option × trade-off × reversibility decisioncode-audit— a deliberately buggy sample fileThis is both documentation and the basis for "showcase" social posts.
What's involved
Run the presets, trim the outputs for readability, and assemble
docs/gallery.mdwith links from the README. No code changes.Good first issue?
Yes — especially for someone learning the plugin who wants to contribute their first run.