DM

    decision memo pack

    1

    Turn messy business options and evidence into structured, decision-ready memos with scorecards and action plans.

    $19

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseOpenClawOpenClaw+21 more
    DM

    decision memo pack

    Example session with this skill installed

    decision_question: Should we migrate our monorepo to microservices?
    audience: CTO and Engineering Leads
    options: Stay monorepo; Extract 2 core services; Full microservice migration
    criteria: Developer velocity, infra cost, complexity
    context: 20 devs, deployment bottlenecks growing
    evidence: Last month had 4 deploy failures due to merge conflicts.
    deadline: Q3 planning session
    risk_tolerance: balanced

    • Read your context and instructions
    • Compiled the decision memo
    • Generated the document

    I have drafted a decision memo regarding the potential migration from a monorepo to microservices based on your current deployment bottlenecks.

    Decision memo: Monorepo vs. Microservices Migration

    Decision question: Should we migrate our monorepo to microservices?
    Audience: CTO and Engineering Leads
    Decision deadline: Q3 planning session
    Context / horizon: 20-person engineering team facing deployment bottlenecks; seeking balance between velocity and infra overhead.
    Generated: 2023-10-27 · Draft for human verification — not advice

    1. Decision at a glance

    Recommendation: Extract 2 core services (Hybrid approach)
    Confidence: medium
    Why: A full migration introduces excessive infrastructure complexity for a 20-person team. Extracting the most congested services addresses the immediate deployment failures while limiting the operational tax.

    2. Decision frame

    • Success conditions: Reduced deployment lead time, zero failures due to cross-team merge conflicts.
    • Constraints: Limited DevOps headcount to manage new infrastructure.
    • Assumptions: Current deployment failures are primarily caused by tight coupling, not build tooling.
    • What is in / out of scope: Infrastructure automation is in scope; rewriting frontend code is out of scope.

    3. Options and scorecard

    OptionFit to criteriaUpsideTrade-offsEvidence / confidence
    Stay monorepoLowZero infra cost increaseContinued bottlenecksHigh / Deploy logs
    Extract 2 servicesHighTargeted reliefIncremental complexityMedium / Team size
    Full migrationMediumMax autonomyHigh infra overheadLow / Tooling gaps

    4. Recommendation and decision gates

    The hybrid approach (Option 2) allows us to isolate the domains causing 80% of the merge conflicts without over-engineering the entire stack. We should proceed if the pilot service extraction reduces build times by >30%.
    Gates:

    1. Successful PoC of inter-service communication.
    2. Deployment failure rate remains below 1% for the new services.

    5. Risks and dependencies

    Risk / dependencySeverityEarly warningMitigation / owner
    Increased latencymediumP99 monitoring spikesImplement gRPC
    Operational overheadhighDevOps ticket backlogStandardize CI/CD

    6. Action plan

    WhenActionOwnerSuccess check / gate
    NowAudit logs to pick top 2 service candidatesLead DevCandidates identified
    7 daysDefine service boundaries and API contractsArchitectDocumentation signed off
    30 daysDeploy first service to stagingDevOpsGreen CI/CD pipeline
    90 daysDecommission original code in monorepoLead Dev0 calls to old path

    7. Open questions and source placeholders

    1. [VERIFY: Actual cost of AWS Managed Prometheus for service monitoring.]
    2. [SOURCE: Deployment failure logs from September — URL TBD]

    8. Suggested next step

    Schedule a 30-minute technical review to select the two specific services for the pilot extraction based on recent deployment conflict data.

    Next steps

    • Review the scorecard to ensure the weights for "infra cost" align with the Q3 budget.
    • Replace the [SOURCE] placeholder with the link to your deployment logs.
    • Assign owners to the initial 7-day action items.

    decision-memo-pack.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    What you get

    Compare business options using weighted criteria and evidence scorecards.Generate structured risk assessments with early warning signs and mitigations.Define clear 7/30/90-day action plans to move decisions into execution.Document decision records for stakeholders to ensure long-term alignment.

    About this skill

    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.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean today

    • Passed all security checks, Safe to install

    Listedtoday

    What's inside

    Frequently Asked Questions