Workflows

Business work

Research competitors with sources

Produce a useful competitor comparison with traceable facts, dates, and explicit uncertainty.

CodexClaude CodeCursor

What you will work toward.

A decision-oriented comparison tied to a defined customer need and current primary sources.

Prepare my brief

Make this workflow yours.

Choose your AI tool, describe your task, and copy one complete project brief. Your inputs stay in this tab.

Includes your prompt, selected references, skill instructions, setup steps, and checks. Use your own AI account; Pristren does not run a model here.

Describe your project or task to prepare your brief.

Read the complete brief
Research competitors for [Describe the project, audience, and useful result.] within Use existing project conventions. State assumptions and verify the result..

Define the customer, decision, geography or market if relevant, and comparison criteria. Select a small defensible shortlist instead of a broad directory. Find current official product pages, documentation, pricing, and relevant release notes. Record each source URL and the date checked. Seek evidence for the exact feature or qualification being compared.

Build a concise comparison around the customer’s real task. Separate verified facts, vendor claims, your interpretation, and unknowns. Include plan restrictions, usage limits, integrations, migration costs, and pricing currency or billing conditions where relevant. A missing mention is not proof a feature does not exist. Do not invent account access or hands-on testing.

Explain where each option fits and what would change the decision. Cite sources next to important claims and identify any stale, inaccessible, or conflicting evidence. Finish with unresolved questions and a small next validation step. Do not contact companies, send pitches, or publish the research unless separately authorized.

Execution environment: Codex. Follow applicable project instructions and verify the requested result.

Workflow
https://pristren.com/workflows/research-competitors/

Expected result
A decision-oriented comparison tied to a defined customer need and current primary sources.

Before you begin
- The business question and target customer.
- A shortlist or a clear category and selection rule.
- Access to official product, documentation, and pricing pages.

Setup for Codex
- Start Codex in the repository and read applicable AGENTS.md guidance. Include only the files this task needs.
- Research primary sources, date each observation, and distinguish official claims from your own analysis.
- Use the acceptance checks below to assess the result; an agent completion message is not evidence that the task passed.

Selected resources
- Research competitors with sources — master prompt: https://pristren.com/resources/research-competitors-prompt/
  Use the task-specific master prompt above.
- Build reports from evidence: https://pristren.com/resources/evidence-led-report/
  Use the published resource’s Download SKILL.md action, or copy its complete original SKILL.md text. Draft resources are not publicly downloadable.
  Save the supplied SKILL.md as .agents/skills/evidence-led-report/SKILL.md in the project. Review it before use.
  Open the project in your tool and select evidence-led-report by name; check that it resolves to this project-local version.
  Read the resource below and apply only the parts relevant to the current task.
  Inspect the loaded skill before using it on a representative task. This page documents setup; it has not performed the installation for you.
  mkdir -p .agents/skills/evidence-led-report

Skill instructions (Build reports from evidence)
---
name: evidence-led-report
description: Produce a sourced research or business report from supplied data while keeping observations, calculations, and recommendations distinct.
---

# Evidence-led report

Define the question, audience, time range, and unit of analysis before drawing conclusions. Identify the source of each input and whether it is current enough for the question. Ask only for missing information that would materially change the result.

Keep a working evidence record: source URL or artifact, checked date, claim supported, scope or plan qualifier, and uncertainty. Missing documentation means unverified; it does not establish that a capability is absent. A vendor claim is not a hands-on benchmark.

For calculations, state units, denominators, exclusions, and transformations. Check that totals reconcile and distinguish zero from missing values. Do not turn views into unique people, a download into a successful implementation, or an enquiry into a paying client.

Write the report around the answer and the evidence needed to assess it. Separate observed facts, interpretations, and proposed actions. Cite close to the supported statement. Include material limitations and make recommendations proportional to the evidence.

For a repeatable report, describe the expected inputs and validation checks so a later run can reject stale or malformed data. Drafting a report does not authorize sending it, publishing it, or modifying the source system.


Execution
1. Define the customer decision, criteria, and shortlist rule.
2. Collect current primary evidence and dated source notes.
3. Compare the task-relevant capabilities and commercial qualifications.
4. Write fit, tradeoffs, unknowns, and the next validation step with citations.

Acceptance checks
- Material factual claims have direct primary source links.
- Pricing includes relevant currency, billing, or usage qualifications.
- Unknown and untested behavior is labelled explicitly.
- The recommendation follows the stated customer criteria.

If something fails
- A pricing page hides exact limits: Record the omission and the visible qualification; avoid inventing a number or assuming unlimited use.
- Sources disagree: Compare publication dates and scope, preserve the conflict, and identify which claim needs confirmation.

Inspect the project first. Report the changes, the checks actually run, and anything still unresolved. Ask before any deployment or external publication.
Tool setup and prerequisites
Documentation reviewedChecked 2026-11-17

Tool setup checked against official documentation. Pristren has not executed this workflow through this tool.

  1. Start Codex in the repository and read applicable AGENTS.md guidance. Include only the files this task needs.
  2. Research primary sources, date each observation, and distinguish official claims from your own analysis.
  3. Use the acceptance checks below to assess the result; an agent completion message is not evidence that the task passed.
Official setup documentation

Before you begin

  • The business question and target customer.
  • A shortlist or a clear category and selection rule.
  • Access to official product, documentation, and pricing pages.
Skills and tools included in your brief

Required resources are included. Add optional ones when your task needs them.

Research competitors with sources — master prompt

Required

Start with this workflow’s original task-specific master prompt.

Review instructions
Build reports from evidence

Required

Separate observations, interpretation, and unresolved questions.

Review instructions
Context7

Optional

Look up technical package documentation when integration behavior matters.

Review instructions

What your AI will work through.

  1. Define the customer decision, criteria, and shortlist rule.
  2. Collect current primary evidence and dated source notes.
  3. Compare the task-relevant capabilities and commercial qualifications.
  4. Write fit, tradeoffs, unknowns, and the next validation step with citations.

Check the result before calling it done.

  • Material factual claims have direct primary source links.
  • Pricing includes relevant currency, billing, or usage qualifications.
  • Unknown and untested behavior is labelled explicitly.
  • The recommendation follows the stated customer criteria.

When something gets in the way.

A pricing page hides exact limits

Record the omission and the visible qualification; avoid inventing a number or assuming unlimited use.

Sources disagree

Compare publication dates and scope, preserve the conflict, and identify which claim needs confirmation.

How did your attempt go?

Try the brief in your AI tool first. Your feedback helps us find workflows that need attention.

Sources and review notes