background-task
GitHub指导在请求/响应循环外添加后台任务(如邮件、清理、定时作业),支持 Celery、Taskiq、Arq、Prefect 等队列,提供定义、入队及调度规范。
Trigger Scenarios
Install
npx skills add vstorm-co/full-stack-ai-agent-template --skill background-task -g -y
SKILL.md
Frontmatter
{
"name": "background-task",
"description": "Add or modify work that runs outside the request\/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic\/cron task. This project's queue is {{ cookiecutter.background_tasks }}."
}
Background Tasks ({{ cookiecutter.background_tasks }})
Tasks live in backend/app/worker/tasks/ (e.g. email_tasks.py, rag_tasks.py, cleanup_tasks.py). The app uses {{ cookiecutter.background_tasks }}. An in-process fallback (worker/background/) exists for trivial cases.
When to use a task vs. inline
- Task: anything slow, retryable, or fire-and-forget — sending email, ingesting/embedding documents, calling slow external APIs, periodic cleanups, materialized-view refreshes.
- Inline: fast, transactional work that the response depends on.
Add a task
-
Define it in
backend/app/worker/tasks/<area>.py: {%- if cookiecutter.use_celery %}from app.worker.celery_app import celery_app @celery_app.task(name="send_welcome_email") def send_welcome_email(user_id: str) -> dict: ...Enqueue:
send_welcome_email.delay(user_id)(or.apply_async(args=[...], countdown=60)). {%- elif cookiecutter.use_taskiq %}from app.worker.taskiq_app import broker @broker.task async def send_welcome_email(user_id: str) -> dict: ...Enqueue:
await send_welcome_email.kiq(user_id). {%- elif cookiecutter.use_arq %}# add the coroutine, then list it in arq_app.WorkerSettings.functions async def send_welcome_email(ctx, user_id: str) -> dict: ...Enqueue:
await request.state.arq_pool.enqueue_job("send_welcome_email", user_id). {%- elif cookiecutter.use_prefect %}from prefect import flow @flow(name="send-welcome-email", log_prints=True) async def send_welcome_email_flow(user_id: str) -> dict: ...Fire-and-forget from a service:
asyncio.create_task(send_welcome_email_flow(user_id)). {%- endif %} -
Call it from a service (not from the route directly) — keep business logic in
services/, enqueue at the end of the unit of work. -
Schedule it (optional): {%- if cookiecutter.use_celery %} add to
beat_scheduleincelery_app.py(runmake celery-beat). {%- elif cookiecutter.use_taskiq %} append toSCHEDULESintasks/schedules.py(runmake taskiq-scheduler). {%- elif cookiecutter.use_arq %} add acron(...)entry toWorkerSettings.cron_jobsinarq_app.py. {%- elif cookiecutter.use_prefect %} register a deployment with aCronSchedule/IntervalScheduleinapp/worker/prefect_app.py. {%- endif %} -
Run / verify: {%- if cookiecutter.use_celery %}
make celery-worker(+make celery-beatfor schedules,make celery-flowerto monitor). {%- elif cookiecutter.use_taskiq %}make taskiq-worker(+make taskiq-schedulerfor schedules). {%- elif cookiecutter.use_arq %} the worker runs in the dev stack (make dev), oruv run --directory backend arq app.worker.arq_app.WorkerSettings. {%- elif cookiecutter.use_prefect %} theprefect-server+prefect-runnerstart withmake dev; watch runs at http://localhost:4200. {%- endif %}
Rules
- Tasks take serializable args (ids, primitives) — not ORM objects or sessions. Re-fetch inside the task with a fresh session.
- Make tasks idempotent where possible (safe to retry).
- Keep heavy imports inside the task function to keep the API import-light.
- See
docs/howto/add-background-task.mdfor the full walkthrough.
Version History
- 0.2.16 Current 2026-07-25 10:05


