- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add Doist/todoist-cli --skill build-feature -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add Doist/todoist-cli --skill build-feature -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add Doist/todoist-cli --skill build-feature -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add Doist/todoist-cli --skill build-feature -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/Doist/todoist-cli/tree/HEAD/.agents/skills/build-featureDe l'éditeur
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.mdVue d'ensemble
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
Téléchargez .agents/skills/build-feature/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/Doist/todoist-cli.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.