AI Decision Memo Builder

    1

    Turns messy transcripts and notes into structured, decision-ready memos with clear trade-offs and recommendations.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    AI Decision Memo Builder

    Example session with this skill installed

    Build a one-pager based on our chat: We need to choose between AWS and Supabase for the new MVP. AWS is cheaper at scale but harder to set up. Supabase is fast but we worry about vendor lock-in.

    • Read your context and instructions
    • Compiled the ai decision memo

    I have drafted a one-page decision memo based on your comparison of AWS and Supabase, focusing on the trade-offs between speed-to-market and long-term scalability.

    Decision Memo: MVP Infrastructure Selection

    Date: 2023-10-27
    Decision Owner: Engineering Lead
    Audience: Product Stakeholders
    Decision Needed By: Friday, Oct 31

    Decision and Recommendation (BLUF)

    Recommendation: Proceed with Supabase for the MVP phase.
    Action: Approval to begin implementation immediately to meet the November launch deadline.

    Context

    We need to select a backend infrastructure provider for our MVP. The primary driver is a tight launch window (4 weeks), balanced against long-term cost and architectural flexibility.

    Options Considered

    1. Supabase (Recommended): Managed Backend-as-a-Service.
    2. AWS (EC2/RDS/S3): Traditional cloud infrastructure.
    3. Do Nothing: Delay launch to evaluate further providers.

    Criteria and Comparison

    CriteriaSupabaseAWS
    Setup SpeedHigh (Pre-built Auth/DB)Low (Manual configuration)
    Scaling CostModerate (Tiered pricing)Low (Granular control)
    Vendor Lock-inHigh (Proprietary API)Low (Standard Postgres/S3)
    MaintenanceLow (Serverless/Managed)High (DevOps required)

    Analysis and Trade-offs

    Supabase is the recommended choice because it reduces initial development time by approximately 40%, ensuring we hit the MVP launch date. The primary trade-off is

    vendor lock-in; migrating away later will require rewriting the auth and database logic. However, the risk of missing the market window outweighs the cost of a future migration.

    Risks and Mitigations

    Risk: Scaling costs exceed budget if users grow 10x.

    Mitigation: Set billing alerts at $200/mo and plan a migration path to RDS if we hit 50k MAUs.

    • Risk: Vendor lock-in. Mitigation: Use standard SQL for all business logic to keep data portable.

    Next Steps

    1. Approve recommendation: Project Lead by Oct 28.
    2. Provision Supabase Project: DevOps by Oct 29.
    3. Set Billing Alerts: [needed] by Oct 30.

    Open Questions and Assumptions

    • Assumptions: We assume the current budget for infrastructure is under $500/mo for the first quarter.
    • Uncertainty: Exact AWS configuration costs are [needed] for a direct price comparison at scale.

    Next steps

    • Provide the specific budget limit to refine the scaling cost analysis.
    • Confirm who will be responsible for setting the billing alerts.
    • Request a "Review" if you want me to tighten the language for an executive audience.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Decisions often stall because the logic is scattered across chat threads, meeting transcripts, and messy notes. This skill converts raw project context into a professional, decision-ready memo that allows stakeholders to approve, reject, or challenge a recommendation in minutes.

    What it does

    • Extracts briefs by identifying decision owners, deadlines, options, and constraints from disorganized input.
    • Builds comparison tables that evaluate multiple real options against consistent criteria like budget and risk.
    • Surface trade-offs to ensure the recommended path is presented alongside its costs and potential downsides.
    • Identifies gaps by marking missing data, names, or figures as assumptions rather than inventing facts.
    • Adapts formats ranging from 100-word executive summaries to 1,000-word deep dives for high-stakes choices.

    How it works

    1. Input analysis: Provide a transcript, note, or draft, and the skill identifies the core decision and stakeholders.
    2. Gap handling: The skill makes professional assumptions for minor gaps or asks up to three targeted questions for critical missing data.
    3. Drafting: It generates a structured memo including a BLUF (Bottom Line Up Front), analysis, and risk mitigations.
    4. Refinement: Use specific modes like "Review" to critique existing drafts or "Adapt" to turn a memo into a Slack message.

    Frameworks & tools

    This skill is platform-agnostic and designed for use within LLM environments like Claude, ChatGPT, or Cursor. It outputs standard Markdown compatible with GitHub, Notion, and Slack.

    Why this beats prompting it yourself

    Standard prompts often produce generic summaries or "straw man" arguments that lean too hard into a favorite option. This skill enforces strict neutrality, mandates the inclusion of a "do nothing" option, and uses a structured quality check to ensure trade-offs and risks are never buried.

    Use cases

    • Vendor selection: Comparing software tools against budget, security, and feature sets.
    • Build vs. Buy: Documenting the logic for developing internal tools versus licensing third-party tech.
    • Hiring decisions: Summarizing candidate evaluations for a final "go/no-go" from leadership.
    • Strategic pivots: Justifying changes in product direction or budget reallocations to a board.

    Known limitations

    Does not provide professional legal, tax, or medical advice. Requires user-provided data as it will not search external databases or invent missing financial figures.

    Does not replace professional legal or financial advice. Will not invent facts; missing data is flagged as [needed]. Requires user-provided context or transcripts to function.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Permissions

    No special permissions declared or detected

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill is designed to run in any major LLM environment, including Claude, ChatGPT, and Cursor. It generates standard Markdown output that can be instantly pasted into Notion, Slack, or GitHub for immediate team review.

    Unlike standard AI summaries, this skill uses a structured 'quality check' to prevent bias. It forces the inclusion of trade-offs, a 'do-nothing' option, and risk mitigations, ensuring you present a neutral, high-stakes evaluation rather than just a generic summary.

    If your notes are missing key data like budget or specific deadlines, the skill identifies these as 'assumptions' or asks up to three targeted questions. This ensures the final memo remains grounded in reality rather than inventing facts to fill the gaps.

    You receive the complete system logic and structured templates required to deploy the Decision Memo Builder in your preferred AI workspace. This includes specific configurations for different output modes like 'Review' and 'Adapt.'

    This skill is best suited for complex project choices like vendor selection, 'Build vs. Buy' scenarios, hiring decisions, and strategic pivots where clear logic and stakeholder alignment are required.

    New in Business & Operations