Results for “budget-justification”

Plan and review paid-media budgets, bidding, pacing, marginal return, forecasts, CPA, ROAS, MER, LTV:CAC, constraints, and allocation across supported platforms.

`analysis-agent`/`task-agent`/`review-agent`: use when latency, throughput, bundle, memory, CPU, query, rendering, or resource cost needs a budget; skip without performance risk.

Audits Claude Code context window consumption across agents, skills, MCP servers, and rules. Identifies bloat, redundant components, and produces prioritized token-savings recommendations.

Audits Claude Code context window consumption across agents, skills, MCP servers, and rules. Identifies bloat, redundant components, and produces prioritized token-savings recommendations.

Intercepts responses to let users choose the depth and token budget before answering, with heuristic token estimation and preset depth levels.

Context window monitoring and budget management. Keeps orchestrator at 15-30% context usage while subagents get full 200k tokens. Provides warnings at thresholds, context-aware summarization triggers, and wave-level budget planning.

Build event budgets with categories and contingency. TRIGGERS - Use when user needs help with event-budget related tasks.

Build event budgets with categories and contingency. TRIGGERS - Use when user needs help with event-budget related tasks.

Use to audit arrears, collections and financial-difficulty conversations for fair treatment — forbearance offered, pressure absent, vulnerability recognised. Trigger for "audit our collections calls", "are we treating customers in arrears fairly", "did we offer forbearance", financial difficulty handling, payment plan conversations, or a complaint about collections conduct.

Diagnose paid-ad campaigns and draft or apply optimizations using evidence, financial constraints, and experiments. Supports budget reallocation, bid changes, creative rotation, and CPA/ROAS improvement.

Write clear design rationale that connects decisions to user needs, business goals, and principles.

Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments for a product or feature.

Use to audit whether similar customers with similar failures received similar redress, and to find variation that could not be defended. Trigger for "are our refunds consistent", "do we compensate similar cases the same way", "audit our goodwill decisions", redress fairness review, customers who escalate getting more, or a complaint that someone else was treated better.

Prüft E-Rechnungen auf Frist, Form, Zuständigkeit und Rechtsweg; liefert eine Fristen- und Risikoampel mit Sofortschritten.

Compress selected context to a target token budget while preserving decisions, evidence, constraints, and unresolved questions. Use when relevant material is already selected but too long; use context-optimization when selection, deduplication, and ordering are also required.

Identify, categorize, and prioritize technical debt into a ranked, defensible backlog that ties each remediation to impact and effort — a register, not a wish list.

Google and Meta paid media account structure evaluation. Audits campaign/ad set architecture against conversion volume minimums, budget thresholds, and targeting overlap. Identifies over-segmentation, under-segmentation, budget fragmentation, and structural anti-patterns blocking algorithmic learning. Provides consolidation roadmaps with migration plans. Use when inheriting accounts, quarterly health checks, or before scaling budgets.

Use to analyse billing and pricing complaints, separating genuine pricing objections from billing defects and unclear communication. Trigger for "customers complaining about price", "billing complaint analysis", "why do customers dispute their invoice", "is our pricing a problem", unexpected-charge complaints, or a pricing decision that needs evidence from support.

Access and manage YNAB budgets programmatically: list budgets, accounts, categories, and transactions, and create new transactions with optional filters.

Create and manage budgets with variance analysis and departmental allocation. Use when the user requests budget planning or provides relevant inputs for this workflow.

Per-page UX audit using NN/g heuristics, Intuit microcopy, and Google HEART. Use when evaluating usability, auditing microcopy, checking UX heuristics, or assessing cognitive load. Cross-page flows/IA → audit-ux-journeys. Layout/breakpoints → audit-responsive. Empty/error states → audit-ui-states.

Optimize Kubernetes cluster costs by right-sizing resources, configuring autoscalers, using spot instances, and monitoring spend.

Compress bloated project or global memory while preserving decisions, rationale, revisit triggers, provenance, and active user preferences. Load when memory exceeds budget, global memory is too large, session logs are repetitive, or before appending to an over-budget memory file.

Short clarifying interview before starting non-trivial engineering work — surfaces the actual requirement, what's explicitly out of scope, and what proves it's done. Use before writing code when the task's requirement, scope, or definition of done isn't already unambiguous. Not for trivial or fully-specified changes — that's ceremony, not clarity.

Debt that exists only in engineers' heads cannot be prioritised, funded, or

Audits over-engineered codebases by factoring layers into live obligations, quotienting redundant distinctions, ablating unearned surface, and normalizing survivors while preserving required behavior. Produces an evidence-backed Reduction Certificate, cuts, migration phases, proof signals, and rollback.

Cost-benefit analysis. Produces economic NPV and financial NPV side by side, with BCR, optimism bias (with mitigation), Marginal Excess Tax Burden, real-terms rebasing, WELLBY / QALY / VPF wellbeing valuation, sensitivity, switching values, EANC for unequal-life options, validation gate, and a one-line headline verdict (socially worthwhile vs financially self-sustaining). Backed by the greenbook R package (HM Treasury Green Book primitives) when available, with graceful fallback. Supports HMT Green Book, EU Better Regulation, World Bank, ADB, and Victorian HVHR. Reads a longlist markdown file directly via --from.

Use when content is verbose, repetitive, or padded and needs tightening while preserving meaning

Provides evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflows for sales snapshots, pricing comparisons, duplicate-charge diagnosis, or code-backed billing reality.

Use to verify that the chain from conversation to evaluation to decision is complete and reconstructible, so a QA score or a customer outcome can be explained months later. Trigger for "can we prove why this decision was made", "is our audit trail complete", "reconstruct how this score was produced", evidencing an AI-assisted decision, or an auditor asking how a conclusion was reached.

Optimize a complete candidate context package by deduplicating, filtering, ordering, and allocating its token budget. Use when retrieved or assembled material is noisy or exceeds the useful context budget; use context-ranking for scoring chunks and context-compression for shrinking selected content.

Prüft Frist, Form, Zuständigkeit, Rechtsweg und Sofortmaßnahmen für Behörden-, Gerichts- oder Registerwege in der Liquiditätsplanung und liefert eine Fristen- und Risikoampel mit Sofortschritten.

Derive selection thresholds from market data instead of hardcoding. Trigger when: (1) reviewing hardcoded parameters, (2) volume/price thresholds seem arbitrary, (3) selection returns too many/few candidates.

Use to build a defensible cost per contact and cost to serve by driver, channel or customer segment, for automation business cases and budget decisions. Trigger for "what does a ticket cost us", "cost per contact", "what would automating this save", "cost to serve by segment", building a business case for a bot or a process change, or a savings claim that looks too good.