The Tool Catalog

Every tool in the toolbox, navigable by what you do.

The toolbox federates the whole universe of corpus-grounded analytics tools — and that universe crosses every area of focus. Filter it down to the lens you need: the Marketing view is the GTM toolbox, Compensation the comp toolbox — subset views of one catalog, never separate copies. Every tool runs on peopleanalyst.com and is federated to agents over MCP.

89 tools · 8 focus areas

Browse the catalogTry a two-minute wizard

The catalog

89 tools, filterable by focus area.

Pick a focus area to scope the universe to one lens, or search across all of it. Each card shows what a tool does, what it takes in and gives back, and links to run it.

Focus area

8 of 89 tools · Software engineering

Systems practice — architecture, reviews, reliability, tech-debt.

Application Designs

Software engineering

Get the technical blueprint — architecture, stack, components, phases — for any product idea.

In
{ text, sourceType?: deep_research|book|research, sourceId?, title?, author? }
Out
ApplicationDesignCanonical[] (architecture · stack · data model · features · flows · phases)

run it on peopleanalyst.com →

Architecture Decision Record

Software engineering

Describe a decision — get a clean Architecture Decision Record (Nygard form).

In
{ decision, cluster? }
Out
{ decision_summary, title, status, context, decision, options_considered[]{option, pros[], cons[]}, consequences{positive[], negative[]}, riskiest_assumptions[], grounded_in, provenance }

run it on peopleanalyst.com →

Code Review Checklist

Software engineering

Describe a project — get a context-fit code-review rubric.

In
{ context, cluster? }
Out
{ context_summary, categories[]{category, checks[]}, blocking[], nits[], automation_suggestions[], riskiest_assumptions[], grounded_in, provenance }

run it on peopleanalyst.com →

Incident Postmortem

Software engineering

Describe an incident — get a blameless postmortem with typed action items.

In
{ incident, cluster? }
Out
{ incident_summary, impact, timeline[]{when, what}, root_cause, contributing_factors[], what_went_well[], action_items[]{action, type, owner_hint}, riskiest_assumptions[], grounded_in, provenance }

run it on peopleanalyst.com →

Requirements

Software engineering

Paste an idea (or book, study, report) — get a PRD-grade, MVP-scoped backlog.

In
{ input, sourceType: business_idea|deep_research|book|research, sourceId? }
Out
RequirementCanonical[] + gap report (missing/weak fields)

run it on peopleanalyst.com →

SLO Definer

Software engineering

Describe a service — get user-centric SLIs, SLOs, and an error-budget policy.

In
{ service, cluster? }
Out
{ service_summary, slis[]{sli, definition, measurement}, slos[]{objective, target, window}, error_budget_policy, alerting_notes[], riskiest_assumptions[], grounded_in, provenance }

run it on peopleanalyst.com →

System Design Review

Software engineering

Describe a design — get a senior design review with risks + recommendations.

In
{ design, cluster? }
Out
{ design_summary, strengths[], risks[]{risk, severity, mitigation}, scalability_notes[], failure_modes[], open_questions[], recommendations[], riskiest_assumptions[], grounded_in, provenance }

run it on peopleanalyst.com →

Tech Debt Register

Software engineering

Describe a system — get a rated, prioritized tech-debt register.

In
{ context, cluster? }
Out
{ context_summary, items[]{item, impact, effort, risk_if_ignored, priority}, quick_wins[], sequencing[], riskiest_assumptions[], grounded_in, provenance }

run it on peopleanalyst.com →

Want a drop-in for the tool you already use?

The catalog above runs on peopleanalyst.com. When you want the same capability inside Google Sheets, Excel, Power BI, or Tableau, the Store packages it as a drop-in.

Browse the StoreDescribe your problem