How Linear Engineering Velocity Reporter Tracks Speed

It is Thursday afternoon and your engineering manager needs a velocity report for tomorrow’s leadership sync. She opens Linear, Notion, Slack, exports the last 3 sprints, calculates completion rates in a spreadsheet, compares against the previous quarter, and writes a summary. Two hours later, the report is done — and it is already missing this week’s data.

The gap is not data availability — it is analysis throughput. Raw ticket counts and status boards do not answer the questions that matter: which risks are systemic, which bottlenecks recur, which patterns predict delivery delays. Linear Engineering Velocity Reporter automates the engineering intelligence workflow, converting raw Linear, Notion, Slack data into structured analysis without manual compilation.

Four Agents. Weekly Velocity Report. Dual-Audience Insights.

The Linear Engineering Velocity Reporter pipeline runs 4 agents in sequence. The Fetcher pulls data from Linear and Notion and Slack, and The Formatter delivers the output. Here is what happens at each stage and why it matters.

• The Fetcher (Code-only): Queries Linear GraphQL API for completed issues across the lookback window — assignees, estimates, labels, state transitions, and completion timestamps.
• The Assembler (Code-only): Computes 5 Velocity Health Dimensions: throughput trend (week-over-week vs 4-week baseline), bottleneck identification (state accumulation analysis), contribution distribution (Gini coefficient), bug/feature ratio (label classification), and cycle time health (median, P90, outliers)..
• The Analyst (Classification): Scores each dimension 1-10 (VHS), classifies overall health (HEALTHY/CONCERNING/CRITICAL), produces dual-audience output: executive summary for eng leadership + engineering recommendations with specific actions.
• The Formatter (Creative): Generates a Notion weekly velocity report with dimension breakdowns, trend data, and recommendations, plus a Slack Block Kit digest for the eng-leadership channel with VHS scores, executive summary, and top 3 actions..

When the pipeline completes, you get structured output that is ready to act on. The blueprint bundle includes everything needed to deploy, configure, and customize the workflow:

• 24-node main workflow + 3-node scheduler
• Weekly engineering velocity report from Linear completed issue data
• 5-dimension Velocity Health Score (VHS): throughput trend, bottleneck identification, contribution distribution, bug/feature ratio, cycle time health
• VHS 1-10 per dimension with overall health classification (HEALTHY/CONCERNING/CRITICAL)
• Dual-audience output: executive summary for leadership + engineering recommendations for the team
• Throughput decline >20% triggers URGENT alert with root cause analysis
• Per-week throughput trend with 4-week rolling baseline comparison
• Contribution distribution via Gini coefficient — detects bus factor risk
• Bug/feature ratio monitoring with label-based classification
• Cycle time analysis with median, P90, and outlier detection (>3x median)
• Notion velocity report with dimension breakdowns and trend charts
• Slack Block Kit digest with VHS scores and top 3 recommendations
• Configurable: team IDs, velocity metric (issues/points), baseline weeks, alert threshold
• Full technical documentation + system prompts

Sprint window, metric calculations, and report format are configurable in the system prompts — adapt to your team’s workflow without modifying the pipeline. This means Linear Engineering Velocity Reporter adapts to your specific process, terminology, and integration requirements without forking the entire workflow.

Understanding how the pipeline works helps you customize it for your environment and troubleshoot issues when they arise. Here is a step-by-step walkthrough of the Linear Engineering Velocity Reporter execution flow.

Step 1: The Fetcher

Tier: Code-only

The pipeline starts here. Queries Linear GraphQL API for completed issues across the lookback window — assignees, estimates, labels, state transitions, and completion timestamps. Groups issues by week for trend analysis.

This stage ensures all downstream agents receive clean, validated input. If this step returns incomplete data, every downstream agent works with a degraded picture.

Step 2: The Assembler

Tier: Code-only

Computes 5 Velocity Health Dimensions: throughput trend (week-over-week vs 4-week baseline), bottleneck identification (state accumulation analysis), contribution distribution (Gini coefficient), bug/feature ratio (label classification), and cycle time health (median, P90, outliers).

