content: Launch post — Run Recurring Documentation Checks with Schedule Triggers

[frances720]

Feature

Promptless now supports schedule triggers — write standing instructions once, set a cron schedule, and Promptless runs a documentation review at each matching time without needing an inbound code event.

Entries considered this run

Window: 2026-08-10 → 2026-08-17 (7 days). 5 commits, 5 entries considered, 2 qualified.

#	Entry	Decision	Reason
1	GitLab MR comment 👀 acknowledgment — Adds a 👀 reaction to GitLab MR comment mentions (commit a30968d, PR #4501)	SKIP	Minor acknowledgment polish; doesn't unlock a new workflow
2	Run documentation checks on a schedule — New schedule trigger type: run standing instructions on a repeating cron schedule (commit def75a3, PR #4505)	QUALIFIES	New trigger type that enables proactive, event-free documentation audits — a genuinely new class of workflows
3	CI failures as a distinct "CI failed" event — CI failures now show as their own event in the suggestion timeline, separate from human feedback items (commit d692a8f)	SKIP	UI clarity improvement; doesn't unlock a new use case
4	GitLab inline citation comments — Citations post as diff-positioned discussion threads on GitLab MRs (commit eca7d1f, PR #4514)	QUALIFIES	Meaningful new UX for GitLab users: reviewers can see citation context in GitLab without switching to the dashboard
5	Research breakdown KB inline + delegated research attribution — Research breakdown shows KB reads in sequence and labels delegated subagent research (commit 730cb63, PR #4528)	SKIP	Display polish to an existing panel; doesn't unlock a new workflow

Covered entry (full text)

Run documentation checks on a schedule: Promptless now supports schedule triggers—run standing instructions on a repeating cron schedule, at most once an hour, in the timezone you pick (for example, a Monday-morning check that the changelog and release-notes page still agree). See Schedule triggers.

Source: commit def75a3.

PR(s) researched

• Promptless/promptless#4505 — Schedule triggers (merged 2026-08-10)
• Docs PR Document schedule (cron) triggers #840 — Document schedule (cron) triggers

File

src/content/blog/product-updates/schedule-triggers.mdx

AI-generated draft — needs human review before publishing.

---

Generated by Claude Code

[promptless]

Documentation review — schedule triggers launch post (automated docs-specialist review; the merge decision stays with you)

Reviewed the one added file, src/content/blog/product-updates/schedule-triggers.mdx, against source and against this collection's conventions. Verdict: approve — accurate, on-style, and convention-compliant.

Correctness against source (verified, not from memory). Every behavioral claim checks out against the backing feature (Promptless/promptless#4505) and its tests, and against the linked docs page:

• Cron + optional timezone + free-text standing instructions, dispatched on a clock — confirmed (ScheduleMatchClause / ScheduleTriggerConfig).
• "Runs at most once an hour" — confirmed (MINIMUM_SCHEDULE_INTERVAL = 1h, validated by sampling real occurrences; sub-hourly expressions like */5 * * * * are rejected). Your wording ("at most once an hour") is exactly right and avoids overclaiming.
• Five-field cron only; six-field and @daily shorthand rejected — confirmed.
• In-flight run → next occurrence skipped, not queued; missed occurrences skipped, not backfilled — both confirmed in code and tests.
• Timezone optional IANA name, defaults UTC, holds wall-clock across DST — confirmed (spring-forward/fall-back tests).
• Quiet finish (no suggestion, no notification) when nothing needs changing — confirmed; matches the docs page's own framing.
• YAML shape (trigger_type: schedule, cron+timezone inside a match clause, top-level instructions, multiple clauses = multiple cadences) — confirmed against the model, JSON schema, and yaml-spec; your example matches the docs verbatim.
• Runs against active doc collections and flows through normal notification/publishing policies — confirmed (shared gating dispatch path).

Doc quality & style. Frontmatter, imports (BlogNewsletterCTA, BlogRequestDemo both exist), sentence-case headings, second-person voice, and problem→what-it-does→who-benefits→how structure all match the established product-updates posts. The internal link /docs/connect/triggers/schedule resolves to the shipped page slug. Serves the scale-up/enterprise docs-team and DevRel personas well: clear problem framing, a copy-pasteable YAML example, and a dashboard walkthrough.

Two non-blocking FYIs (no change required — your wording is already accurate; noting only because I checked them):

• "finishes quietly … no suggestion and no notification" is enforced by the agent's standing instructions rather than a hard code guard. This matches the docs page's phrasing, so it's consistent; just be aware it's behavioral rather than a mechanical guarantee.
• "run the same instructions on multiple cadences by adding more match clauses" is correct. One edge case not worth surfacing in a launch post: if two clauses of the same trigger land in the same sweep window they collapse to a single run (newest wins). Your example (Mon vs. Thu) never collides, so nothing to change.

Approving. Nice, tight post.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
promptless-docs	Ready	Preview	Aug 17, 2026 2:57pm