Create durable per-decider ballot files with Must/Should/Could tiers.
npx skills add https://github.com/eins78/agent-skills --skill ballot
Please help me install this Agent Skill. Skill: ballot Source: https://github.com/eins78/agent-skills/tree/main/skills/ballot Command: npx skills add https://github.com/eins78/agent-skills --skill ballot
Durable decision artefacts for decisions that happen async — reviewers look at them over chat, on a PR, after the agent session ends. The ballot surface provides a portable, readable format whose reconciliation lives in the sessionlog.
Create a ballot file per decider using the provided template and fill each DEC with a single decision surface and a clean cover block.
High-intent search queries and answers about installing and using this skill.
To track asynchronous decisions, you can create durable ballot files that capture each decider's choice. These files use Must/Should/Could tiering to express urgency and keep records readable on small screens with clean diffs.
Creating an auditable record for architecture decisions requires a durable artifact separated from discussion notes. The ballot approach enforces a DOSSIER-slug-BALLOT-Reviewer naming convention and reconciles decisions through a sessionlog.
Sessionlog reconciliation works by separating durable decision artifacts from ongoing discussion notes. The ballot files capture the per-decider sign-off, while the sessionlog handles the reconciliation to ensure portable, auditable records.
Yes, you can use the Must/Should/Could decision surface for hiring panels and PR handoffs. This tiering expresses urgency and impact, producing one file per decider to maintain readable surfaces for asynchronous review.
The ballot skill supports both standalone and dossier-invoked usage. It applies a consistent template and reference materials to produce per-decider files for asynchronous code reviews, vendor selections, and architecture decisions.
alexandremendoncaalvaroDraft an Architecture Decision Record from a conversation into a numbered ADR file.
apply-theRecord explicit approvals against Canon gates with RUN_ID, TARGET, DECISION, and RATIONALE.
caozx1110Archive technical chat discussions into structured Markdown notes.
takusaotomeReview meeting minutes for missing sections, action items, decisions, and clarity.