Why this step matters: The result is a prioritized action queue, not just a data dump.

Step 3: The Analyst

Tier: Classification

Scores each dimension 1-10 (VHS), classifies overall health (HEALTHY/CONCERNING/CRITICAL), produces dual-audience output: executive summary for eng leadership + engineering recommendations with specific actions. Flags throughput decline >20% as URGENT alert.

Every field in the output is structured for the next agent to consume without parsing.

Step 4: The Formatter

Tier: Creative

This is the final deliverable — what lands in your inbox or dashboard. Generates a Notion weekly velocity report with dimension breakdowns, trend data, and recommendations, plus a Slack Block Kit digest for the eng-leadership channel with VHS scores, executive summary, and top 3 actions.

The entire pipeline executes without manual intervention. From trigger to output, every decision point follows a documented path. Every execution produces a traceable audit trail.

All nodes have been validated during Independent Test Protocol (ITP) testing on n8n v2.7.5. The error handling matrix in the bundle documents the recovery path for each failure mode.

Webhooks send event_id, Calendar sends id, test fixtures send record_id. Three input sources, three different field names for the same concept. We detect format by field presence, not flags or configuration. If event_id exists, it is webhook format. If id exists without event_id, it is calendar format. No ambiguity.

— ForgeWorkflows Engineering

Weekly 5-dimension engineering velocity analysis with dual-audience reporting (exec summary + eng recommendations) and dual-channel delivery (Notion velocity report + Slack digest with VHS scores).

The primary operating cost for Linear Engineering Velocity Reporter is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Run: ~$0.03-$0.10/run (weekly aggregate). This figure includes all API calls across all agents in the pipeline — not just the primary reasoning step, but every classification, scoring, and output generation call.

To put this in context, consider the manual alternative. A skilled team member performing the same work manually costs $60–90/hour for an engineering manager’s reporting time at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 2–4 hours weekly, the per-execution cost in human labor is significant. The blueprint executes the same pipeline for a fraction of that cost, with consistent quality and zero fatigue degradation.

Infrastructure costs are separate from per-execution LLM costs. You will need an n8n instance (self-hosted or cloud) and active accounts for the integrated services. The estimated monthly infrastructure cost is ~$0.03-0.10 per weekly run + Linear subscription., depending on your usage volume and plan tiers.

Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12. ITP result is 8/8 variations, 14/14 milestones. These are not marketing claims — they are test results from structured inspection protocols that you can review in the product documentation.

All cost and performance figures are ITP-measured — tested against real data fixtures on n8n v2.7.5 in March 2026. See the product page for full test methodology.

7 files.

When you purchase Linear Engineering Velocity Reporter, you receive a complete deployment bundle. This is not a SaaS subscription or a hosted service — it is a set of files that you own and run on your own infrastructure. Here is what is included:

• CHANGELOG.md — Version history
• README.md — Setup and configuration guide
• docs/TDD.md — Technical Design Document
• linear_engineering_velocity_reporter_v1_0_0.json — n8n workflow (main pipeline)
• system_prompts/analyst_system_prompt.md — Analyst system prompt
• system_prompts/formatter_system_prompt.md — Formatter system prompt
• workflow/levr_scheduler_v1_0_0.json — Scheduler workflow

Start with the README.md. It walks through the deployment process step by step, from importing the workflow JSON into n8n to configuring credentials and running your first test execution. The dependency matrix lists every required service, API key, and estimated cost so you know exactly what you need before you start.

Every file in the bundle is designed to be read, understood, and modified. There is no obfuscated code, no compiled binaries, and no phone-home telemetry. You get the source, you own the source, and you control the execution environment.

Linear Engineering Velocity Reporter is built for Engineering, Leadership teams that need to automate a specific workflow without building from scratch. If your team matches the following profile, this blueprint is designed for you:

