Make Faster Business Decisions — Decision Memo Pack

Unlike free "help me decide" prompts that pick an answer and back-fill reasons, this skill always scores a do-nothing option, labels the confidence of every piece of evidence, sets go/stop decision gates and leaves [VERIFY] slots instead of inventing numbers. Sample output (excerpt; input: 20-dev team, 4 deploy failures last month, options stay monorepo / extract 2 services / full microservices): Recommendation: Extract 2 core services (hybrid) · Confidence: medium | Option | Fit | Upside | Trade-off | Evidence / confidence | |---|---|---|---|---| | Stay monorepo (do nothing) | Low | No new infra cost | Bottlenecks continue | High / deploy logs | | Extract 2 services | High | Targeted relief | Some new complexity | Medium / team size | | Full migration | Medium | Max team autonomy | Heavy infra overhead | Low / tooling gaps | Decision gates: proceed only if the pilot service cuts build time by more than 30% and its deploy failure rate stays under 1%. | When | Action | Owner | Gate | |---|---|---|---| | 7 days | Define service boundaries + API contracts | Architect | Docs signed off | | 30 days | First service live in staging | DevOps | Green CI/CD | | 90 days | Remove old code path from monorepo | Lead Dev | 0 calls to old path | Open questions: [VERIFY: monitoring cost per service] · [SOURCE: September deploy failure logs] You get 8 fixed sections every time: decision at a glance, decision frame, options scorecard, recommendation + gates, risks with early warnings, action plan, open questions, next step. Works in Claude Code, Cursor and Codex · no invented stats or ROI · v1.0, updated Oct 2026 · questions answered via Agensi messages within 24h · More Cygnix Labs tools: https://apify.com/cygnix_labs Business decisions often stall due to messy evidence and unclear trade-offs. This skill converts raw notes and conflicting options into a structured decision memo that helps stakeholders choose a path and begin execution. ## What it does - **Frames decisions** by clarifying success conditions, constraints, and underlying assumptions. - **Scores options** using a comparative matrix that weighs pros, cons, and evidence confidence levels. - **Identifies risks** by mapping potential failure points to specific early warning signs and mitigations. - **Generates action plans** with structured 7, 30, and 90-day milestones to move from choice to implementation. - **Flags gaps** by explicitly listing open questions and data points that require human verification or sourcing. ## How it works 1. **Define the inputs** by providing the decision question, intended audience, and at least two available options. 2. **Review the draft** as the skill structures your evidence into a scorecard and recommendation. 3. **Verify placeholders** by replacing bracketed source tags with actual data or internal documentation. ## Frameworks & tools This skill uses standard Markdown for document structure and is designed for use in environments like Claude Code, Cursor, or ChatGPT. ## Why this beats prompting it yourself Writing decision memos from scratch often leads to confirmation bias or missing risk factors. This skill enforces a consistent, objective evaluation framework that separates facts from inferences, ensuring you never skip the "do nothing" option or fail to define decision gates. ## Use cases - **Build vs. Buy** evaluations for new engineering tools or infrastructure. - **Product prioritisation** memos for deciding which feature to pilot next quarter. - **Vendor selection** reports comparing different service providers against cost and fit. - **Go/No-go assessments** for market entry or new project launches. ## Known limitations Does not provide regulated advice for legal, medical, tax, or investment decisions. Requires a human to provide core evidence as it cannot access private internal metrics or live market data.