What problem does it solve? Teams using the quorum pipeline accumulate one directory per planned change in docs/work/, but there is no built-in way to see the full record of what the repository has been asked to do, who planned it, when, and how far each change got. This Skill reads that record back as a readable, chronological listing. ## Core Features & Use Cases - Chronological change listing: Runs history.py to print one section per work item, oldest first, with the original prompt quoted verbatim, the planner, the date, and the outcome. - Filtering and formatting options: Supports --author, --limit, --json, and a fixed-width table mode for narrow terminals, with --markdown as the default for readable prose output. - Honest provenance reporting: Distinguishes commit author from requester, flags uncommitted plans, and states explicitly what the record cannot tell you, such as work on unmerged branches. - Use Case: A developer returning to a repository after a month asks what changes have been planned and shipped; the Skill lists every work item with its prompt and verdict, then points to the relevant plan.md and verdict.md files for detail. ## Quick Start Ask the AI to show the history of everything this repository has been asked to build through the quorum pipeline.
