Use when operating the Horadus repo through task, sprint, triage, or branch-start workflows; prefer the `horadus` CLI over ad hoc markdown parsing or one-off shell helpers when an equivalent command exists.
Use this skill for repo workflow operations in this project.
Implementation note:
tools/horadus/python/horadus_cli/.horadus entrypoint points directly at the tooling package.tools/horadus/python/horadus_app_cli_runtime.py;
the tooling package should not import business-app modules directly.horadus over direct rg/awk/markdown scraping when the CLI covers
the workflow.--format json for agent use.--dry-run before any branch-creating command.AGENTS.md for canonical workflow policy, completion rules, and merge/review semantics.git / gh commands only when the Horadus CLI does not expose the
needed workflow step yet, or when the CLI explicitly tells you a manual
recovery step is required.horadus tasks record-frictionuv run --no-sync horadus tasks preflightuv run --no-sync horadus tasks safe-start TASK-XXX --name short-nameuv run --no-sync horadus tasks context-pack TASK-XXXmake agent-checkuv run --no-sync horadus tasks local-review --format jsonuv run --no-sync horadus tasks local-gate --fulluv run --no-sync horadus tasks lifecycle TASK-XXX --strictuv run --no-sync horadus tasks finish TASK-XXXuv run --no-sync horadus tasks record-friction TASK-XXX --command-attempted "..." --fallback-used "..." --friction-type forced_fallback --note "..." --suggested-improvement "..."uv run --no-sync horadus tasks summarize-friction --date YYYY-MM-DDuv run --no-sync horadus tasks list-active --format jsonuv run --no-sync horadus tasks show TASK-XXX --format jsonuv run --no-sync horadus tasks search "query" --format jsonuv run --no-sync horadus tasks eligibility TASK-XXX --format jsonuv run --no-sync horadus tasks start TASK-XXX --name short-name --dry-run --format jsonuv run --no-sync horadus triage collect --lookback-days 14 --format jsonhoradus tasks finish.horadus tasks context-pack TASK-XXX recommends pre-push local review,
follow that guidance. The default/env provider chain already falls through
missing provider CLIs on PATH in repo order. If the first local-review run
hits a provider-specific timeout, auth/config failure, or unreadable output
and you still want local automation, rerun with --allow-provider-fallback;
if the local-review path still remains unusable, request manual review early
rather than waiting for the finish loop.--provider override first, then
HORADUS_LOCAL_REVIEW_PROVIDER from optional local-only .env.harness,
then the repo default claude.AGENTS.md.references/commands.md
or docs/AGENT_RUNBOOK.md.