Pricing Change Decision Memo with Scenarios and Risks
Produce a decision memo that compares pricing options using your numbers, with scenario math, customer risk, and a test plan. Helps a founder or manager decide whether to change prices and how.
341 prompts · last added
49 results for “risk-assessment” · page 1 of 3
Produce a decision memo that compares pricing options using your numbers, with scenario math, customer risk, and a test plan. Helps a founder or manager decide whether to change prices and how.
Maps a current team workflow, finds bottlenecks and handoff failures, designs a leaner future-state process with roles and automation candidates, and outlines a low-risk pilot with success metrics.
Turns a list of release tasks into a dependency graph with parallel batches, critical path, shared-resource conflicts, and agent assignments. Supports the decision on what to run now versus wait on.
Guides a source-backed evaluation of software or service vendors against weighted criteria. Ends with a decision memo covering risks, open questions, and verification steps before purchase.
Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then applying small reversible steps with verification after each. Delivers a diff, risk register, and rollback plan.
Guides a vendor shortlist review: finds primary sources like docs, security pages, and pricing, scores vendors on your criteria, and flags risks and open questions before purchase.
Produces a developer-ready component specification covering anatomy, variants, states, tokens, accessibility, and open questions from a short component brief.
Plans and executes a library or framework version migration in Cursor in small, verifiable batches, with an impact inventory, rollback points, and per-batch test gates instead of one risky bulk edit.
Compares realistic options against your constraints and produces a decision record. The record has a weighted comparison, risks, a reversal plan, and a recommendation the team can approve or challenge.
Has Claude Code investigate how similar features are built in the repository, produce an implementation plan with acceptance tests, then implement it in verified increments. Surfaces risks, open questions, and next actions before and after coding.
Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then making small, reversible commits. Helps you decide whether the refactor preserved behavior and is worth merging.
Has Codex review a branch diff against a base ref in read-only mode. It checks correctness, tests, security, and maintainability, and returns evidence-backed findings with severity and a merge recommendation.
Turns a pasted feature spec into independent coding-agent tasks with file ownership, interface contracts, a merge order and a done command for each task.
Analyzes a recurring manual task and produces an automation blueprint with trigger, steps, data mapping, error handling, and a test plan. It also helps you decide whether the task is worth automating at all.
A save-ready SKILL.md that has your coding agent review a branch before merge: correctness, security, tests and migrations, with findings ranked by severity and no style nitpicks.
Diagnoses what a price objection really means and builds response scripts, trade-based concession rules, and escalation criteria. It helps a rep decide whether to hold price, trade scope, or walk away.
Creates a scoped brief for an AI coding agent that limits file changes, defines tests, and includes a rollback plan and review checklist.
Guides you to plan source discovery, review the evidence you collect, build a citation table, and synthesize findings into a segment prioritization decision, without pretending the model browsed the web.
Combines your Docs, Sheets, meeting notes, and outside sources into one decision memo. Separates internal evidence from external research and logs conflicts, gaps, and next actions.
Claude Code interviews you briefly about a repeated workflow and writes a complete SKILL.md with a precise trigger description, steps, supporting files and a verification step.
Produces a set of testable guardrail rules for your coding agent, covering blocked commands, approval gates, secret handling and hook checks.
Has Claude Code review a branch diff like a skeptical maintainer, producing severity-ranked findings with evidence and a clear merge, fix, or block recommendation. Use it before opening or approving a pull request.
Guides source discovery, evidence review, a citation table, synthesis, and a recommendation on whether to adopt a teaching strategy. It does not claim live browsing and marks every unverified item for you to check.
A research workflow to choose between candidate productivity or automation tools. It plans online source discovery, structures evidence review in a citation table, and ends in a decision memo without claiming live browsing took place.
Guide
Nothing that fits? Write a prompt with AI.
341 copy-ready prompts for productivity, writing, business and coding and more. Each one sets the role, the steps and the output format, and marks the parts you fill in with curly brackets.
Most are written for ChatGPT (285), Gemini (260), Claude (217) and Claude Code (42); the number is how many prompts list that tool. Each prompt page lists its tools, and most text prompts also work in any capable chat model.
Words in curly brackets, such as {audience}, are the parts you replace with your own details. Choose “Ready to use (no blanks)” in the filters to see prompts you can paste as they are.
By how often they are copied, unless you choose another order. Newest shows the latest additions first. Trending ranks prompts by copies, opens and saves over the last two weeks.
No. Every prompt is free to copy or open in your AI tool. A free account lets you save prompts to your vault.
Yes. Write with AI asks what you need, builds a short form for it, and writes the prompt as you fill it in.