Engineering Weekly Report Agent
aka “Eng Pulse” in the catalog
Friday afternoon: what engineering shipped, what's stuck and why, and where the delivery risk is. One honest read of the team's week, pulled from the tools, not a status meeting.
- Category
- Engineering, Operations
- Scheduled tasks
- 3daily, weekly, monthly
- Runtime
- Hermes
- Works with
- GitHubLinearJiraSentrySlack
- Hosting
- Fully managed, always on
- Weekly Eng PulseWeekly on Friday at 15:00
- Blocked RadarWeekdays at 10:00
- Monthly Eng ReviewMonthly on day 1 at 15:00
- Mon
- 10:00Blocked Radar
- Tue
- 10:00Blocked Radar
- Wed
- 10:00Blocked Radar
- Thu
- 10:00Blocked Radar
- Fri
- 10:00Blocked Radar
- 15:00Weekly Eng Pulse
How the Engineering Weekly Report Agent works
Every run reads from the tools you connect, works through its brief, and keeps what it learns in a persistent workspace, so context carries forward instead of starting from scratch.
Connect the ones you use. It works with what it has.
- Weekly Eng PulseWeekly on Friday at 15:00
- Blocked RadarWeekdays at 10:00
- Monthly Eng ReviewMonthly on day 1 at 15:00
Keeps in its workspace
- Who the owner is: business, timezone, quiet hours, delivery channel
- What good looks like: targets, sources to include and exclude, the blocked threshold, what the owner optimizes for
A report after each run
Sent to your Slack, Telegram, or another channel you connect.
Drafts that wait for you
Anything that leaves your business is written for your approval, not sent on its own.
Answers in chat
Ask it about its work any time from the agent's chat in your dashboard.
The Engineering Weekly Report Agent, on autopilot
Each task runs on its own schedule in a managed environment. Adjust any of them, or add your own.
Task 01Weekly on Friday at 15:00
Weekly Eng Pulse
Send the Friday engineering pulse covering the week, from every configured source per ~/workspace/DELIVERY.md (honoring its exclusions): delivery…
Once a week
Task 02Weekdays at 10:00
Blocked Radar
Check for work that is NEWLY stuck since ~/state/flow-seen.json (update it; exit fast when nothing changed): items blocked past the threshold in ~/workspace/DELIVERY.md, PRs waiting on review beyond the review SLA…
About 5 runs a week
Task 03Monthly on day 1 at 15:00
Monthly Eng Review
Compile the monthly engineering review for leadership: the month's trend lines from ~/state/pulse-history.json, DORA-style metrics flagged as directional rather than a scoreboard…
What it delivers
Each run ends with a message in your channel. Here is the brief the Engineering Weekly Report Agent's first task works from.
Engineering Weekly Report AgentAGENTWeekly on Friday at 15:00
Weekly Eng Pulsecompleted
The brief: Send the Friday engineering pulse covering the week, from every configured source per ~/workspace/DELIVERY.md (honoring its exclusions): delivery…
Deploy this template and Qoren provisions a dedicated, managed cloud environment: no Docker, VPS, or server upkeep. Tailor the persona, schedules, and tools, use the managed model key or bring your own, and the agent stays online with activity, usage, and spend in one dashboard.
Engineering Weekly Report Agent template questions
What does the Engineering Weekly Report Agent template do?
Friday afternoon: what engineering shipped, what's stuck and why, and where the delivery risk is. One honest read of the team's week, pulled from the tools, not a status meeting. It runs 3 scheduled tasks on a managed cloud environment.
Which runtime does the Engineering Weekly Report Agent use?
It runs on the Hermes runtime in a dedicated cloud environment that Qoren provisions and keeps online for you.
How often does the Engineering Weekly Report Agent run?
On a schedule you control. Out of the box it runs weekly on friday at 15:00, weekdays at 10:00, monthly on day 1 at 15:00. You can change the cadence, or trigger it on demand.
Will the Engineering Weekly Report Agent do things without my approval?
No. It drafts and prepares the work, and you stay in control of anything that leaves your business. A reply, an invoice reminder, or a public post is written for your approval, not sent on its own.
What do I need to connect before it works?
Start from the template and connect the tools it needs, then set a model key: use the managed key included with your plan, or bring your own on any plan. The Engineering Weekly Report Agent runs on the Hermes runtime.
Templates that pair well with this one.
Deploy it alongside these to cover the whole workflow.
Explore use cases- Engineering
Application Security Review Agent
aka “Appsec Reviewer”
The security holes already sitting in your codebase (injection, broken auth, leaked secrets, unsafe data flows) found, ranked by exploitability, and explained with the fix. Your code only, read-only, propose-only.
Weekly on Monday at 04:00+1 more
Works with GitHub, Linear, Jira, Slack.2 tasks - Engineering
Dependency Upgrade Agent
aka “Dependency Upgrader”
Outdated and vulnerable dependencies caught, the upgrade prepared and tested on a branch, the changelog risk spelled out. A draft PR you merge, never one that merges itself.
Weekly on Monday at 06:00+2 more
Works with GitHub, Snyk, Linear, Slack.3 tasks - Engineering
Incident Triage Agent
aka “Incident Triager”
New production errors triaged the moment they spike: grouped, blamed on the deploy that likely caused them, root-cause hypothesis and the suspect file:line attached, so you debug from a lead, not a wall of stack traces.
Every 15 minutes+1 more
Works with Sentry, GitHub, Linear, Datadog, Slack.2 tasks
Deploy the Engineering Weekly Report Agent today.
Sign in, start from this template, and go live in minutes. Plans from $39/mo.