DecisionDeck

Problem

When there is already a lot of material, the real decision often stays buried under summaries, theme clusters, and 'both sides have points' framing. decisiondeck targets the layer after information gathering: compress documents, meeting notes, proposals, and research notes into a one-page brief that can go straight into a decision meeting, not another long summary.

How It Works

It first identifies the actual decision and audience, then separates messy input into facts, repeated signals, constraints, positions, assumptions, and unknowns. Key steps include:

• Rewrite mixed goals, approaches, and implementation details into comparable options
• Mark conflicts between sources and judge whether they change the call
• Label evidence as directly supported, inferred from multiple signals, weak, or missing
• End with the recommended option, why it holds now, what would change the call, and the next step

Boundaries

It fits 'one page for the boss, client, or project owner,' 'reconcile conflicts,' and 'go/no-go' requests. If the main need is cross-document retrieval, relationship discovery, or an execution plan, pair it with a knowledge connector or next-action skill. When input is messy, normalize it and still drive toward a decision; when evidence is thin, say so explicitly instead of hiding uncertainty behind more summaries.