Skip to main content
You have written three commands. An agent working in this repository has no idea they exist. Except it does, because they are real subcommands and the CLI can list them:
Thirty-three ship with the CLI; three are yours. They appear in the same list, with their flags, types, defaults and allowed values — because that is what task() declared.
Nothing generated that. There is no manifest to keep in sync, because the command is the description.

​
The file that makes it land

AGENTS.md ships in the repository. Read it:
It is short, and it is mostly a pointer: run aspect describe, here is what each command answers, run these before handing work back. It can be short because it points at aspect describe — the flags and defaults are already in the tool, so the document does not carry them and cannot go stale against them. That is the file you would write for your own repository.

​
The part worth noticing

Ask your agent to write a new command — something small, like listing packages with no tests. It reads the three existing tasks as examples, sees the conventions you have been reading all session (task(), typed args, printing to stdout), and writes one. Then aspect describe lists that too. That is the claim this course has been making: discoverability is not a feature you add at the end, it is what you get for declaring the command properly in the first place.
A file under .aspect/ that does not load takes every task down with it, and aspect describe too — the CLI reads them all before it runs anything. The error names the file and line. If you need describe working while you debug, move the new file aside.
If you are reading this without an agent, the four .aspect/*.axl files are the examples it would have read.

​
Where this goes

Everything you built ran locally, offline, with no account:
  • The AXL you actually need. What you write next is for your repository, not this one. Point your agent at the Aspect docs MCP server and it can search the CLI reference, the AXL reference and this course while it writes. The anonymous endpoint needs no account.
  • CI. The same tasks post status checks, PR comments and inline lint findings when you connect an account. Nothing you wrote changes. See reporting into CI.
  • Housekeeping. aspect gc and aspect worktree are AXL tasks too — they improve the work around the build rather than the build itself. See reclaim disk and memory.
You never typed AXL from a tutorial. You read it, ran it, and changed one thing at a time — and the last of those changes was written by something else.