Skip to content

feat(po): rich navigable review artifact for plan-backlog (#74) - #76

Merged
atamanvega merged 1 commit into
mainfrom
feat/plan-artifacts
Sep 9, 2026
Merged

feat(po): rich navigable review artifact for plan-backlog (#74)#76
atamanvega merged 1 commit into
mainfrom
feat/plan-artifacts

Conversation

@atamanvega

Copy link
Copy Markdown
Collaborator

Implements #74 (from @santielizondo's idea). At plan-backlog's review step, a non-trivial backlog draft is now presented as a navigable artifact on hosts that support them (Claude Code / claude.ai) — collapsible epics → stories with acceptance criteria, labels, sizing and dependencies, plus search/filter and a table of contents — so a large backlog is easy to scan and drill into.

Design

  • The artifact is a review aid, not the gate: the in-chat draft summary + approval question remain the approval surface (a page/dialog is not a substitute). Skill loads artifact-design before building it.
  • Portable hosts (Codex / Cursor / Copilot) keep Markdown — artifacts are Claude-side, like the /plan-backlog command + backlog-planner agent.
  • Only for non-trivial backlogs (a couple of items don't need a page).

Files

  • skills/plan-backlog/SKILL.md §5 — the rich review surface.
  • commands/plan-backlog.md, agents/backlog-planner.md — reflect it in the gate (caller renders; a subagent only returns the draft).
  • README + CHANGELOG; version → 0.19.12.

Verification

node scripts/build-codex-plugin.mjs && node scripts/validate-codex-plugin.mjs && node --test scripts/*.test.mjs && git diff --exit-code
# validate ✓ · 35/35 · skill synced, version aligned

Closes #74.

🤖 Generated with Claude Code

…9.12)

On hosts with artifacts (Claude Code / claude.ai), present a non-trivial backlog
draft as a navigable artifact at the review step — collapsible epics → stories with
acceptance criteria, labels, sizing, dependencies, plus search/filter and a ToC — so
a large backlog is easy to scan and drill into.

- skills/plan-backlog/SKILL.md §5: rich review surface guidance (load artifact-design);
  the in-chat draft + approval question stay the gate (artifact is a review aid, not a
  substitute); portable hosts keep Markdown.
- commands/plan-backlog.md + agents/backlog-planner.md: reflect the artifact in the gate
  (caller renders it; a subagent only returns the draft).
- README + CHANGELOG updated; version aligned to 0.19.12; node --test 35/35.

From @santielizondo's idea. Closes #74.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@vercel

vercel Bot commented Sep 9, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
claude-dev-kit-telemetry-relay Ignored Ignored Preview Sep 9, 2026 7:20am UTC

Request Review

@atamanvega
atamanvega merged commit c562d41 into main Sep 9, 2026
3 checks passed
@atamanvega
atamanvega deleted the feat/plan-artifacts branch September 9, 2026 07:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

idea: richer artifact format for generated plans (navigable/collapsible/searchable HTML)

1 participant