Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

todo

Étoiles5

Forks0

Mis à jour21 juillet 2026 à 20:31

Use when the user asks to "ideate on an idea", "refine an idea", "brainstorm", "write a spec", or "create a specification". Idea -> spec authoring that precedes tracked work; all TODO tracker actions (create/claim/implement/complete/defer/batch/...) belong to the `todo-db` skill.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

joeharris76

joeharris76/BenchBox

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

4 fichiers

SKILL.md

readonly

name	todo
description	Use when the user asks to "ideate on an idea", "refine an idea", "brainstorm", "write a spec", or "create a specification". Idea -> spec authoring that precedes tracked work; all TODO tracker actions (create/claim/implement/complete/defer/batch/...) belong to the `todo-db` skill.
version	0.7.0
tools	Bash, Read, Edit, Write, Task

Idea → Spec Authoring

This is the pre-tracker thinking workflow. Route to ideate or spec and read the file in the Read column before acting; all tracker state belongs to todo-db, never this skill.

Actions

Action	Trigger	Read
`ideate`	ideate/refine/brainstorm	`references/ideate.md`
`spec`	write/create a specification	`references/spec.md`
`help`	help/list actions	this table

Handoff

Once the spec is agreed, use todo-db: todo create (or its create-from-spec flow). Do not write TODO state to files; the tracker database is the record.

Plus depuis ce dépôt

même dépôt

review-protocol

joeharris76/BenchBox

Shared protocol for review-shaped actions, authorization scope, defect routing, L2 audit handling, and local-only capture.

2026-07-225

benchbox-workflow

joeharris76/BenchBox

Use when the user asks to "test TPC-H", "check compliance", "review architecture", "run quality checks", "check binaries", "test dialect translation", "compare implementations", "run live platform tests", or "plan and execute" a benchmark feature.

2026-07-215

code

joeharris76/BenchBox

Use for "commit code", "review code", "fix lint/type error", "improve performance", "compare code", "shrink code", "generate spec from code", "investigate code", "debug an error", "triage a bug", "iterate to green", or "create handoff prompt".

2026-07-215

docs

joeharris76/BenchBox

Use when the user asks to "create documentation", "build docs", "review docs", "compare documents", "compress docs", "adversarial review docs", or "commit docs".

2026-07-215

skill-sync

joeharris76/BenchBox

Use when the user asks to "sync skills", "set up skill-sync", "check skill status", "validate skills", "preview skill changes", "diagnose skills", "pin a skill", "unpin a skill", "prune skills", or "promote skill changes".

2026-07-215

test

joeharris76/BenchBox

Use when the user asks to "run tests", "create tests", "fix failing test", "add test coverage", "fix slow tests", or "commit test changes".

2026-07-215

name	todo
description	Use when the user asks to "ideate on an idea", "refine an idea", "brainstorm", "write a spec", or "create a specification". Idea -> spec authoring that precedes tracked work; all TODO tracker actions (create/claim/implement/complete/defer/batch/...) belong to the `todo-db` skill.
version	0.7.0
tools	Bash, Read, Edit, Write, Task

Idea → Spec Authoring

This is the pre-tracker thinking workflow. Route to ideate or spec and read the file in the Read column before acting; all tracker state belongs to todo-db, never this skill.

Actions

Action	Trigger	Read
`ideate`	ideate/refine/brainstorm	`references/ideate.md`
`spec`	write/create a specification	`references/spec.md`
`help`	help/list actions	this table

Handoff

Once the spec is agreed, use todo-db: todo create (or its create-from-spec flow). Do not write TODO state to files; the tracker database is the record.