- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Doist/todoist-cli --skill build-feature -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Doist/todoist-cli --skill build-feature -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Doist/todoist-cli --skill build-feature -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Doist/todoist-cli --skill build-feature -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/Doist/todoist-cli/tree/HEAD/.agents/skills/build-featureFrom the publisher
Find the command most like the one you are building and read it with its test: src/commands/task/add.ts for a write that returns an entity, src/commands/today.ts for a list, src/commands/label/delete.ts for a destructive write behind --yes. For a new command or subcommand, add-command is the checklist of every file to touch. Read the rules in AGENTS.md. Done when you can name the file you will copy patterns from.
List what the request leaves open: command and flag names (consistent verbs and flags across entities; see docs/decisions/001-lenient-cli-ergonomics.md), positional argument or named flag, the human and --json output, error codes, --dry-run and --yes, behaviour under a read-only token. Ask the owner all of them at once, each with your recommendation. Don't ask what the code can answer. Done when every decision has an answer.
Write each behaviour as a command and the expected result, for example: "td label create --name work --json calls addLabel with { name: 'work' } and prints the label as JSON". Each becomes a test. Done when a test could pass or fail on every one.
For each behaviour: write its test at the public interface (program.parseAsync(['node', 'td', ...])), see it fail, make it pass, run its test file. Follow write-tests. Done when every behaviour from step 3 has a passing test you saw fail.
Done when each row that applies is handled.
Follow verify. If the feature needs restructuring first, do that as a separate change with refactor.
Builds a new command, flag or behaviour in thin test-first slices, after settling the open decisions with the owner. Use when asked to "add", "build", "implement", "support" or "create" something, suc
---name: build-featuredescription: Builds a new command, flag or behaviour in thin test-first slices, after settling the open decisions with the…---# .agents/skills/build-feature/SKILL.mdOverview
Builds a new command, flag or behaviour in thin test-first slices, after settling the open decisions with the owner. Use when asked to "add", "build", "implement", "support" or "create" something, such as a new command, subcommand or flag.
FAQ
Download .agents/skills/build-feature/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/Doist/todoist-cli.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.