// Compare evaluated document versions or variants; read-only on source docs. Use when asked to compare drafts, A/B versions, quality-diff docs, or pick the best.
Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents. Drop-in replacement for bd/Beads with simpler architecture. Use for: tracking issues/beads with dependencies, creating bugs/features/tasks, planning specs, implementing features from specs, code reviews, committing code, creating PRs, loading coding guidelines (TypeScript, Python, TDD, golden testing, Convex, monorepo patterns), code cleanup, research briefs, architecture docs, agent handoffs, and checking out third-party library source code. Invoke when user mentions: tbd, beads, bd, shortcuts, issues, bugs, tasks, features, epics, todo, tracking, specs, planning, implementation, validation, guidelines, templates, commit, PR, pull request, code review, testing, TDD, test-driven, golden testing, snapshot testing, TypeScript, Python, Convex, monorepo, cleanup, dead code, refactor, handoff, research, architecture, labels, search, checkout library, source code review, or any workflow shortcut.
Apply the common Markdown documentation guidelines to any document; modifies the doc. The basic, universal edit tier. Use when asked to tidy, clean up, conform, fix formatting/structure, or add the footer.
Copy-edit a Markdown document for language and formatting (the Expression and Form dimensions); modifies the doc. A superset of pprose-common-edit. Use when asked to copy edit, proofread, polish, tighten, rewrite, or line edit.
Score one practical document with metrics and rubric grading; read-only on source. Use when asked to score, evaluate, grade, rubric-check, or measure quality.
Full editorial pass over a practical document across all 20 Practical Prose dimensions; modifies the doc AND writes an editorial-review side document. A superset of pprose-copy-edit. Use when asked for a deep or full edit, an editorial review, a substantive edit, or a strengths-and-weaknesses review with suggested fixes.
| name | pprose-compare |
| description | Compare evaluated document versions or variants; read-only on source docs. Use when asked to compare drafts, A/B versions, quality-diff docs, or pick the best. |
This is read-only on source documents. It writes or prints comparison reports.
Use it after each input document already has a validated Practical Prose eval report.
*.eval.md reports.old=new.Run pprose runbook practical-prose-eval-compare for the full procedure.
Validate each input:
pprose report validate path/to/artifact.eval.md --complete
Generate the comparison:
pprose compare a.eval.md b.eval.md --format unified --pairs 'a=b' > comparison.md
Add --table-styles only when generating a report for a browser that supports the
optional table-style microformat.
Add human analytical prose only when the user asks for a full report, and ground it in specific table cells.
Return the comparison path or table, validation status for each input, and any alignment or rubric-version warnings.