Prompt Cards

From <org plan> and <targets>, create a headcount plan by team, location, and level. Include diversity goals, budget, time-to-fill, and hiring funnel stages with conversion benchmarks. Output a dashboard spec and weekly stand-up ritual.

Evaluate vendors from <contracts> and <usage>. Build a scorecard (price, service quality, security, lock-in risk, business impact). Recommend renew, renegotiate, or replace with quantified ROI and switching costs. Include a negotiation brief.

Draft an investor update: highlights, product and GTM progress, key KPIs, GAAP vs non-GAAP reconciliation, customer logos, pipeline, hiring, risks, and asks. Include a metrics table and a concise narrative suitable for email and deck.

Create a monthly BvA for each department from <budget> and <actuals>. Show variance absolute and percent, drivers, and corrective actions. Roll up to consolidated forecast update and cash impact. Provide a CFO talking points script.

For product <name>, compute unit economics: revenue mix, discounts, gross margin, CAC payback, LTV/CAC, and contribution margin. Recommend price tiers and packaging. Provide a waterfall from list to net. Include risks and an experiment plan.

Build a 18-month cash runway model from <starting cash> and <burn profile>. Run base, conservative, and aggressive scenarios. Include hiring plan effects, COGS, FX risk, debt covenants, and sensitivity to revenue slip. Output a table and key levers to extend runway.

Threat-model feature <feature> using STRIDE. Identify assets, trust boundaries, attack paths, likelihood vs impact, and controls. Map mitigations to standards (ISO/IEC 27001, SOC 2). Output a table of threats, controls, residual risk, and test cases.

Prioritize <backlog> using RICE scoring. Show score breakdown, dependencies, risk heat, and hiring needs. Produce a quarter-by-quarter roadmap, capacity assumptions, and a cutline. Include a one-pager per epic with acceptance criteria and success metrics.

Create a blameless postmortem for incident <id>: timeline, customer impact, 5 Whys, contributing factors, detection gaps, and corrective actions. Propose guardrails, SLO/SLA adjustments, runbooks, and 30-60-90 follow-ups with Jira tickets and owners. Provide an executive summary.

For workload <service>, model 12-month capacity and cloud cost. Include CPU/GPU, storage, egress, and LLM inference. Compare reserved vs spot vs savings plans. Map to SLOs and traffic seasonality. Output a table with monthly forecast, a rightsizing plan, and a cost-to-serve KPI per user.

Generate an ADR for <system change>: context, decision, options considered, trade-offs (latency, throughput, cost), failure modes, rollback plan, security and privacy impact, data migration, and observability updates. End with acceptance criteria and sign-offs.

Draft the next all-hands: agenda, metrics snapshot, wins, customer stories, shout-outs, and upcoming priorities. Include an anonymous tough Q\&A section with concise, values-aligned answers. Add a morale pulse (1-5), follow-up actions, and a 30-day communication plan.