GitHub

TaskOps Helpdesk Roadmap

> Experimental template: This plan supports private demos only. Details may change between exports until the gallery is fully public.

_Last updated: 2025-11-06_

Overview

TaskOps Helpdesk is our flagship template for showing Weldr to developers and investors. It combines tasks, approvals, SLAs, and multi-channel notifications to highlight:
  • • Natural-language authoring of real workflows
  • • Progressive Ownership (managed → extended) when editing scaffolds
  • • Preview-ready UI + generated code that developers can extend immediately

    • This document describes the public-facing demo plan. Internal automation details now live in docs/internal/automation-roadmap.md.

    Hero Flow (Web App Demo)

  • Kickoff prompt – “Create a helpdesk for inbound tickets with tasks and SLA tracking.”
    • - App Model shows Ticket ↔ Task ↔ Comment, with status + priority fields.
  • Approval workflow – “Add an approval workflow with pending → approved states and escalation notifications.”
    • - Workflow + notifications capabilities appear with clear spec summaries.
  • Progressive ownership moment – Flip the notifications provider to Extended, edit the @custom Slack handler, and regenerate to prove the block stays intact.
  • Preview proof – Use the preview pane to create a ticket, assign tasks, and trigger a notification event.
  • Template publish – Show the “Use this template” button that seeds the same DSL + code for any user.

    • Hero Script (Draft)

    | Step | Prompt / Action | Expected Result | | --- | --- | --- | | 1 | “Create a helpdesk for inbound tickets. I need tickets with status, tasks assigned to agents, comments, and SLA targets.” | DSL creates Ticket (status, slaMinutes), Task (assignee, status), Comment; relationships Ticket→Task, Ticket→Comment. Preview boots with seeded ticket list. | | 2 | “Add a state-machine workflow named TicketApproval that controls Ticket.status with states pending, approved, escalated.” | Workflow capability surfaces with those states; App Model highlights workflow node. | | 3 | “Add approveTicket (pending→approved) and escalateTicket (approved→escalated) transitions. approveTicket triggers sendApprovalEmail; escalateTicket triggers sendEscalationAlert.” | Workflow transitions persist with actions attached. | | 4 | “Send Slack and email notifications when a ticket is escalated. Store history so we can audit alerts.” | Notifications capability shows channels [slack, email], triggers escalated, storeHistory: true. | | 5 | Flip notifications provider to Extended and edit Slack handler (lib/server/notifications/providers/slack.ts). | Ownership badge switches to Extended; custom block added. | | 6 | “Add SLA breach reminders every 2 hours until the ticket is approved.” | Workflow/notifications update; spec reflects reminder action; preview data seeds sample breach. | | 7 | Preview -> create ticket, escalate, observe notification log; show GitHub export (optional). | Demonstrates end-to-end reliability. |

    _(Record screenshots / DSL snapshots for each step; store under docs/demos/assets/taskops/.)_

    Deliverables

    | Asset | Description | Owner | | --- | --- | --- | | Hero script | Final prompt list, expected DSL diffs, screenshots for each step | Docs | | Template bundle | DSL + generated files + ownership manifest checked into repo | Engineering | | Preview data seeding | Script/reset that preloads sample tickets/tasks | Engineering | | Developer handoff guide | How to locate key files, ownership status, recommended custom hooks | Developer Experience |

    Template Exporter Requirements

  • CLI command (pnpm template:export taskops-helpdesk) that:
    • - Loads an eval bundle (default: eval-output/taskops-helpdesk.bundle.json; pass --bundle to override). - Writes templates/apps/taskops-helpdesk/ with DSL JSON, ownership manifest, full bundle, and template metadata. - Generates a manifest entry consumed by the web app template gallery (template.json).
  • Validation step ensuring required files exist (weldr.app.json, weldr.ownership.yaml, bundle.json, template.json, README.md).
  • Optionally upload bundle metadata for “Use this template” button (includes description, capability list, last verified score).

    • # Generate the bundle via scripted scenario (dev server must be running)
pnpm eval:taskops

# Export the latest taskops bundle (writes to templates/apps/taskops-helpdesk/)
pnpm template:export taskops-helpdesk

# Overwrite an existing export, pointing at a specific bundle + manifest
pnpm template:export taskops-helpdesk --force --bundle=/tmp/taskops.bundle.json --manifest=./weldr.ownership.yaml

    Template Availability

  • • Templates remain free tier for launch; paid plans can add premium automation later.
  • • Each template ships with ownership metadata so developers know what’s editable immediately.
  • • The /templates page in the web app now spotlights TaskOps Helpdesk with quick-start commands and direct links to the exported assets.

    • Using the Template in the Web App

  • From My Apps → Apps & Chats, click Start from Template to jump straight into the gallery without hunting through navigation. (The empty state shows the same CTA.)
  • On /templates, open “TaskOps Helpdesk” to review summary stats, last-generated timestamp, and the run/export commands.
  • Click Create from Template to seed a new chat; you’ll see an inline toast (“Template applied — opening the chat now”) so it’s obvious the hydration succeeded before the redirect.
  • Run the bundled commands locally (pnpm eval:taskops, pnpm template:export taskops-helpdesk) whenever you need to refresh the assets or regenerate screenshots.
  • Import the DSL (weldr.app.json) into the builder or continue iterating from the auto-created chat; ownership metadata and generated files already match the exported template.

    • Demo Readiness Checklist

  • • [ ] Hero script rehearsed end-to-end (chat → spec → code → preview).
  • • [ ] Template exporter validated (same assets available to every user).
  • • [ ] Ownership manifest reviewed (notifications provider defaults to Extended for quick editing).
  • • [ ] Preview data seeding + reset command documented.
  • • [ ] GitHub sync demo optional but prepared (export template to repo in <2 minutes).

    • FAQ

    Do customers run the eval/autopilot tooling? No. The self-improvement loop is an internal quality system that keeps capabilities healthy. See docs/internal/automation-roadmap.md if you need those details. Will TaskOps be open-sourced? Most of the template and capabilities will be open source. Proprietary automation scripts stay private until we finalize the licensing plan.