ballot

Create durable per-decider ballot files with Must/Should/Could tiers.

2|Updated Feb 7, 2026

Search Tags:#decision #async #review #reconciliation #dossier #sessionlog #ballot

Ready to run

npx skills add https://github.com/eins78/agent-skills --skill ballot

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

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.

Core Features & Use Cases

One file per decider to keep surfaces readable on small screens and enable clean diffs.
Must / Should / Could tiering to express urgency and impact.
Reconciliation happens in the sessionlog to separate durable artefacts from discussion notes.
Standalone or dossier-invoked usage with a consistent template and reference materials.

Quick Start

Create a ballot file per decider using the provided template and fill each DEC with a single decision surface and a clean cover block.

Frequently Asked Questions about ballot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I track asynchronous decisions for code reviews and sign-offs outside of a live session?▼

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.

What's the best way to create an auditable record for architecture decisions and vendor selections?▼

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.

How does sessionlog reconciliation work for asynchronous decision-making?▼

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.

Can I use a Must/Should/Could tiering format for hiring panel and PR handoff reviews?▼

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.

Does the ballot skill work as a standalone tool or does it require a dossier?▼

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.