with one click
kandev-routines
Schedule recurring work via cron and webhook triggers
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Schedule recurring work via cron and webhook triggers
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Kandev release & versioning conventions — single SemVer across npm, Homebrew, GitHub release. Use when cutting a release, debugging release artifacts, or answering questions about version channels.
Review changed code for quality, security, and architecture compliance. Use after implementing features or before opening PRs.
Diagnose Kandev bugs, running-instance issues, UI/browser failures, and runtime behavior. Use when the user reports unexpected behavior, asks to investigate, asks to add logs/instrumentation, or when a fix needs root-cause evidence before implementing. Triage first, gather evidence safely, then hand off to /fix or /tdd for code changes.
Write and run web E2E tests (Playwright) using TDD — locations, patterns, commands, and debugging.
Ensures UI feature work ships with desktop and mobile parity, responsive behavior, and mobile Playwright E2E coverage. Use when implementing, planning, reviewing, or testing any new feature, page, component, workflow, form, dialog, sidebar, navigation, dashboard, or visual UI change; if work touches frontend or user-facing UI, this skill must run even when user mentions only desktop or says "new feature".
Create a committed implementation plan from a feature spec. Explores the codebase, designs the approach, and produces docs/plans/<feature>/plan.md plus individual task files. Use after writing a spec and before implementing.
| name | kandev-routines |
| description | Schedule recurring work via cron and webhook triggers |
| kandev | {"system":true,"version":"0.42.0","default_for_roles":["ceo"]} |
Routines fire on cron or webhook and create a fresh task each time, assigned to a specific agent. Use them when work needs to happen on a clock (daily standups, weekly reports, hourly health checks).
$KANDEV_CLI kandev routines list
$KANDEV_CLI kandev routines create \
--name "Daily standup" \
--task-title "What did each agent ship today?" \
--task-description "Summarise yesterday's commits and PRs across the team. Post to #engineering." \
--assignee A-ceo \
--cron "0 9 * * MON-FRI" \
--timezone "Europe/Lisbon"
This creates the routine and attaches a cron trigger in one command. The CLI does two API calls under the hood (routine + trigger); the response is the trigger row.
$KANDEV_CLI kandev routines pause --id R-1
$KANDEV_CLI kandev routines resume --id R-1
$KANDEV_CLI kandev routines delete --id R-1
--name — display name; users see this on the Routines page.--task-title — title for every task this routine creates. Supports {{name}} and {{date}} placeholders.--task-description — agent instructions for each fire.--assignee — the agent ID that receives the task. For coordinator work, this is the CEO; for distributed checks, a worker or specialist.--cron — standard 5-field cron expression.tasks create directly.