• You operate in a engineering or leadership function and handle the workflow this blueprint automates on a recurring basis
• You have (or are willing to set up) an n8n instance — self-hosted or cloud
• You have active accounts for the required integrations: Linear account with API access, Anthropic API key, Notion workspace, Slack workspace (Bot Token with chat:write)
• You have API credentials available: Anthropic API, Linear (httpHeaderAuth, Bearer prefix), Notion (httpHeaderAuth Bearer), Slack (Bot Token, httpHeaderAuth Bearer)
• You are comfortable importing a workflow JSON and configuring API keys (the README guides you, but basic technical comfort is expected)

This is NOT for you if:

• Does not create Linear issues — use Feature Request Extractor (#20) for Slack-to-Linear issue creation
• Does not predict sprint risk — use Linear Sprint Risk Analyzer (#46) for forward-looking per-sprint risk analysis
• Does not audit backlog health — use Linear Backlog Grooming Intelligence (#53) for staleness and priority distribution audits
• Does not modify Linear data — this is a read-only analysis tool
• Does not work with non-Linear project management tools — this is Linear-specific
• Does not track individual developer performance — this is team-level velocity analysis

Review the dependency matrix and prerequisites before purchasing. If you are unsure whether your environment meets the requirements, contact support@forgeworkflows.com before buying.

Every pipeline has boundaries. These are intentional design decisions, not oversights — understanding them helps you deploy with the right expectations and plan for edge cases in your environment.

Does not create Linear issues — use Feature Request Extractor (#20) for Slack-to-Linear issue creation

This is intentional. We default to human-in-the-loop for actions that carry reputational or financial risk. Once your team has validated output accuracy over 20+ cycles, you can adjust the pipeline to auto-execute — the workflow JSON supports it, but the default is conservative.

Does not predict sprint risk — use Linear Sprint Risk Analyzer (#46) for forward-looking per-sprint risk analysis

We scoped this boundary after ITP testing revealed inconsistent results when the pipeline attempted this. The agents handle what they handle well — extending beyond this scope requires custom prompt engineering specific to your data shape.

Does not audit backlog health — use Linear Backlog Grooming Intelligence (#53) for staleness and priority distribution audits

This keeps the pipeline focused on a single workflow. Adding this capability would introduce branching logic that varies by organization, and the tradeoff between complexity and reliability was not worth it for a reusable blueprint. Fork the workflow JSON if your use case demands it.

Deployment follows a structured sequence. The Linear Engineering Velocity Reporter bundle is designed for the following tools: n8n, Anthropic API, Linear, Notion, Slack. Here is the recommended deployment path:

1. Step 1: Import workflows and configure credentials. Import both workflow JSON files into n8n (main + scheduler). Configure Linear API key (httpHeaderAuth with Bearer prefix), Notion API token (httpHeaderAuth with Bearer prefix), Slack Bot Token (httpHeaderAuth with Bearer prefix, chat:write scope), and Anthropic API key following the README.
2. Step 2: Configure velocity parameters. Set LINEAR_TEAM_IDS (team IDs to analyze), VELOCITY_METRIC (issues or points), BASELINE_WEEKS (default 4), DECLINE_ALERT_THRESHOLD (default 0.2 for 20%), NOTION_DATABASE_ID, and SLACK_CHANNEL in the scheduler Payload Builder node.
3. Step 3: Activate scheduler and verify. Update the webhook URL in the scheduler Trigger Main Workflow node to match your main workflow webhook path. Activate both workflows. Send a test POST with _is_itp: true and sample velocity data. Verify the velocity report appears in Notion and the digest with VHS scores appears in Slack.

Before running the pipeline on live data, execute a manual test run with sample input. This validates that all credentials are configured correctly, all API endpoints are reachable, and the output format matches your expectations. The README includes test data examples for this purpose.

Once the test run passes, you can configure the trigger for production use (scheduled, webhook, or event-driven — depending on the blueprint design). Monitor the first few production runs to confirm the pipeline handles real-world data as expected, then let it run.

For technical background on how ForgeWorkflows blueprints are built and tested, see the Blueprint Quality Standard (BQS) methodology and the Inspection and Test Plan (ITP) framework. These documents describe the quality gates every blueprint passes before listing.

Ready to deploy? View the Linear Engineering Velocity Reporter product page for full specifications, pricing, and purchase.