Linear vs monday.com

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Linear~partialclaimed6/10

   Linear's developer docs are exposed as clean .md pages (agents.md, graphql.md, webhooks.md, sdk.md, aig.md), a pattern consistent with agent-oriented/llms.txt-style documentation that an AI agent could be pointed at directly. However, there's no explicit llms.txt file cited, no first-party statement framing these docs as agent-consumption-optimized, and no independent evidence of an agent successfully using them this way. Missing for 10: explicit llms.txt manifest, documentation of agent-readability intent, third-party confirmation of successful agent consumption.

   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
   • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
   • [claimed-docs] “The agent must signal its identity clearly so that it can never be mistaken for a person.”

   proof ↗⚑ flag

   monday.com~partialprobed6/10

   monday.com has extensive agent-oriented developer documentation (MCP server docs, agent APIs, webhooks, scopes) confirmed by both docs and a probe verifying the MCP docs page exists, but a direct probe shows no llms.txt file is served (404), so the specific 'point an agent at llms.txt' capability is absent even though broader agent-oriented docs exist. missing for 10: a working llms.txt endpoint, independent confirmation that agent-oriented docs are consumable/structured for LLM ingestion.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developer.monday.com/llms.txt”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”
   • [claimed-docs] “Use our native integration, or manually connect with our hosted MCP url. Each agent gets its own identity on monday.”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Linear
   Linear✓fullclaimed7/10

   Linear exposes a full GraphQL API with API-key and OAuth2 authentication, a typed SDK, webhooks for event-driven automation, and documented rate limits/deprecation policy — all of which allow scripting issue creation, queries, and workflow automation entirely headlessly (e.g. from CI pipelines) without the UI. Missing for 10: no dedicated CLI tool or explicit CI/GitHub Actions integration guide, and no independent hands-on report of using the API in a CI pipeline.

   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
   • [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
   • [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
   • [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
   • [claimed-docs] “const myIssues = await me.assignedIssues();”

   proof ↗⚑ flag

   monday.com~partialclaimed6/10

   monday.com exposes a GraphQL API, SDKs, webhooks, and lets you 'run and manage every monday agent programmatically from your own code, anywhere you need it' (monday-docs-9, monday-docs-35, monday-docs-28), which supports scripted/headless automation. However there is no explicit documentation of CI/CD integration, headless test runners, or pipeline examples, and no independent verification that these APIs work reliably in automated pipelines. Missing for 10: explicit CI/CD documentation or examples, independent/hands-on confirmation of headless operation, and any mention of exit codes/scriptable non-interactive workflows.

   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”
   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Deploy to isolated sandboxes monday manages. Your syncs and tools run on our infra, not yours.”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Linear—none0/10

   All MCP-related evidence (linear-probe-1, linear-docs-67, linear-intdir-4, linear-intdir-6) describes Linear exposing its OWN MCP server so that other tools (Cursor, Claude) can connect TO Linear — the opposite direction from the story, which asks whether a user can plug external MCP servers INTO Linear so Linear's agent can use their tools. No evidence shows Linear or Linear Agent consuming/importing third-party MCP servers as a client.

   • [probe] “official MCP server documented at https://linear.app/docs/mcp”
   • [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”
   • [claimed-docs] “Connect Cursor to the Linear MCP server”
   • [claimed-docs] “Connect Claude to the Linear MCP server”

   proof ↗⚑ flag

   monday.com—none0/10

   The evidence shows monday.com exposing its own hosted/developer MCP server so external agents (Claude, ChatGPT, etc.) can connect to monday, and monday's agents can be reached via multiple channels including 'our MCP' — this is monday acting as an MCP server/provider, not monday consuming third-party MCP servers to extend its own agents' toolset. There is no documentation of monday's agents importing or plugging in external MCP servers as tool sources.

   • [claimed-docs] “Use our native integration, or manually connect with our hosted MCP url. Each agent gets its own identity on monday.”
   • [claimed-docs] “Connect agents from Claude, ChatGPT, Make, or any provider through a managed connection or a simple webhook — or build code-first with the a…”
   • [claimed-docs] “Bring an agent in once and reach it from Slack, WhatsApp, Telegram, Make, our MCP, or the API. One identity, every surface — no rebuilding p…”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to monday.com
   Linear✓fullprobed7/10

   Linear publishes an official MCP server (docs page at linear.app/docs/mcp) and the changelog confirms ongoing feature work on it (e.g., Okta-based access management via Linear's MCP), showing agents can connect through this official channel. Missing for 10: independent/hands-on verification of the MCP server in use and detailed docs on setup/tool coverage beyond the single probe reference.

   • [probe] “official MCP server documented at https://linear.app/docs/mcp”
   • [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”

   proof ↗⚑ flag

   monday.com✓fullprobed8/10

   Monday.com documents an official hosted MCP server with a dedicated docs page (confirmed by probe) plus first-party guidance on connecting agents from Claude, ChatGPT, etc. via this MCP endpoint, granular scopes, and managed secrets. Missing for 10: independent/hands-on third-party verification that the MCP server works as documented in practice.

   • [claimed-docs] “Use our native integration, or manually connect with our hosted MCP url. Each agent gets its own identity on monday.”
   • [claimed-docs] “Connect agents from Claude, ChatGPT, Make, or any provider through a managed connection or a simple webhook — or build code-first with the a…”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”
   • [claimed-docs] “Work with tools like Claude, Copilot, and ChatGPT through official integrations or the monday MCP, and keep data secure with trusted AI conn…”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Linear—none0/10

   The evidence pack documents Linear's GraphQL API, TypeScript SDK, webhooks, OAuth, and MCP server, but nowhere mentions an official command-line interface (CLI) tool for interacting with Linear. Since CLI is a plausible and common tool for developer-facing products, its absence here is a gap rather than an inapplicable axis.

   ⚑ flag

   monday.com—none0/10

   The evidence pack covers monday's APIs, SDKs, MCP servers, and apps framework, but nowhere mentions an official CLI tool for developers or AI-native workflows. Since a platform of this kind could plausibly offer a CLI, absence of evidence means the axis is unmet rather than inapplicable.

   ⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Linear✓fullclaimed9/10

   Linear ships a well-documented public GraphQL API with introspection, an explorable schema via Apollo Studio, OAuth2/API-key auth, TypeScript SDK, webhooks, rate-limit documentation, and a deprecation policy, giving AI-native users a robust way to programmatically drive the product. missing for 10: independent hands-on developer reports validating real-world API usage/reliability beyond Linear's own docs.

   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
   • [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
   • [claimed-docs] “query Issue { issue(id: "BLA-123") { id title description } }”
   • [claimed-docs] “const myIssues = await me.assignedIssues();”
   • [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
   • [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
   • [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
   • [claimed-docs] “Docs, "Deprecations": "Linear's GraphQL API doesn't have versioning like many REST APIs... we take breaking changes and deprecations serious…”

   proof ↗⚑ flag

   monday.com✓fullprobed9/10

   monday.com documents a full GraphQL API (monday-docs-35), SDKs (monday-docs-28), granular OAuth scopes and secret storage (monday-docs-6), webhooks/event subscriptions (monday-docs-7, monday-docs-27), and an official MCP server (monday-probe-2) alongside apps framework docs — giving AI-native users multiple documented, programmatic ways to drive the product. Missing for 10: no independent/hands-on developer corroboration of API robustness or reliability beyond first-party docs.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Request granular scopes like `boards:read`. Store keys in managed secret storage.”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to monday.com
   Linear~partialclaimed6/10

   Linear documents OAuth2 apps with distinct scopes (e.g. app:assignable, app:mentionable) for building agents, admin approval workflows for third-party apps, and per-key rate limits differentiated by auth type, which together enable a degree of least-privilege credentialing for agent integrations. However, personal API keys (the simpler credential path) are not shown to be scope-limited, and there's no first-party or independent evidence of fine-grained per-resource/action scoping akin to full least-privilege IAM. Missing for 10: documentation of scoped personal API keys, granular resource-level permission control beyond the small named scope list, and independent/hands-on verification of least-privilege enforcement.

   • [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
   • [claimed-docs] “app:assignable | Allow the app to be assigned as a delegate on issues and made a member of projects app:mentionable | Allow the app to be me…”
   • [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
   • [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”
   • [claimed-docs] “Use URL parameters to send users directly to a pre-filled Create OAuth App form in Linear. An equivalent JSON manifest format lets you store…”
   • [claimed-docs] “Admins can manage access centrally, without requiring employees to sign in or authorize Linear individually.”
   • [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”

   proof ↗⚑ flag

   monday.com✓fullclaimed7/10

   Docs explicitly describe requesting granular scopes (e.g. boards:read), storing keys in managed secret storage, admin-level scoping of each agent's board access, and audit logging of every action — directly matching scoped/least-privilege credential issuance for agents. Missing for 10: no independent/hands-on verification of scope granularity or credential rotation, and no detail on token expiry/revocation workflows.

   • [claimed-docs] “Request granular scopes like `boards:read`. Store keys in managed secret storage.”
   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”
   • [claimed-docs] “Get hosting, storage, secrets, and scaling on infra certified for SOC 2, HIPAA, and ISO 27001. Your data never leaves our secure servers.”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear publishes an official TypeScript SDK exposing its GraphQL schema with strongly typed models (linear-docs-53, linear-docs-89, linear-docs-93), backed by full GraphQL API docs, introspection, published schema SDL, OAuth2/API key auth, rate limits, and deprecation policy (linear-supp-graphql-introspection, linear-supp-apollo-explorer, linear-supp-rate-limits, linear-supp-deprecations, linear-docs-99, linear-docs-50). This gives AI-native developers a solid, well-documented official SDK to build against. Missing for 10: independent/hands-on developer corroboration (e.g., GitHub stars, community usage reports) of the SDK itself beyond official docs, and SDKs in languages beyond TypeScript.

   • [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
   • [claimed-docs] “Install the Linear SDK to use strongly typed models and operations”
   • [claimed-docs] “const myIssues = await me.assignedIssues();”
   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
   • [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
   • [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
   • [claimed-docs] “Docs, "Deprecations": "Linear's GraphQL API doesn't have versioning like many REST APIs... we take breaking changes and deprecations serious…”
   • [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
   • [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”

   proof ↗⚑ flag

   monday.com✓fullprobed7/10

   Monday documents official SDKs/tooling for AI-native builders: a GraphQL API, an 'apps framework' for code-first development, an open-source React component library (Vibe) for native-looking UI, and a documented developer MCP server for scaffolding/deploying agents. Together these constitute a real official SDK/toolchain for building AI-native apps and agents on the platform. Missing for 10: independent/hands-on developer corroboration of SDK quality or adoption, and llms.txt returns 404 suggesting incomplete AI-facing doc tooling.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Connect agents from Claude, ChatGPT, Make, or any provider through a managed connection or a simple webhook — or build code-first with the a…”
   • [claimed-docs] “Build with Vibe, monday's open-source React components, and look native instantly.”
   • [claimed-docs] “Match monday with Vibe, our open-source React components, so your app looks native from day one.”
   • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”
   • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developer.monday.com/llms.txt”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Linear
   Linear✓fullclaimed9/10

   Linear provides documented webhooks with a webhookCreate mutation to subscribe to HTTP push notifications for data create/update/delete events, plus in-app event subscriptions for project views routed to Inbox/Slack, giving AI-native users clear ways to consume event streams programmatically. Missing for 10: independent/hands-on corroboration of webhook reliability or payload completeness beyond first-party docs.

   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
   • [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”

   proof ↗⚑ flag

   monday.com✓fullclaimed8/10

   Docs explicitly describe webhook subscriptions to real-time board events (create_item, change_column_value, etc.) plus agent-triggering webhooks, backed by a GraphQL API for integration. Missing for 10: independent/hands-on verification of webhook reliability and payload details beyond vendor docs.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”

   proof ↗⚑ flag

10. ai-native userHand off work between tools or agents without losing context or information

    weight 1 · round to Linear
    Linear✓fullclaimed7/10

    Linear documents extensive hand-off machinery for agentic work: issues can be delegated (not assigned) to AI agents while humans retain ownership, agents behave like workspace members (mentions, comments, docs) so context stays attached to the issue, and MCP/integration connectors (GitHub, Copilot, Codex, Claude, Cursor, Slack) let work flow between tools while Linear remains the shared context hub. Features like 'Write with Agent' (pulls prior updates plus Slack context), checkpoints/version history, guided reviews with before/after screenshots, and Loops updating linked docs/Slack on changes all reinforce continuity across handoffs. missing for 10: independent/hands-on verification that context genuinely survives cross-tool handoffs (all evidence is first-party docs), and no explicit benchmark/comparison of information loss vs other tools

    • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
    • [claimed-docs] “Assigning an issue to your app now sets it as the delegate, not the assignee—so humans maintain ownership while agents act on their behalf.”
    • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
    • [claimed-docs] “Once connected to Linear, teammates can delegate issues to your agent or mention it in comments.”
    • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
    • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
    • [claimed-docs] “If you need to revert to an earlier version, restore to any previous checkpoint from version history.”
    • [claimed-docs] “Linear Agent can now set up, run, and test your code before returning its work.”
    • [claimed-docs] “The agent opens the app, navigates through a flow, and verifies its implementation. It also captures before-and-after screenshots”
    • [claimed-docs] “Linear Agent can now write code using Claude Code and Codex.”
    • [claimed-docs] “Connect Cursor to the Linear MCP server”
    • [claimed-docs] “Connect Claude to the Linear MCP server”
    • [claimed-docs] “Connect GitHub to automate PR workflows, review code in Linear, sync issues and understand your codebase with Linear Agent”
    • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
    • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
    • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”

    proof ↗⚑ flag

    monday.com~partialprobed7/10

    monday.com documents one persistent agent identity reachable across Slack, WhatsApp, Telegram, Make, MCP, and API 'no rebuilding per channel' (monday-docs-12), plus 2-way sync, webhooks, a unified Models API, and an official MCP server (monday-docs-1, monday-docs-2, monday-docs-17, monday-docs-31, monday-probe-2) that together support handing off work/context between tools and agents. Missing for 10: independent/hands-on verification that context is actually preserved across handoffs (all evidence is vendor docs), and no case study showing a real multi-tool handoff working end-to-end.

    • [claimed-docs] “Bring an agent in once and reach it from Slack, WhatsApp, Telegram, Make, our MCP, or the API. One identity, every surface — no rebuilding p…”
    • [claimed-docs] “Use our native integration, or manually connect with our hosted MCP url. Each agent gets its own identity on monday.”
    • [claimed-docs] “Connect agents from Claude, ChatGPT, Make, or any provider through a managed connection or a simple webhook — or build code-first with the a…”
    • [claimed-docs] “Connect the developer MCP to any agent. Scaffold, set env vars, and promote versions from chat.”
    • [claimed-docs] “Enable 2-way sync between monday products and any platform you work with to trigger automations, eliminate manual work, and keep your busine…”
    • [probe] “official MCP server documented at https://developer.monday.com/apps/docs/mcp-servers”
    • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”

    proof ↗⚑ flag

Agentic features

1. engineerRestore an AI coding agent's session to any previous checkpoint in its version history

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear explicitly documents checkpoint-based version history restore for coding sessions: "If you need to revert to an earlier version, restore to any previous checkpoint from version history" — this directly matches the story of restoring an AI agent's session state. It's first-party documentation only, with no independent/hands-on corroboration of the restore behavior in practice. Missing for 10: independent/hands-on verification of restore reliability, and detail on granularity/scope of what gets restored.

   • [claimed-docs] “If you need to revert to an earlier version, restore to any previous checkpoint from version history.”
   • [claimed-docs] “Linear Agent can now set up, run, and test your code before returning its work.”
   • [claimed-docs] “Coding sessions run in the cloud, so you can prototype ideas and make changes without setting up a local development environment.”

   proof ↗⚑ flag

   monday.com—none0/10

   No evidence of any session/checkpoint versioning or restore capability for monday's AI agents; docs cover connectivity, scopes, sandboxing, and audit logging but never mention rollback or history checkpoints.

   ⚑ flag

2. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Linear~partialclaimed6/10

   Linear ships AI-agent features (Write with Agent for project updates, Loops for automated doc/plan updates, auto-triage/routing of feedback into issues, Linear Agent investigating issues) that surface generated content and suggestions inside the product, per linear-docs-19, linear-docs-38, linear-docs-45, linear-docs-62, linear-docs-95-97. However, these are framed as agentic task-execution/automation rather than analytic 'insights' (e.g., trend analysis, prioritization recommendations, summarization dashboards), and there's no independent/hands-on evidence validating quality of these AI outputs. missing for 10: dedicated insight/analytics generation (e.g., pattern detection across issues, predictive suggestions, summarized health reports) and third-party corroboration of suggestion quality.

   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
   • [claimed-docs] “When a new issue is reported, Linear Agent can investigate and attempt a fix before it reaches an engineer, reducing the load on your team.”
   • [claimed-docs] “Automatically turn conversations and customer feedback into actionable issues that are instantly routed, labeled, and prioritized for the ri…”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”

   proof ↗⚑ flag

   monday.com~partialclaimed6/10

   Docs claim AI agents can surface deep intelligence, actionable insights, risk/progress gap detection, and automated reports/summaries directly in monday (docs-20, docs-21, docs-22, docs-23, docs-32), which matches the story of in-product AI-generated insights. However, evidence is entirely vendor marketing copy with no independent/hands-on validation of insight quality or accuracy, and community feedback focuses on performance/UX issues rather than AI insight capability. Missing for 10: independent verification of insight quality, concrete examples/screenshots of generated insights, and hands-on user reports confirming the feature works as described.

   • [claimed-docs] “Surface deep intelligence and actionable insights from any subject.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Spot risks and progress gaps before they become problems.”
   • [claimed-docs] “Schedule meetings, summarize calls, and extract action items.”
   • [claimed-docs] “Score our open deals and send proposals to anyone above 80%.”

   proof ↗⚑ flag

3. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Linear✓fullclaimed8/10

   Linear's "Loops" feature explicitly lets users describe a job in plain language and set it to run on a schedule or in response to events, enabling autonomous background automations (e.g., updating docs, posting Slack updates, monitoring initiatives) without manual triggering. This is well documented across multiple changelog entries describing scheduling, event triggers, and recurring workflows. Missing for 10: independent/hands-on verification of reliability at scale and no third-party community confirmation of autonomous background execution in practice.

   • [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
   • [claimed-docs] “You can now add a loop to Favorites”

   proof ↗⚑ flag

   monday.com✓fullclaimed8/10

   monday.com documents native automations (event triggers like create_item/change_column_value, real-time listeners), plus AI agents that run in isolated sandboxes managed by monday, scoped with permissions, audited, and triggered autonomously by mentions/assignments or scheduled reports (status updates on a set schedule). This directly supports background/autonomous automation setup. Missing for 10: independent/hands-on verification of autonomous background execution reliability and no community corroboration of agent-based automations specifically (community evidence is generic negative sentiment unrelated to this feature).

   • [claimed-docs] “Deploy to isolated sandboxes monday manages. Your syncs and tools run on our infra, not yours.”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”
   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “You lead. Agents act.”

   proof ↗⚑ flag

4. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Linear✓fullclaimed8/10

   Linear ships a built-in 'Linear Agent' that users can delegate issues to directly (assign/mention), which writes code via Claude Code/Codex, edits text, runs Loops for recurring work, drafts project updates, and shows delegated work status in My Issues, all documented extensively in first-party changelog docs. missing for 10: independent/hands-on verification beyond vendor changelog, and clearer detail on reliability/limits of the built-in assistant in real-world use.

   • [claimed-docs] “Linear Agent can now write code using Claude Code and Codex.”
   • [claimed-docs] “Linear Agent can now set up, run, and test your code before returning its work.”
   • [claimed-docs] “We’ve also added section under My Issues → Assigned for your delegated issues. It shows the status of each coding session, and gives you a q…”
   • [claimed-docs] “Once connected to Linear, teammates can delegate issues to your agent or mention it in comments.”
   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “You can now edit text with Linear Agent, and use Loops to keep docs and project descriptions up-to-date.”
   • [claimed-docs] “When a new issue is reported, Linear Agent can investigate and attempt a fix before it reaches an engineer, reducing the load on your team.”
   • [claimed-docs] “@Linear can you take a stab at this?”

   proof ↗⚑ flag

   monday.com✓fullclaimed8/10

   monday.com offers built-in AI agents that can be messaged, assigned items, and @mentioned to perform real work directly within the product ('Talk to agents like teammates... assign them items'), with docs describing creating custom agents via natural language and managing them from an admin dashboard. Community evidence is generic product criticism unrelated to the AI assistant feature, so it doesn't dispute this capability. Missing for 10: independent hands-on verification of agent quality/reliability and no third-party review of the assistant feature specifically.

   • [claimed-docs] “Talk to agents like teammates. Message them in updates, assign them items, and @mention them in any conversation to kick off real work — rep…”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [claimed-docs] “Describe any workflow in your own words to create a unique agent in minutes.”
   • [claimed-docs] “Message them in updates, assign them items, and @mention them in any conversation to kick off real work — replies, statuses, and follow-ups …”
   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”
   • [claimed-docs] “You lead. Agents act.”

   proof ↗⚑ flag

5. ai-native userOperate the product with natural-language commands

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear supports natural-language interaction extensively: users can @mention Linear Agent, describe jobs in plain language for Loops, use 'Write with Agent' to draft updates, and delegate issues via comments in natural language (linear-docs-11, -19, -36, -41, -68). This is well documented across multiple first-party changelog entries and the agents.md docs, but missing for 10: independent/hands-on evidence of natural-language command accuracy or limitations, and no dedicated NL command palette/chat interface separate from agent-delegation workflows.

   • [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
   • [claimed-docs] “Once connected to Linear, teammates can delegate issues to your agent or mention it in comments.”
   • [claimed-docs] “@Linear can you take a stab at this?”
   • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
   • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”

   proof ↗⚑ flag

   monday.com✓fullclaimed7/10

   monday.com documents natural-language operation extensively: users can message, assign, and @mention agents in plain language to kick off real work, and can describe entire workflows in their own words to create agents. This directly matches the story of operating the product via natural-language commands. Missing for 10: independent/hands-on verification that NL commands reliably produce correct actions, and more detail on limits of NL understanding beyond marketing copy.

   • [claimed-docs] “Talk to agents like teammates. Message them in updates, assign them items, and @mention them in any conversation to kick off real work — rep…”
   • [claimed-docs] “Describe any workflow in your own words to create a unique agent in minutes.”
   • [claimed-docs] “Message them in updates, assign them items, and @mention them in any conversation to kick off real work — replies, statuses, and follow-ups …”
   • [claimed-docs] “You lead. Agents act.”

   proof ↗⚑ flag

6. ai-native userBuild and configure my own custom AI agent within the product

   weight 2 · round to monday.com
   Linear~partialclaimed6/10

   Linear offers in-product mechanisms for creating custom agent-like automation: Loops let users 'describe the job in plain language' and set it to run on a schedule or event (linear-docs-36/95-100), and Skills let teams codify and share recurring agent workflows (linear-docs-23/46). Linear also documents a developer-facing Agents API for building agents that behave like workspace members (assignable, mentionable, can comment) (linear-docs-16, linear-docs-54/64/75/90/94). This is meaningful but falls short of a full custom-agent builder with model/tool selection or a dedicated no-code agent studio. Missing for 10: no evidence of choosing/configuring underlying models or custom toolsets, no dedicated 'agent builder' UI beyond Loops/Skills, and no independent hands-on confirmation of ease-of-use.

   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
   • [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”
   • [claimed-docs] “We now support sharing skills with your team so great personal workflows can become shared team process.”
   • [claimed-docs] “Build agents that can investigate incidents, monitor SLAs, or analyze customer feedback.”
   • [claimed-docs] “How to best integrate an AI agent into Linear”
   • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
   • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
   • [claimed-docs] “app:assignable | Allow the app to be assigned as a delegate on issues and made a member of projects app:mentionable | Allow the app to be me…”

   proof ↗⚑ flag

   monday.com✓fullclaimed7/10

   monday's docs describe a dedicated agent-building capability: defining goals/rules in natural language, describing workflows to create custom agents, scoping board access, hosting/sandboxing, granular permissions, and monitoring via an admin dashboard (monday-docs-13, 14, 10, 5, 6, 9). This directly matches the story of building/configuring a custom AI agent within the product. Missing for 10: independent or hands-on verification that the agent builder works as described in practice, and detail on customization limits/complexity for non-technical users.

   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [claimed-docs] “Describe any workflow in your own words to create a unique agent in minutes.”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”
   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”
   • [claimed-docs] “Deploy to isolated sandboxes monday manages. Your syncs and tools run on our infra, not yours.”
   • [claimed-docs] “Request granular scopes like `boards:read`. Store keys in managed secret storage.”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Linear
   Linear~partialclaimed6/10

   Linear's GraphQL API supports introspection and is explorable/queryable via Apollo Studio Explorer with no login required, effectively an interactive reference with runnable queries, plus published docs with sample queries/mutations and an SDK. However, this is a third-party hosted explorer rather than a first-party embedded interactive API reference, and there's no evidence of runnable examples directly within Linear's own developer docs site. missing for 10: first-party embedded interactive API console with runnable examples on developers.linear.app itself, independent/hands-on confirmation of the Apollo Explorer experience, broader runnable example coverage beyond basic query/mutation snippets.

   • [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
   • [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
   • [claimed-docs] “query Issue { issue(id: "BLA-123") { id title description } }”
   • [claimed-docs] “const myIssues = await me.assignedIssues();”
   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “Learn how to use the GraphQL API to query and mutate your data”

   proof ↗⚑ flag

   monday.com—none0/10

   The evidence shows monday has a GraphQL API and developer docs, but there is no mention of an interactive API reference, playground, or runnable code examples anywhere in the pack.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developer.monday.com/llms.txt”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to monday.com
   Linear~partialclaimed6/10

   Linear's API is GraphQL, not OpenAPI/REST, but it explicitly supports schema introspection and publishes a full schema SDL file in the linear/linear GitHub repo, plus an explorable schema via Apollo Studio — giving AI-native users machine-readable access to the API's shape without needing a human-written spec. This satisfies the intent of a downloadable machine-readable spec via GraphQL introspection/SDL rather than OpenAPI itself. missing for 10: no explicit OpenAPI/Swagger document, no single-click 'download spec' artifact, and no independent/community confirmation of using the introspection or SDL file in practice.

   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
   • [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “Linear's public API is built using GraphQL.”

   proof ↗⚑ flag

   monday.com✓fullclaimed7/10

   monday documents an expressive GraphQL API for developers with public developer docs, which serves as a machine-readable/documented spec analog for programmatic access, though it's GraphQL rather than a formal OpenAPI/REST spec download. missing for 10: an explicit downloadable OpenAPI/Swagger file or schema export, and independent confirmation of spec completeness.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Linear
   Linear~partialclaimed5/10

   Linear's own docs explicitly state its GraphQL API 'doesn't have versioning like many REST APIs,' but they do document a deprecation policy: use of the @deprecated schema directive, proactive outreach for breaking changes, and changelog entries tagged [API]. This satisfies the 'documented deprecation policy' half of the story but directly contradicts the 'versioned APIs' half. Missing for 10: an actual versioning scheme (e.g., v1/v2 endpoints or dated API versions), and independent/community corroboration that deprecation notices are reliably honored in practice.

   • [claimed-docs] “Docs, "Deprecations": "Linear's GraphQL API doesn't have versioning like many REST APIs... we take breaking changes and deprecations serious…”
   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”

   proof ↗⚑ flag

   monday.com—none0/10

   The evidence pack describes monday's GraphQL API, apps framework, and MCP integrations but contains no mention of API versioning scheme or a documented deprecation policy for its APIs. Missing for 10: explicit versioning scheme documentation, deprecation policy/timeline, changelog or migration guides.

   ⚑ flag

4. ai-native userThe documented API rate limits and concurrency caps before building automation at scale

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear's developer docs explicitly publish per-auth-type rate limits (API key, OAuth, unauthenticated), leaky-bucket refill behavior, complexity limits, and rate-limit response headers, giving AI-native builders concrete numbers to design automation around. Missing for 10: explicit documented concurrency caps (max simultaneous requests/connections) beyond hourly request quotas, and no independent/hands-on confirmation that these limits hold in practice at scale.

   • [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”

   proof ↗⚑ flag

   monday.com—none0/10

   No evidence pack item documents specific API rate limits, request quotas, or concurrency caps for monday's GraphQL API, MCP server, or agent platform; docs mention general scopes and secret storage but never numeric or documented limits.

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Linear
   Linear~partialclaimed4/10

   Linear's GraphQL API, SDK, and webhook system (linear-docs-49,53,51) provide the technical means to script bulk changes across issues, and there's a documented bulk import capability (linear-docs-47). However, there is no explicit documentation of a dedicated bulk-edit UI, batch mutation endpoints, or AI-agent-driven bulk operation workflow across many items at once. missing for 10: explicit bulk-edit/multi-select UI docs, batch/bulk GraphQL mutations, and any agent or automation example operating on multiple items simultaneously.

   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “Import data from other services into Linear”
   • [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”

   proof ↗⚑ flag

   monday.com!disputedcontradicted4/10

   monday's GraphQL API, webhooks, and automation triggers (create_item, change_column_value) suggest programmatic bulk item manipulation is possible, but there's no explicit documentation of a batch/bulk operations endpoint, and independent hands-on reports describe the platform struggling and crashing once boards exceed a few thousand items (up to ~20k before failure), directly undercutting claims of smooth operation 'across many items at once'. Missing for 10: explicit bulk/batch API documentation, evidence of large-scale (10k+) item operations succeeding, and any first-party rebuttal to the scaling complaints.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [community] “Until a while ago, when a user landed on their board, we threw all the board data right into the client... it started to struggle and finall…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Linear
   Linear✓fullclaimed8/10

   Linear's 'Loops' feature explicitly lets users describe a job in plain language and choose to run it on a schedule or in response to an event (e.g., initiative/project/cycle changes), with concrete examples like auto-updating docs or posting Slack messages when a target date changes. This is reinforced by webhook support for event-driven automation via the API. Missing for 10: independent/hands-on corroboration beyond vendor docs, and detail on the breadth of definable trigger conditions/rules.

   • [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”

   proof ↗⚑ flag

   monday.com✓fullclaimed7/10

   monday.com's automation engine and agent framework support event-based triggers (create_item, change_column_value, real-time events, agent mentions/assignments) that fire automated actions, well documented across native automations and the developer platform. missing for 10: independent/hands-on verification of rule complexity and reliability at scale, and clearer detail on conditional logic depth beyond simple trigger-action pairs.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Enable 2-way sync between monday products and any platform you work with to trigger automations, eliminate manual work, and keep your busine…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear's 'Loops' feature is explicitly designed for recurring agent workflows: users describe a job and choose to run it 'on a schedule or in response to an event,' with examples like auto-updating launch plans and posting Slack updates when project dates change. Docs also show loops can be shared as team-wide skills and pinned/favorited for ongoing use, covering both scheduling and workflow automation depth. Missing for 10: independent/hands-on confirmation that scheduled loops reliably trigger as configured, and technical detail on scheduling granularity or failure handling.

   • [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
   • [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”
   • [claimed-docs] “We now support sharing skills with your team so great personal workflows can become shared team process.”
   • [claimed-docs] “You can now add a loop to Favorites”

   proof ↗⚑ flag

   monday.com~partialclaimed5/10

   monday's docs mention scheduled automation only in the narrow context of status updates and performance reports ('Automate status updates and performance reports on a set schedule'), which supports recurring job scheduling but doesn't document a general-purpose recurring workflow/job scheduler for arbitrary AI-native automations. Missing for 10: explicit cron-like scheduling API/UI for arbitrary workflows, examples of recurring agent tasks beyond reporting, and independent confirmation of reliability at scale.

   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Linear
   Linear~partialclaimed4/10

   Linear offers general version history/checkpoint restore for work (linear-docs-35) and rich review tooling for agent-produced code changes (guided reviews, diff rendering — linear-docs-7, linear-docs-72), which partially satisfies the 'version, review, rollback' need for AI-generated work. However there is no evidence of version control, review, or rollback specifically for the automations/Loops themselves (the scheduled/event-driven workflows) — only their outputs (documents, code) get versioned. Missing for 10: explicit versioning of Loop/automation definitions, audit trail of automation changes, and a dedicated rollback mechanism for the automation logic itself rather than just its output artifacts.

   • [claimed-docs] “If you need to revert to an earlier version, restore to any previous checkpoint from version history.”
   • [claimed-docs] “Guided Reviews break diffs into focused sections with explainers on what changed and why.”
   • [claimed-docs] “Images, fonts, Markdown, and PDFs now render directly inside Linear diffs.”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”

   proof ↗⚑ flag

   monday.com—none0/10

   Evidence covers agent building, deployment, MCP connectivity, and app scaffolding (with 'promote versions from chat' hinting at some deployment lifecycle), but there is no mention of automation version history, review workflows, diffing, or rollback of automations. No documented capability to revert an automation to a prior version.

   ⚑ flag

Ai task automation

1. ai-native userHave AI automatically triage and prioritize incoming bugs and tasks

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear docs explicitly describe AI-driven triage: incoming feedback/issues are 'instantly routed, labeled, and prioritized for the right team,' and Linear Agent can 'investigate and attempt a fix before it reaches an engineer,' plus a Priority tab surfaces what needs attention. These directly match the automatic triage/prioritization story. Missing for 10: independent/hands-on evidence validating triage accuracy or reliability beyond vendor changelog claims.

   • [claimed-docs] “Automatically turn conversations and customer feedback into actionable issues that are instantly routed, labeled, and prioritized for the ri…”
   • [claimed-docs] “When a new issue is reported, Linear Agent can investigate and attempt a fix before it reaches an engineer, reducing the load on your team.”
   • [claimed-docs] “The new Priority tab separates what needs your attention from what can wait, so something like a review blocking a release never gets buried…”

   proof ↗⚑ flag

   monday.com~partialclaimed5/10

   monday.com documents AI agents that can be assigned items, triggered on item creation/column changes, and used to "spot risks and progress gaps" or manage support tickets via Zendesk integration, which supports building an automated triage-like workflow, but there is no explicit documentation of an out-of-the-box 'triage and prioritize bugs' capability or example. missing for 10: a concrete bug/task triage workflow example, explicit prioritization logic, and independent/hands-on evidence that this works in practice.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Talk to agents like teammates. Message them in updates, assign them items, and @mention them in any conversation to kick off real work — rep…”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Spot risks and progress gaps before they become problems.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “Connect Zendesk or Active Directory to manage your support tickets in monday.com, helping teams resolve issues faster and keep customers hap…”

   proof ↗⚑ flag

2. ai-native userHave my in-app AI assistant learn my tone, shorthand, and preferences to tailor its output

   weight 1 · round drawn
   Linear—none0/10

   Evidence shows Linear Agent can draft updates, edit text, and run automated 'Loops', but nothing describes it learning an individual user's tone, shorthand, or personal preferences to tailor future outputs — personalization/memory of style is never mentioned.

   ⚑ flag

   monday.com—none0/10

   The evidence describes monday's AI agents/automation framework (agent creation, MCP, integrations, admin scoping) but nothing about the assistant learning a user's tone, shorthand, or writing preferences to tailor output. Missing for 10: any mention of personalization/memory of user style, adaptive tone learning, or preference-based output customization.

   ⚑ flag

Workflow automation

1. product managerBuild multi-step automations without writing code

   weight 2 · round to Linear
   Linear✓fullclaimed7/10

   Linear's 'Loops' feature lets users describe a recurring job in plain language and choose a schedule or event trigger, with multi-step behavior like updating documents and posting Slack messages when conditions change—exactly a no-code automation builder usable by a PM. Additional context (skills, agent-based investigation/monitoring) reinforces no-code configurability. missing for 10: independent/hands-on evidence of a PM successfully building complex branching automations, and detail on conditional/branching logic depth

   • [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
   • [claimed-docs] “Build agents that can investigate incidents, monitor SLAs, or analyze customer feedback.”
   • [claimed-docs] “We now support sharing skills with your team so great personal workflows can become shared team process.”
   • [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”

   proof ↗⚑ flag

   monday.com~partialcommunity6/10

   monday.com's docs describe automation recipes (triggers like create_item/change_column_value, scheduled reports, agent assignment flows) that let a PM configure multi-step automations without code, and its no-code automation builder is a well-known core feature referenced via triggers/subscriptions. However, the evidence pack is heavily focused on the newer AI-agent/developer platform rather than the classic drag-and-drop automation board builder itself, and community feedback raises usability/reliability concerns that could affect building complex automations at scale. missing for 10: direct documentation of the classic visual automation recipe builder UI, independent hands-on validation of multi-step automation reliability, and confirmation that no coding is required for complex branching logic.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Build agents for your exact needs. Define the goal, set the rules, watch the results.”
   • [community] “Until a while ago, when a user landed on their board, we threw all the board data right into the client... it started to struggle and finall…”

   proof ↗⚑ flag

2. engineerBuild trigger-and-action automation rules to eliminate repetitive manual steps

   weight 3 · round to Linear
   Linear✓fullclaimed8/10

   Linear's 'Loops' feature explicitly lets users describe a job in plain language and choose to run it on a schedule or in response to an event, automating recurring work like updating docs, posting Slack messages, or monitoring initiatives — a direct trigger-and-action automation capability, further extensible via webhooks and the GraphQL API for custom automations. missing for 10: independent/hands-on verification of Loops reliability at scale, and more detail on the breadth of available trigger/action types beyond the examples shown.

   • [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”

   proof ↗⚑ flag

   monday.com~partialclaimed5/10

   Evidence shows trigger/event subscriptions (create_item, change_column_value) and scheduled automations for status updates/reports, which map to trigger-and-action rules, but the pack lacks documentation of monday's classic no-code Automations recipe builder (e.g., cross-board triggers, conditional actions, integration recipes) that engineers would typically use. Missing for 10: dedicated automation-builder documentation, examples of multi-step conditional recipes, and independent/hands-on validation that these rules reliably eliminate manual steps.

   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”

   proof ↗⚑ flag

3. engineerCreate a workflow that runs on a schedule or recurring event to handle routine team work

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear's 'Loops' feature explicitly lets users describe a job in plain language and choose to run it on a schedule or in response to an event, targeting recurring team work like weekly planning, doc updates, or launch plan syncing (linear-docs-11, linear-docs-36, linear-docs-23, linear-docs-95, linear-docs-96, linear-docs-100). This directly matches the story of scheduled/recurring workflow automation for routine team tasks. missing for 10: independent/hands-on verification of Loops reliability and no detail on error handling or monitoring of scheduled runs.

   • [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”

   proof ↗⚑ flag

   monday.com~partialclaimed6/10

   Docs show scheduled automation for reports/status updates and event-based triggers (webhooks on create_item, change_column_value, agent mentions), which together support building recurring/scheduled workflows for routine work. However, evidence doesn't detail monday's core automation recipe builder, cron-style scheduling controls, or monitoring/error-handling for these workflows. Missing for 10: detailed schedule configuration UI/API, recipe builder specifics, failure/retry handling, and independent confirmation of reliability at scale.

   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Fire when an agent is messaged, assigned an item, or mentioned in an update.”

   proof ↗⚑ flag

4. ai-native userWhat happens—extra charges, throttling, or a hard stop—when I exceed my plan's automation or API call limits

   weight 3 · round to Linear
   Linear~partialclaimed6/10

   Linear's docs publish exact per-auth-type API rate limits, response headers (e.g. X-RateLimit-Requests-Limit) and a leaky-bucket refill model, and separately allow admins to set spend limits for AI agent/automation usage that reset periodically — together these give a user real visibility into automation/API limits. However, the pack doesn't explicitly spell out the concrete consequence of exceeding a limit (e.g. exact 429 throttling behavior, whether overages incur extra charges, or a hard stop for automation/Loops usage), so the full 'what happens when I exceed' picture is only partially documented. Missing for 10: explicit statement of throttling/error response code, confirmation of no/optional overage billing, and documented consequence for exceeding automation (Loops/agent) usage specifically rather than just spend caps.

   • [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
   • [claimed-docs] “Admins can also set workspace-wide and per-user spend limits that reset daily, weekly, or monthly.”

   proof ↗⚑ flag

   monday.com—none0/10

   No evidence pack item discusses plan limits, rate limits, overage charges, throttling behavior, or hard stops for automation/API usage—only feature and integration descriptions are present.

   ⚑ flag

Cross tool sync

1. designerKeep project status updated from my design tool without switching apps

   weight 2 · round drawn
   Linear—none0/10

   The evidence pack shows Linear's API, webhooks, GraphQL SDK, and general integrations (GitHub, Slack, Okta) but contains no mention of a Figma or other design-tool plugin/integration that lets designers update project status without leaving their design tool. Missing for 10: any Figma/design-tool plugin, any documented design-tool-to-Linear status sync, or third-party evidence of such a workflow.

   ⚑ flag

   monday.com—none0/10

   Evidence lists many integrations (Salesforce, GitHub, Slack, Zendesk, communication tools) and a general integrations marketplace, but nothing mentions Figma, Adobe XD, Sketch, or any design-tool-specific integration that would let a designer update project status directly from their design tool.

   • [claimed-docs] “Discover 850+ integrations and apps to centralize work, enhance collaboration, and drive better business results faster.”
   • [claimed-docs] “Easily connect monday.com to thousands of other tools with - no development needed.”
   • [claimed-docs] “Integrate Salesforce, Quickbooks, or HubSpot to manage leads, track opportunities, and keep your sales process proactive and results-driven.”
   • [claimed-docs] “Link pull requests from GitHub or GitLab directly to their related items in monday.com so teams can quickly access code and updates in conte…”
   • [claimed-docs] “Integrate your org’s communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”

   proof ↗⚑ flag

Docs knowledge

1. product managerCreate and organize shared docs and notes alongside my project work

   weight 3 · round to Linear
   Linear~partialclaimed6/10

   Linear supports document creation and organization tied to projects/issues (teams can create documents from home page, add existing documents to projects/issues, group into sections, comment on docs, mobile doc editing) which covers shared docs alongside project work. However, evidence for cross-team/workspace-wide doc organization, folder hierarchies, or dedicated doc search/collaboration features (e.g. co-editing, version history for docs specifically) is thin. missing for 10: evidence of broader doc organization features (folders/wikis beyond project linkage), real-time co-editing, and independent user feedback confirming docs experience.

   • [claimed-docs] “Teams can create documents directly from their home page, add existing documents from projects and issues, and group resources into sections…”
   • [claimed-docs] “Document creation and editing are now available in Linear's iOS and Android apps.”
   • [claimed-docs] “You can now comment directly on text or images in issue descriptions.”
   • [claimed-docs] “Use callout components to draw attention to important information in issue and project descriptions, as well as documents.”

   proof ↗⚑ flag

   monday.com—none0/10

   The evidence pack covers monday's AI agents, integrations, MCP, and developer platform extensively, but contains no mention of a native Docs or notes feature for organizing shared documents alongside project boards. Absence of evidence for this applicable capability yields 'none'.

   ⚑ flag

In context discussion

1. engineerComment directly on specific text or images within an item's description

   weight 2 · round to Linear
   Linear✓fullclaimed9/10

   Linear's own changelog explicitly states the exact capability: 'You can now comment directly on text or images in issue descriptions,' directly matching the story. missing for 10: no independent/hands-on corroboration beyond the vendor changelog entry.

   • [claimed-docs] “You can now comment directly on text or images in issue descriptions.”

   proof ↗⚑ flag

   monday.com—none0/10

   No evidence pack item mentions commenting on specific text or images within an item's description; all documentation focuses on agents, integrations, boards, and infrastructure rather than inline commenting/annotation features.

   ⚑ flag

Real time sync

1. engineerSee teammates' changes reflected instantly across open sessions without refreshing

   weight 3 · round drawn
   Linear—none0/10

   The evidence pack contains no documentation or community reports describing real-time, no-refresh syncing of teammates' changes across open sessions (e.g., live cursors, instant issue updates, presence). References to webhooks (linear-docs-51/52) describe external HTTP push notifications for integrations, not in-app live UI updates, and speed-related comments (linear-comm-6) address load times, not multi-session sync.

   ⚑ flag

   monday.com—none0/10

   The evidence pack contains no documentation or claims about real-time sync of board changes across open sessions; all monday-docs items concern the AI agent/developer platform (MCP, webhooks, agents), not live collaborative UI updates. Community evidence discusses performance/slowness but not specifically real-time refresh behavior, so there's no basis to confirm the capability.

   ⚑ flag

Team chat

1. engineerChat with my team directly inside the same tool I plan work in

   weight 2 · round to monday.com
   Linear~partialclaimed4/10

   Linear supports asynchronous team collaboration via comments on issues, documents, and images (linear-docs-24, linear-docs-22) and @mentions (linear-docs-54), plus Slack integration for notifications (linear-docs-61, linear-docs-81), but there is no evidence of a native real-time chat/messaging feature inside Linear itself — collaboration is comment-based, not conversational chat. missing for 10: a dedicated in-app chat/messaging surface, evidence of synchronous team chat, and any first-party claim positioning Linear as a chat tool rather than relying on comments/Slack.

   • [claimed-docs] “You can now comment directly on text or images in issue descriptions.”
   • [claimed-docs] “Teams can create documents directly from their home page, add existing documents from projects and issues, and group resources into sections…”
   • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
   • [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
   • [claimed-docs] “Create issues from Slack messages and sync threads”

   proof ↗⚑ flag

   monday.com~partialclaimed5/10

   monday.com's 'Updates' feature (message, @mention, assign items 'in any conversation') is documented as a native in-item communication mechanism, and the platform also integrates with Slack/Teams/Gmail for broader team chat, suggesting engineers can converse without leaving the work-planning surface. However, the evidence pack frames this messaging capability almost entirely around AI agents rather than human-to-human team chat, and no first-party or independent source describes robust native person-to-person chat/threads as a core UX pillar. Missing for 10: explicit documentation of human team chat/threads within boards, independent corroboration of real-time chat usability, and evidence it's used as a primary chat tool rather than via external integrations.

   • [claimed-docs] “Talk to agents like teammates. Message them in updates, assign them items, and @mention them in any conversation to kick off real work — rep…”
   • [claimed-docs] “Message them in updates, assign them items, and @mention them in any conversation to kick off real work — replies, statuses, and follow-ups …”
   • [claimed-docs] “Integrate your org’s communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”
   • [claimed-docs] “Integrate your org's communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”

   proof ↗⚑ flag

App ecosystem

1. engineerKeep tasks bi-directionally synced with my code repository's issue tracker instead of duplicating data

   weight 2 · round to Linear
   Linear~partialclaimed5/10

   Linear's changelog references GitHub-synced issues (opening them in GitHub) and syncing review requests/teams with GitHub, plus a public GraphQL API and webhooks that could be used to build two-way sync with an external tracker, but there is no explicit documentation describing full bi-directional field sync (status, description, comments) that eliminates duplicate data entry with a repo issue tracker. Missing for 10: explicit doc/feature description of two-way sync with GitHub Issues (not just PR/review linking), independent/hands-on confirmation that sync avoids duplication, and coverage beyond GitHub (e.g., GitLab).

   • [claimed-docs] “Open a GitHub-synced issue in GitHub with OG”
   • [claimed-docs] “You can now assign reviews to GitHub teams.”
   • [claimed-docs] “You can now assign reviews to GitHub teams. Review requests assigned to your GitHub teams appear in a dedicated section of the Reviews inbox…”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”

   proof ↗⚑ flag

   monday.com—none0/10

   No evidence of a bi-directional sync with GitHub/GitLab/Jira-style issue trackers; docs focus on agents, MCP hosting, and generic integrations but never mention repo issue-tracker sync specifically.

   ⚑ flag

2. engineerSee my assigned tasks from multiple project management tools in one unified view

   weight 2 · round drawn
   Linear—none0/10

   Evidence shows Linear integrates with GitHub, Slack, Okta, and supports one-time data import from other services (linear-docs-47), but there is no evidence of a unified cross-tool task view aggregating assignments from multiple external project management tools (e.g., Jira, Asana) into one dashboard. Linear positions itself as a replacement for such tools rather than an aggregator.

   • [claimed-docs] “Import data from other services into Linear”

   proof ↗⚑ flag

   monday.com—none0/10

   The evidence pack focuses entirely on monday's AI agent framework, MCP hosting, and integration channels for building agents—none of it describes a unified cross-tool task view pulling assigned tasks from multiple external project management tools (e.g., Jira, Asana, Trello) into one dashboard for an engineer. No integration or aggregation feature matching this story is documented.

   ⚑ flag

3. engineerConnect common tools like Slack, GitHub, and Google Drive natively

   weight 2 · round to Linear
   Linear✓fullclaimed9/10

   Linear's integrations directory explicitly documents native Slack (create issues from Slack messages, sync threads, Slack notifications), GitHub (automate PR workflows, review code, sync issues, assign reviews to GitHub teams), and Google Drive-adjacent file referencing plus a broad app ecosystem (Figma, GitLab, Sentry, Datadog, Notion, etc.), backed by OAuth/API infrastructure for deeper connections. Missing for 10: explicit first-party documentation of a native Google Drive integration specifically (only general file/import references appear) and independent hands-on confirmation of these integrations' reliability.

   • [claimed-docs] “Connect GitHub to automate PR workflows, review code in Linear, sync issues and understand your codebase with Linear Agent”
   • [claimed-docs] “Create issues from Slack messages and sync threads”
   • [claimed-docs] “You can now assign reviews to GitHub teams.”
   • [claimed-docs] “You can now assign reviews to GitHub teams. Review requests assigned to your GitHub teams appear in a dedicated section of the Reviews inbox…”
   • [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
   • [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”
   • [claimed-docs] “Learn how to reference a file in markdown content, or upload with the API”
   • [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”

   proof ↗⚑ flag

   monday.com✓fullclaimed8/10

   monday.com documents native integrations for Slack, GitHub/GitLab, and Google (Drive/Calendar/Gmail) via its integrations directory, plus a broader library of 850+ apps/integrations and GraphQL API/webhooks for custom connections. Community evidence criticizes general performance/UX but does not contradict integration functionality specifically. Missing for 10: independent hands-on verification of these specific native connectors and any noted integration-specific limitations.

   • [claimed-docs] “Link pull requests from GitHub or GitLab directly to their related items in monday.com so teams can quickly access code and updates in conte…”
   • [claimed-docs] “Integrate your org’s communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”
   • [claimed-docs] “Discover 850+ integrations and apps to centralize work, enhance collaboration, and drive better business results faster.”
   • [claimed-docs] “Work with tools like Claude, Copilot, and ChatGPT through official integrations or the monday MCP, and keep data secure with trusted AI conn…”
   • [claimed-docs] “Integrate your org's communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”
   • [claimed-docs] “Easily connect monday.com to thousands of other tools with - no development needed.”

   proof ↗⚑ flag

4. product managerConnect my workspace to thousands of third-party tools via an app marketplace

   weight 2 · round to monday.com
   Linear~partialclaimed6/10

   Linear ships a documented integrations/app directory (GitHub, Slack, Figma, Salesforce, Sentry, Datadog, Notion, Airbyte, Fivetran, Cursor, ChatGPT, Claude, Jira migration, etc.), an OAuth app creation flow, and admin-level third-party app approval controls, which together function like a marketplace for connecting external tools. However, the evidence shows a curated directory of a few dozen named integrations plus a general public GraphQL/OAuth API for building custom ones, not literally 'thousands' of pre-built marketplace apps as the story implies. Missing for 10: evidence of marketplace scale (thousands of listed apps), a searchable public app store UI, and independent confirmation of ecosystem breadth beyond Linear's own docs.

   • [claimed-docs] “Connect GitHub to automate PR workflows, review code in Linear, sync issues and understand your codebase with Linear Agent”
   • [claimed-docs] “Create issues from Slack messages and sync threads”
   • [claimed-docs] “Create and link issues directly from Figma”
   • [claimed-docs] “Automate your Merge Request workflow”
   • [claimed-docs] “Build custom dashboards and analytics from issue and project data”
   • [claimed-docs] “Delegate issues to Codex directly from Linear”
   • [claimed-docs] “Turn issues into pull requests with Cursor cloud agents”
   • [claimed-docs] “Automate work from issue to tested PR with Devin”
   • [claimed-docs] “Create Linear issues from Datadog Cases and Monitors”
   • [claimed-docs] “Smoothly transition from Jira to Linear”
   • [claimed-docs] “Sync your Linear data with the Fivetran connector”
   • [claimed-docs] “Create Linear issues from Salesforce cases”
   • [claimed-docs] “Connect Linear to Airbyte and consolidate data in data warehouses, lakes, and databases”
   • [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”
   • [claimed-docs] “Use URL parameters to send users directly to a pre-filled Create OAuth App form in Linear. An equivalent JSON manifest format lets you store…”

   proof ↗⚑ flag

   monday.com✓fullclaimed9/10

   monday.com documents an app marketplace/integrations directory with 850+ apps and integrations (Salesforce, Slack, GitHub, Zendesk, etc.), no-code connection options, and flexible APIs/SDKs for custom integrations, directly matching the story. Community evidence cited is about general UI performance/usability complaints, not integrations, so it does not contradict this axis. Missing for 10: independent third-party verification of the marketplace's breadth/quality beyond vendor claims.

   • [claimed-docs] “Discover 850+ integrations and apps to centralize work, enhance collaboration, and drive better business results faster.”
   • [claimed-docs] “Easily connect monday.com to thousands of other tools with - no development needed.”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Integrate Salesforce, Quickbooks, or HubSpot to manage leads, track opportunities, and keep your sales process proactive and results-driven.”
   • [claimed-docs] “Link pull requests from GitHub or GitLab directly to their related items in monday.com so teams can quickly access code and updates in conte…”
   • [claimed-docs] “Integrate your org’s communication tools - Slack, Gmail, Google Calendar, Outlook, Microsoft Teams, and more - to centralize communication a…”
   • [claimed-docs] “Enable 2-way sync between monday products and any platform you work with to trigger automations, eliminate manual work, and keep your busine…”
   • [claimed-docs] “Connect Zendesk or Active Directory to manage your support tickets in monday.com, helping teams resolve issues faster and keep customers hap…”

   proof ↗⚑ flag

Extensibility

1. designerBuild custom views and dashboard widgets that feel native to the product

   weight 1 · round to monday.com
   Linear—none0/10

   Evidence only shows saved/shareable filtered views (linear-docs-13) and standard issue/project views — there is no SDK, embed framework, or dashboard-widget builder that would let a designer create custom native-feeling widgets or dashboards. The public API/webhooks/SDK docs (linear-docs-49-53) are developer-facing data access, not a UI customization surface for designers.

   ⚑ flag

   monday.com~partialclaimed6/10

   monday's developer docs explicitly support building custom board/item views, dashboard widgets, and full-page apps, and provide the Vibe React component library specifically to make custom UI 'look native instantly.' However, evidence is limited to vendor docs with no independent/hands-on corroboration of designer experience building these views, and community feedback focuses on core product usability rather than the custom-view/widget building workflow itself. Missing for 10: independent or hands-on verification of the widget-building experience, and details on design constraints/limitations designers encounter when building native-feeling views.

   • [claimed-docs] “Create custom board views, item views, dashboard widgets, and full-page apps.”
   • [claimed-docs] “Build with Vibe, monday's open-source React components, and look native instantly.”
   • [claimed-docs] “Add actions to the item, board, and column menus, right where work happens.”

   proof ↗⚑ flag

Getting started

1. product managerThat exporting my workspace preserves full history—comments, attachments, and audit trails—not just task titles

   weight 3 · round drawn
   Linear—none0/10

   The evidence pack contains no mention of a workspace export feature at all—only import tooling (from other services into Linear) is documented, with nothing about exporting comments, attachments, or audit trails out of Linear. This is a fair question for a project-management tool, so absence of evidence means 'none' rather than 'na'.

   • [claimed-docs] “Import data from other services into Linear”
   • [claimed-docs] “Import tooling for uploading from other systems”

   proof ↗⚑ flag

   monday.com—none0/10

   No evidence pack items mention workspace export functionality, or preservation of comments, attachments, or audit trails during export; all documentation focuses on agents, integrations, and MCP servers. Missing for 10: any documentation of an export feature, evidence of what data (comments/attachments/audit logs) is retained, and any hands-on or community confirmation of export fidelity.

   ⚑ flag

2. engineerFollow a guided walkthrough to set up my workspace the first time

   weight 1 · round drawn
   Linear—none0/10

   No evidence describes an onboarding wizard, guided workspace setup, or first-run tutorial for new engineers; the pack covers agents, integrations, API docs, and changelog features but nothing about initial workspace configuration guidance.

   ⚑ flag

   monday.com—none0/10

   The evidence pack covers monday's developer platform, AI agents, and integrations but contains no mention of a guided onboarding walkthrough or first-time workspace setup flow for engineers. One community comment (monday-comm-10) even notes the product 'required too much setup and customization,' but this is not concrete counter-evidence of a documented walkthrough claim—there simply is no walkthrough feature evidenced.

   • [community] “I used monday.com a few years ago. Back then it was called 'dapulse'... I felt silly every time I said it. I just remember really wanting to…”

   proof ↗⚑ flag

3. product managerImport my data from another tool when switching over

   weight 2 · round to Linear
   Linear✓fullclaimed6/10

   Linear documents explicit import capabilities: generic 'Import data from other services into Linear' plus a dedicated Jira migration flow ('Smoothly transition from Jira to Linear') and import tooling for uploading from other systems mentioned in the repo README. This directly satisfies the PM's need to migrate data when switching tools, though detail is thin — missing for 10: specifics on which tools/formats are supported, what data (comments, attachments, custom fields) is preserved, and independent/community confirmation that migrations work smoothly in practice.

   • [claimed-docs] “Import data from other services into Linear”
   • [claimed-docs] “Import tooling for uploading from other systems”
   • [claimed-docs] “Smoothly transition from Jira to Linear”

   proof ↗⚑ flag

   monday.com~partialclaimed3/10

   Evidence shows monday.com offers many third-party integrations (Salesforce, HubSpot, Zendesk, GitHub, etc.) and flexible APIs/SDKs that could be used to move data in from other tools, but there is no explicit mention of an import wizard, CSV import, or dedicated 'migrate from X' onboarding flow for switching PMs. Missing for 10: explicit import/migration tooling (e.g., CSV/board import, one-click migration from competitor PM tools), independent confirmation that data import actually works smoothly during onboarding.

   • [claimed-docs] “Discover 850+ integrations and apps to centralize work, enhance collaboration, and drive better business results faster.”
   • [claimed-docs] “Enable 2-way sync between monday products and any platform you work with to trigger automations, eliminate manual work, and keep your busine…”
   • [claimed-docs] “Easily connect monday.com to thousands of other tools with - no development needed.”
   • [claimed-docs] “Integrate Salesforce, Quickbooks, or HubSpot to manage leads, track opportunities, and keep your sales process proactive and results-driven.”
   • [claimed-docs] “Link pull requests from GitHub or GitLab directly to their related items in monday.com so teams can quickly access code and updates in conte…”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”

   proof ↗⚑ flag

4. product managerJumpstart a new project using pre-built templates

   weight 2 · round drawn
   Linear—none0/10

   The evidence pack contains no mention of pre-built project or issue templates for jumpstarting new projects; the closest feature, the 'project composer' with Linear Agent, is AI-assisted drafting rather than a template library. missing for 10: any documentation of a templates gallery, template selection UI, or first-party/community evidence of template-based project creation.

   ⚑ flag

   monday.com—none0/10

   The evidence pack contains no mention of pre-built project templates, template galleries, or quick-start project setups for product managers; all docs items focus on AI agents, integrations, and developer/MCP features. missing for 10: any documentation of a template library, template selection during board/project creation, or industry-specific templates.

   ⚑ flag

Pricing transparency

1. product managerWhether my plan enforces a minimum seat count or annual billing commitment before I subscribe

   weight 3 · round drawn
   Linear—none0/10

   No evidence in the pack addresses pricing plans, seat minimums, or annual billing commitments for Linear's subscription plans; all evidence relates to product features, API, and integrations. Missing for 10: any pricing page or plan documentation disclosing seat minimums, billing cadence, or contract terms.

   ⚑ flag

   monday.com—none0/10

   No evidence in the pack addresses seat minimums or annual billing commitment terms; only a Free-plan credit-card mention is present, which does not answer the story's question about seat/billing enforcement.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Linear
   Linear~partialclaimed7/10

   Linear's GraphQL API exposes the same schema used internally to build the app, with full introspection, mutations for issues/projects/comments, webhooks, OAuth2/API key auth, and an SDK, covering most core CRUD and workflow operations (linear-docs-49, linear-supp-graphql-introspection, linear-docs-74, linear-docs-92-93). However, several UI-native features (Agent sessions/Loops orchestration nuances, admin spend limits, Okta/SSO provisioning, third-party app approval flows, mobile-specific review UI) are not clearly exposed as API-first operations, and no independent evidence confirms 1:1 parity between UI and API surfaces. missing for 10: explicit documentation/confirmation that all admin/security settings (SSO, spend limits, app approvals) and newer Agent/Loop features are fully API-controllable, plus independent verification of full UI-API parity.

   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
   • [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
   • [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
   • [claimed-docs] “query Issue { issue(id: "BLA-123") { id title description } }”
   • [claimed-docs] “const myIssues = await me.assignedIssues();”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
   • [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”

   proof ↗⚑ flag

   monday.com~partialclaimed6/10

   monday's GraphQL API, webhooks, granular scopes, and apps/MCP framework show broad programmatic access to boards, items, columns, and events, suggesting extensive API coverage of UI actions. However, there is no explicit claim or evidence that every UI capability (e.g., all board customizations, dashboard widgets, admin settings) is exposed via API, and no independent verification of API-UI parity. missing for 10: explicit vendor statement of full API/UI parity, independent test confirming coverage of edge-case UI features.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Request granular scopes like `boards:read`. Store keys in managed secret storage.”
   • [claimed-docs] “Subscribe to `create_item`, `change_column_value`, and more.”
   • [claimed-docs] “Listen for real-time events and run your workflow the moment data changes.”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”
   • [claimed-docs] “Run and manage every monday agent programmatically from your own code, anywhere you need it.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Linear
   Linear~partialcommunity4/10

   Linear has no documented one-click 'export all data' feature; however, its open GraphQL API (with full schema introspection, SDK, and reasonable rate limits) lets a technical user programmatically pull out all their issues, projects, and comments, which is a de facto exit path. There's no bulk-export or archive format documented, and community confirms no self-hosting option, meaning a full clean 'leave with your data' workflow is not officially supported. missing for 10: a documented bulk/archival export feature (e.g., JSON/CSV dump), official data-portability tooling, and independent confirmation that a full account export actually works.

   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
   • [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
   • [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
   • [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”

   proof ↗⚑ flag

   monday.com—none0/10

   The evidence pack contains no mention of a bulk data export feature, open-format export (CSV/JSON backup), or account portability tooling — only a GraphQL API for programmatic integration, which is not the same as a documented 'export everything and leave' capability. missing for 10: explicit data export/backup feature, open-format (CSV/JSON) full-account export documentation, any statement about data portability or account closure export.

   • [claimed-docs] “An expressive GraphQL API to interact with your workflows, automate processes, power integrations, and more!”
   • [claimed-docs] “Use our flexible APIs, SDKs to build custom apps and integrations tailored to your unique needs.”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Linear—none0/10

   No evidence indicates Linear's application source is published under an open license; the only related item is a stray README reference on GitHub (linear-docs-101) which does not establish an open-source license or full source availability. Linear is a closed, proprietary SaaS product per all other evidence (docs, integrations, community threads about lack of self-hosting).

   • [claimed-docs] “Import tooling for uploading from other systems”
   • [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”

   proof ↗⚑ flag

   monday.com—none0/10

   monday.com is a closed-source SaaS product; the only open-source item mentioned is 'Vibe' (a UI component library), not the core product's source code. No evidence of the platform's source being available under an open license.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Linear—none0/10

   Linear is explicitly a cloud-only SaaS with no self-hosting option; a community Q&A cites a direct Linear response stating 'We unfortunately don't currently have plans to provide self-hosting' (linear-comm-10). No docs anywhere in the evidence pack mention on-prem/self-hosted deployment.

   • [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”

   proof ↗⚑ flag

   monday.com—none0/10

   monday.com is explicitly a managed SaaS/cloud platform — docs state agents and apps run on monday-managed infra ('Your syncs and tools run on our infra, not yours', 'Your data never leaves our secure servers') with no mention of any self-hosted deployment option. No evidence of a self-hostable core product exists in the pack.

   • [claimed-docs] “Deploy to isolated sandboxes monday manages. Your syncs and tools run on our infra, not yours.”
   • [claimed-docs] “Get hosting, storage, secrets, and scaling on infra certified for SOC 2, HIPAA, and ISO 27001. Your data never leaves our secure servers.”
   • [claimed-docs] “Get hosting, storage, secrets, and scaling on infra certified for SOC 2, HIPAA, and ISO 27001.”

   proof ↗⚑ flag

Mobile access

1. engineerManage my tasks from a full-featured native mobile app without missing desktop functionality

   weight 2 · round to Linear
   Linear~partialclaimed4/10

   Docs show mobile app supports specific engineer workflows like reviewing code diffs and commenting (linear-docs-6) and, as of a recent update, document creation/editing (linear-docs-71), indicating mobile parity is being actively built out rather than already complete. There is no evidence of full task-management parity (e.g., initiatives, project views, filters, admin settings) on mobile, and no independent/community confirmation of a full-featured mobile experience. Missing for 10: comprehensive mobile feature-parity documentation covering all core desktop workflows (initiatives, filters, admin, integrations), and independent user reviews confirming no functionality gaps on mobile.

   • [claimed-docs] “Use the Linear mobile app to review code changes, comment on specific lines, and iterate with Linear Agent.”
   • [claimed-docs] “Document creation and editing are now available in Linear's iOS and Android apps.”

   proof ↗⚑ flag

   monday.com—none0/10

   No evidence pack items mention a native mobile app or any mobile-specific functionality/parity claims; all docs focus on web platform, APIs, agents, and integrations. Community comments discuss performance/usability issues on the general product but say nothing about mobile app feature parity.

   ⚑ flag

Task management

1. product managerTrack cross-team dependencies to coordinate large launches

   weight 2 · round to Linear
   Linear~partialclaimed5/10

   Linear's initiative feature lets a team be assigned to lead cross-team work with statuses (proposed/canceled) and priority, which supports coordinating large launches (linear-docs-4, linear-docs-14, linear-docs-37, linear-docs-63, linear-docs-76), and project-view subscriptions notify on changes (linear-docs-61). However, there's no explicit evidence of dependency-specific features like blocking/blocked-by issue relations or a dependency graph across teams. missing for 10: explicit issue-to-issue dependency/blocking relation docs, cross-team dependency visualization, hands-on evidence of coordinating a large launch using these features.

   • [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work”
   • [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside”
   • [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
   • [claimed-docs] “Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
   • [claimed-docs] “Plan and navigate from idea to launch. Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
   • [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”

   proof ↗⚑ flag

   monday.com—none0/10

   The evidence pack contains no documentation of dependency-tracking features (e.g., linked items, dependency columns, Gantt/timeline views) that would let a PM coordinate cross-team dependencies; nearly all monday-docs items focus on AI agents/MCP integration, unrelated to planning dependencies. One community comment (monday-comm-4) explicitly states 'Linking tickets to one another in Monday is really bad, data gets lost all the time,' which is negative anecdotal evidence but there's no vendor claim of dependency tracking to formally dispute. Missing for 10: any first-party documentation of dependency/linking features, timeline/Gantt views, or cross-team coordination workflows, and any positive hands-on evidence of this capability working.

   • [community] “I use it at my current company. I don't like it. I don't like Jira either, but Jira is still far superior... Linking tickets to one another …”

   proof ↗⚑ flag

2. product managerCustomize fields and workflow statuses to match my team's process

   weight 2 · round drawn
   Linear—none0/10

   The evidence pack contains no vendor documentation describing custom issue fields or configurable workflow statuses for teams; the only relevant community evidence explicitly states Linear lacks the ability to define different issue types or add custom fields, and describes this as a deliberate design choice against Jira-style customization.

   ⚑ flag

   monday.com—none0/10

   The evidence pack is dominated by AI-agent, MCP, and developer-platform documentation and contains no first-party or hands-on evidence describing monday.com's native field/column customization or workflow status editing capabilities for boards. While this is a fair axis for a work-management product, nothing in the pack concretely documents the ability to customize fields or workflow statuses, so it cannot be credited despite being a plausible feature.

   ⚑ flag

3. product managerTrack initiatives with status, priority, and an owning team

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear docs show initiatives support status (Proposed/canceled/other statuses), priority, and an owning team assignment ('assign a team to lead an initiative'), directly matching the story. missing for 10: independent hands-on corroboration of the initiative-tracking UI beyond changelog claims.

   • [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work”
   • [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside”
   • [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work and how it contributes to the broad…”
   • [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
   • [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”

   proof ↗⚑ flag

   monday.com—none0/10

   The evidence pack contains no documentation of monday.com's core board features (status columns, priority columns, owner/people columns) for tracking initiatives; nearly all provided evidence concerns the AI-agent/developer platform (MCP, agents, apps framework) rather than basic work-tracking functionality. Community evidence only speaks to general usability complaints, not specifically to status/priority/owner tracking.

   ⚑ flag

4. engineerPlan and manage sprints for agile software development

   weight 2 · round to Linear
   Linear~partialcommunity4/10

   Evidence shows Linear supports general agile planning artifacts—issues, priorities, initiatives, roadmaps, and project alignment (linear-docs-76, linear-docs-63, linear-docs-37)—and community comments confirm it functions as a fast issue tracker (linear-comm-1, linear-comm-6). However, the pack contains no direct evidence of Linear's sprint/cycle-specific features (e.g., cycle planning, sprint velocity, burndown, backlog grooming) that would confirm dedicated sprint management. Missing for 10: explicit documentation of Cycles/sprint creation, velocity tracking, sprint retrospectives, and backlog prioritization tools.

   • [claimed-docs] “Plan and navigate from idea to launch. Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
   • [claimed-docs] “Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
   • [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
   • [community] “We've been using Linear for a couple months. It's kind of like Superhuman in that the primary benefit is hotkeys. Otherwise it is an issue t…”
   • [community] “Can't speak for other teams... but we migrated from JIRA to Linear for our small team, and haven't looked back. Just the simple fact that it…”

   proof ↗⚑ flag

   monday.com—none0/10

   The evidence pack contains no mention of sprint planning, backlog management, story points, or agile-specific board templates for monday.com; it only covers AI-agent/MCP features, generic board views, and integrations (e.g., GitHub/GitLab PR linking) that don't address sprint/agile workflow support. Absence of evidence for this applicable planning-tracking capability means it cannot be credited as delivered.

   ⚑ flag

5. engineerCreate tasks and assign them to teammates with due dates

   weight 3 · round to Linear
   Linear~partialcommunity4/10

   Evidence confirms issue creation (IssueCreate mutation) and assignment (assignedIssues, agents 'delegated issues through assignment') as core API/product capabilities, implying basic task creation and assignment support, but no evidence pack item explicitly documents setting or displaying due dates on issues. Missing for 10: explicit documentation of a due-date field on issues, UI walkthrough of assigning a task with a due date, and independent confirmation of this specific workflow.

   • [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
   • [claimed-docs] “const myIssues = await me.assignedIssues();”
   • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
   • [community] “I have used Linear on a couple of my hobby projects and it's a great tool to quickly capture features and bugs. My one gripe... is that the …”

   proof ↗⚑ flag

   monday.com—none0/10

   The evidence pack contains no documentation or community reports describing monday.com's core item/task creation, assignee, or due-date fields — nearly all first-party docs here focus on AI agents/MCP integration rather than basic task management, and community comments only vaguely reference 'items' and 'tickets' without confirming assignment/due-date workflows. missing for 10: docs on creating items with owner/assignee columns, due-date column functionality, and any confirmation of this core PM workflow.

   • [community] “Hmm maybe I missed something but isn't Monday some kind of do-all task management system? A client of mine forced us on it and the un-opinio…”
   • [community] “I use it at my current company. I don't like it. I don't like Jira either, but Jira is still far superior... Linking tickets to one another …”

   proof ↗⚑ flag

6. engineerBreak work into subtasks and link dependent tasks so blocking order is clear

   weight 3 · round drawn
   Linear—none0/10

   The evidence pack contains no mention of sub-issues, issue hierarchies, or blocking/blocked-by dependency links—core planning-tracking features one would expect docs to cover for an issue tracker. Nothing here cites Linear's sub-issue or relation functionality, so this applicable axis is unsupported by the given evidence.

   ⚑ flag

   monday.com—none0/10

   The evidence pack contains no documentation of subtask creation or dependency/blocking-order linking features (all docs items focus on AI agents, MCP, and integrations). The only relevant evidence is a community complaint that 'linking tickets to one another in Monday is really bad, data gets lost all the time' (monday-comm-4), which is negative rather than confirmatory, and there is no vendor claim in this pack to set up a dispute.

   • [community] “I use it at my current company. I don't like it. I don't like Jira either, but Jira is still far superior... Linking tickets to one another …”

   proof ↗⚑ flag

7. engineerLog time directly against tasks and projects

   weight 2 · round drawn
   Linear—none0/10

   No evidence in the pack mentions time tracking, time logging, or timesheet functionality against tasks/projects in Linear; the evidence focuses on issue tracking, agents, coding sessions, and planning features.

   ⚑ flag

   monday.com—none0/10

   No evidence in the pack mentions time tracking, time logging columns, or timesheet features against tasks/projects; all citations focus on AI agents, integrations, and app-building framework. Missing for 10: any mention of a time-tracking column, timer widget, or timesheet reporting feature.

   ⚑ flag

Views organization

1. engineerHow the product performs and whether item caps apply in workspaces with tens of thousands of tasks

   weight 2 · round drawn
   Linear—none0/10

   No evidence pack item addresses performance benchmarks, scalability limits, or item caps for workspaces with tens of thousands of tasks; community comments only mention general speed vs Jira without scale specifics. This is a fair question for an issue tracker but remains unaddressed here.

   ⚑ flag

   monday.com—none0/10

   No vendor documentation addresses item caps or performance benchmarks at scale; the only relevant evidence is a hands-on community report stating boards would 'struggle and finally crash after a few thousand items,' capping usable scale around 20k items, directly contradicting the story rather than supporting it.

   • [community] “Until a while ago, when a user landed on their board, we threw all the board data right into the client... it started to struggle and finall…”
   • [community] “I tried using Monday.com for a building project I had and the interface become totally unusably slow... no idea if this is fixed but it seem…”
   • [community] “We'd tried it for a little bit for a small 5-6 person team. It was slow as hell. Stopped using it.”

   proof ↗⚑ flag

2. engineerSwitch between board, list, calendar, and timeline views of the same work

   weight 2 · round drawn
   Linear—none0/10

   The evidence pack has no mention of board, list, calendar, or timeline views, or of switching between them — only a generic reference to sharing 'any filtered view' via URL, which doesn't establish this specific multi-view capability.

   ⚑ flag

   monday.com—none0/10

   The evidence pack only mentions building custom board/item views and dashboard widgets (developer platform for apps), not the native ability to toggle a single board's data between board, list, calendar, and timeline layouts. No citation confirms this specific multi-view switching capability.

   ⚑ flag

3. engineerSave a filtered view of work and share it with a link

   weight 2 · round to Linear
   Linear✓fullclaimed9/10

   Linear explicitly documents saving/sharing filtered views: "You can now share any filtered view by copying its URL from your browser, or by pressing ⌘/Ctrl Shift C on desktop" (linear-docs-13), directly matching the story of sharing a filtered work view via link. Missing for 10: independent/hands-on community confirmation of this specific feature beyond the vendor changelog.

   • [claimed-docs] “You can now share any filtered view by copying its URL from your browser, or by pressing ⌘/Ctrl Shift C on desktop.”

   proof ↗⚑ flag

   monday.com—none0/10

   The evidence pack contains no mention of saved filtered views, view sharing, or shareable links for board/item views — all docs entries focus on AI agents, MCP, integrations, and APIs. This is a fair planning-tracking capability for a work OS product, but nothing in the pack demonstrates it.

   ⚑ flag

4. engineerSearch across all tasks, docs, and comments and get fast, accurate results

   weight 2 · round drawn
   Linear—none0/10

   The evidence pack contains no documentation or community commentary about a search feature spanning issues, docs, and comments, nor any claims about speed or accuracy of such search — only filtering/view-sharing and speed-of-loading tickets are mentioned, which is a different capability.

   ⚑ flag

   monday.com—none0/10

   The evidence pack contains no mention of a search feature spanning tasks, docs, and comments, nor any performance/accuracy claims about search; instead it focuses on integrations, AI agents, and developer platform features. Search is a fair and applicable axis for a work management tool, but no supporting evidence exists here.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Linear—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location controls for Linear workspaces; only unrelated features (access control via Okta, admin app approvals, self-hosting explicitly denied) are covered.

   • [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions. Admins can manage access centrally”
   • [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”

   proof ↗⚑ flag

   monday.com—none0/10

   Evidence mentions general infra security certifications (SOC2, HIPAA, ISO27001) and that data stays on monday's servers, but there is no mention of any region/data-residency selection option for customers. missing for 10: any documentation of selectable data regions, residency controls, or data-locality options.

   • [claimed-docs] “Get hosting, storage, secrets, and scaling on infra certified for SOC 2, HIPAA, and ISO 27001. Your data never leaves our secure servers.”
   • [claimed-docs] “Get hosting, storage, secrets, and scaling on infra certified for SOC 2, HIPAA, and ISO 27001.”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Linear—none0/10

   No evidence in the pack addresses AI training data opt-out or any policy preventing customer data from being used to train AI models; the pack covers agents, integrations, API, and workspace features but is silent on AI training data usage policy.

   ⚑ flag

   monday.com—none0/10

   No evidence pack item addresses opting out of AI model training or data usage policies for AI training; documentation covers security certifications (SOC2/HIPAA/ISO) and agent infrastructure but never mentions training data controls or opt-out mechanisms. Missing for 10: explicit AI training opt-out policy, data usage terms for model training, any admin toggle or contractual guarantee against training use.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Linear—none0/10

   The evidence pack covers admin access control, identity management (Okta/SSO), API rate limits, and agent behavior, but contains no mention of data retention policies, data deletion controls, or configurable retention windows for AI-generated content or session data. Missing for 10: any documentation of retention periods, deletion/export APIs, or admin controls specifically for purging AI agent data or session history.

   ⚑ flag

   monday.com—none0/10

   No evidence addresses data retention policies, deletion controls, or user ability to purge AI-related data; docs mention secure infra/compliance certifications but not retention/deletion controls specifically.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Linear—none0/10

   No evidence in the pack addresses telemetry or usage-tracking opt-out settings for Linear; the material covers agents, integrations, API, and product features but nothing about privacy/telemetry controls. Missing for 10: any documentation of a telemetry setting, opt-out toggle, privacy policy statement, or usage-tracking disclosure.

   ⚑ flag

   monday.com—none0/10

   No evidence in the pack addresses telemetry opt-out or usage-tracking controls for AI-native users; docs cover security/compliance certifications but not user-facing telemetry settings. Missing for 10: any documentation of a telemetry/usage-tracking toggle or opt-out mechanism.

   ⚑ flag

Ai insights

1. ai-native userAsk AI a question and get an instant answer with citations from my workspace content

   weight 2 · round drawn
   Linear—none0/10

   The evidence shows Linear Agent can draft updates by gathering context (e.g. 'Write with Agent' reviewing changes and Slack messages) and supports MCP integrations for external AI tools, but there is no documented feature where a user can directly ask a question and receive an instant answer with citations pulled from workspace content. This is a plausible axis for a workspace tool, but no such Q&A/citation feature is evidenced.

   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
   • [claimed-docs] “Connect ChatGPT deep research to Linear”
   • [claimed-docs] “Previews of Linear issues, views and projects and query Notion AI”

   proof ↗⚑ flag

   monday.com—none0/10

   Evidence covers AI agents, integrations, MCP, and automation but nothing describes a workspace Q&A feature where a user asks a question and receives an answer with citations back to specific workspace content. Vague phrases like 'Surface deep intelligence and actionable insights' or 'Spot risks and progress gaps' do not describe citation-backed instant answers.

   ⚑ flag

2. ai-native userHave AI draft a project or initiative status update from recent activity

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear's 'Write with Agent' feature explicitly drafts project status updates by reviewing recent activity changes and linked Slack messages, and Loops can also react to initiative/project changes to keep documents and plans updated automatically. Missing for 10: independent/hands-on corroboration of update quality, and explicit first-party example of initiative-level (vs project-level) status update drafting.

   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
   • [claimed-docs] “You can now edit text with Linear Agent, and use Loops to keep docs and project descriptions up-to-date. Author name indicators let you chec…”

   proof ↗⚑ flag

   monday.com✓fullclaimed7/10

   monday.com's own docs explicitly describe automating status updates and performance reports on a schedule, plus AI agents surfacing insights and spotting progress gaps, directly matching the story of AI drafting status updates from activity. Missing for 10: independent/hands-on verification of output quality and more detail on exactly how 'recent activity' data feeds into the drafted update.

   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Spot risks and progress gaps before they become problems.”
   • [claimed-docs] “Surface deep intelligence and actionable insights from any subject.”

   proof ↗⚑ flag

Dashboards

1. product managerBuild dashboards and widgets to report on project progress

   weight 2 · round to monday.com
   Linear—none0/10

   The evidence pack covers Linear's agent/AI coding features, initiatives, teams, and API/webhooks extensively, but contains no mention of dashboard-building or configurable reporting widgets for tracking project progress. Filtered/shared views (linear-docs-13) and project view event subscriptions (linear-docs-61) are the closest hints, but neither describes a dashboard or widget system a PM could assemble for progress reporting.

   • [claimed-docs] “You can now share any filtered view by copying its URL from your browser, or by pressing ⌘/Ctrl Shift C on desktop.”
   • [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
   • [community] “The killer missing feature for us is that we can't define different issue types... there's no way to show the issue layout as an expandable …”

   proof ↗⚑ flag

   monday.com~partialcommunity6/10

   Monday's own docs explicitly state you can build custom dashboard widgets and views (monday-docs-3) and automate status/performance reporting (monday-docs-21) and surface risk/progress insights (monday-docs-22), directly matching the PM reporting story. However, there is no independent or hands-on validation of dashboard widget usability, and community reports describe severe performance degradation with large boards (thousands of items) which could undermine dashboard reliability at scale. missing for 10: independent corroboration of dashboard-building workflow, evidence dashboards remain performant/usable at scale, concrete examples of widget types used for reporting.

   • [claimed-docs] “Create custom board views, item views, dashboard widgets, and full-page apps.”
   • [claimed-docs] “Automate status updates and performance reports on a set schedule.”
   • [claimed-docs] “Spot risks and progress gaps before they become problems.”
   • [community] “Until a while ago, when a user landed on their board, we threw all the board data right into the client... it started to struggle and finall…”

   proof ↗⚑ flag

2. product managerRoll up progress across multiple projects into a single portfolio view

   weight 2 · round to Linear
   Linear~partialclaimed4/10

   Linear's Initiatives feature (grouping multiple projects under a lead team, with status like proposed/canceled and priority) points toward portfolio-style organization, but the evidence never explicitly describes progress roll-up (e.g., aggregated completion percentages or a dedicated portfolio dashboard) across projects. Missing for 10: explicit documentation of progress aggregation/visualization across projects, independent/hands-on confirmation of a portfolio view, and any reporting-specific UI details beyond initiative metadata.

   • [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work”
   • [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work and how it contributes to the broad…”
   • [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside”
   • [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
   • [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”
   • [claimed-docs] “Plan and navigate from idea to launch. Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”

   proof ↗⚑ flag

   monday.com—none0/10

   The evidence pack is almost entirely about monday's AI agents, MCP/developer platform, and third-party integrations, with no documentation of a portfolio-level rollup view aggregating progress across multiple projects/boards. General integration claims (e.g., monday-docs-33) refer to cross-platform data sync, not a PM-facing portfolio dashboard.

   ⚑ flag

Access control

1. product managerReview an admin audit log of actions taken across the workspace

   weight 2 · round to monday.com
   Linear—none0/10

   The evidence pack contains no mention of an admin audit log feature listing actions taken across the workspace; the only near-miss reference (linear-docs-59) discusses private teams enabling 'audits' as a use case, not an actual audit log capability. This is an applicable security/compliance axis for a workspace tool like Linear, but no evidence shows it delivers the capability.

   ⚑ flag

   monday.com~partialclaimed4/10

   Docs mention admins can 'audit every action' an AI agent takes as part of agent governance, implying some audit logging exists, but there's no evidence of a general admin audit log covering all user/workspace actions (logins, permission changes, item edits) as a PM would expect for security review. missing for 10: evidence of a comprehensive audit log covering human user actions across the workspace, not just AI agent activity; independent/hands-on confirmation of audit log usability.

   • [claimed-docs] “Scope each agent's board access from the admin, audit every action it takes, and track AI credit spend across the whole org — all from one d…”

   proof ↗⚑ flag

2. product managerAssign granular permissions and roles to control who can view or edit work

   weight 2 · round to Linear
   Linear~partialclaimed5/10

   Linear offers some access-control building blocks—private/restricted sub-teams and initiatives that limit visibility to team members (linear-docs-15, linear-docs-29, linear-docs-40, linear-docs-59), Okta-based identity and 'existing Linear permissions' management (linear-docs-5, linear-docs-60, linear-docs-67), and admin approval of third-party apps (linear-docs-73)—but there's no evidence of granular, role-based view/edit permission assignment at the issue or field level that a PM could configure themselves. Missing for 10: documented custom roles/permission levels, per-user or per-field view/edit controls, and any PM-facing UI for assigning such permissions beyond team membership.

   • [claimed-docs] “Private sub-teams organize groups that work together under one umbrella, like independent business units, skunkworks efforts, or teams handl…”
   • [claimed-docs] “For work that requires tighter access, initiatives led by private teams are only visible to team members.”
   • [claimed-docs] “Restricted to parent team members — parent team members can see and choose to join the sub-team... Private to team members — the team is hid…”
   • [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”
   • [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions.”
   • [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions. Admins can manage access centrally”
   • [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”
   • [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”

   proof ↗⚑ flag

   monday.com—none0/10

   The evidence pack only discusses scoping and auditing AI agent board access (e.g., monday-docs-10, monday-docs-6) and general integration/security certifications, but contains no evidence of human-facing granular roles/permissions (viewer/editor/guest, board-level access control) that a product manager would assign to team members. Missing for full credit: documentation of user role types, board/item permission settings, or admin controls for human collaborators.

   ⚑ flag

3. product managerCreate private sub-teams restricted to specific members

   weight 1 · round to Linear
   Linear✓fullclaimed9/10

   Linear's docs explicitly describe private sub-teams with restricted visibility options — 'Private to team members — the team is hidden, except to members directly invited to that sub-team' and 'Restricted to parent team members', directly matching the story of PM-created private sub-teams limited to specific members. Additional docs confirm these sub-teams can organize sensitive-data groups and that initiatives led by private teams stay confidential. Missing for 10: independent/hands-on corroboration beyond vendor docs.

   • [claimed-docs] “Private sub-teams organize groups that work together under one umbrella, like independent business units, skunkworks efforts, or teams handl…”
   • [claimed-docs] “Restricted to parent team members — parent team members can see and choose to join the sub-team... Private to team members — the team is hid…”
   • [claimed-docs] “For work that requires tighter access, initiatives led by private teams are only visible to team members.”
   • [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”

   proof ↗⚑ flag

   monday.com—none0/10

   No evidence in the pack discusses private sub-teams, member-level board restrictions, or team-based access controls within monday.com's workspace/board permission model; all evidence pertains to AI agents, MCP, integrations, or general product sentiment.

   ⚑ flag

4. engineerSecure organization access with SSO and SAML

   weight 3 · round to Linear
   Linear~partialclaimed7/10

   Linear's docs describe Okta-based identity verification and centralized access management for admins, indicating SSO support, and the MCP changelog confirms managing employee access via Okta-managed identity. However, none of the evidence explicitly mentions SAML configuration or enterprise SSO setup details, and there's no independent/hands-on confirmation of the feature working. Missing for 10: explicit SAML protocol documentation, broader SSO provider support beyond Okta, and independent verification of enforcement.

   • [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions.”
   • [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions. Admins can manage access centrally”
   • [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”
   • [claimed-docs] “Admins can manage access centrally, without requiring employees to sign in or authorize Linear individually.”

   proof ↗⚑ flag

   monday.com—none0/10

   No evidence pack items mention SSO, SAML, identity providers, or authentication standards for organizational access; all docs focus on agents, MCP, integrations, and infra certifications (SOC 2, HIPAA, ISO 27001) rather than SSO/SAML specifically. Missing for 10: any documentation of SSO/SAML support, identity provider integration (Okta, Azure AD, etc.), or admin configuration for enterprise authentication.

   ⚑ flag

Trust reliability

1. product managerThe vendor's published uptime SLA and can check real-time incident status via a public status page

   weight 3 · round drawn
   Linear—none0/10

   No evidence pack item mentions a published uptime SLA or a public status page with real-time incident status; only unrelated docs, community sentiment, and API/agent features are provided. Missing for 10: any mention of an SLA commitment, a status page URL, or incident history/uptime reporting.

   ⚑ flag

   monday.com—none0/10

   No evidence pack item mentions an uptime SLA or a public status page for monday.com; all docs relate to integrations, agents, and infra certifications, not incident transparency. missing for 10: published uptime SLA, public status page URL, real-time incident history.

   ⚑ flag

2. product managerThe vendor's documented support response times for each plan tier

   weight 2 · round drawn
   Linear—none0/10

   No evidence pack item mentions support response time SLAs or plan-tier support commitments; the pack covers product features, API, and agent capabilities but nothing about documented support response times per pricing tier.

   ⚑ flag

   monday.com—none0/10

   No evidence in the pack mentions support response times, SLAs, or tiered support commitments for any monday.com plan; the evidence covers product features, integrations, and community sentiment unrelated to support SLAs.

   ⚑ flag