taskfile

name	taskfile
description	Taskfile discovery and execution — use before running any project command when the project may use go-task. Invoke when the user asks: "run the tests", "build the project", "start the dev server", "run lint/fmt/bench/ci/clean", "what task should I run for X", "task [name] is failing", "how do I pass args to task", or when a Taskfile.yaml/Taskfile.dist.yaml is present. Always read the Taskfile before guessing ecosystem commands — prevents npm-vs-yarn mistakes, wrong test wrappers (cargo test vs nextest), and missed env vars or dep chains. Covers task field inspection, nested includes, CLI_ARGS passthrough, and manual fallback when task is unavailable. Use taskfile-authoring when creating or updating Taskfiles.
version	2.1.0
tags	["taskfile","task","go-task","build","dev-workflow","automation"]
execution	{"plan":{"allow":["inspect Taskfiles","inspect included Taskfiles","map task names to user intent","infer manual fallback commands from Taskfile definitions"],"deny":["execute project commands","install tooling"]},"code":{"allow":["execute tasks via the task runner","reproduce task commands manually when task runner is unavailable","add or update Taskfiles (apply taskfile-authoring rules)"]}}

Taskfile: Discovery, Inspection, and Execution

The Core Idea

Taskfile is the project's ecosystem-agnostic command vocabulary.