Solo to Team includes four skills, a registration line template, instructions, and two anonymized case studies. It requires registering each task as "pending receipt" before dispatch, specifying who is working on it, who will receive it, and who will check in at the deadline; receiving deliverables and completing acceptance are recorded separately, and acceptance must be backed by evidence matching the current version. The author states that they have installed and invoked these skills by name in tools such as Codex, WorkBuddy, DeepSeek Harness, Cursor, CodeBuddy, Kimi Work, and Qianwen Office, but validation with Claude Code has not yet been completed.
Why it matters Codifying the rule that "dispatched tasks must be received and claims of completion require evidence" allows the same methodology to be used across different agent tools.
Stars 844 (+61 / 24h)
Reasoning
- 61 new stars in 24 hours (reflects attention only); MIT license
- The README is restrained regarding validation scope: it specifies which hosts have been validated and to what extent
Usage
- Refer to the "How to install and invoke on each host" section in the README to find instructions for your tool; even without installing the tools, you can first practice dispatching, receiving, and verifying using the registration line template in a table.
Risks
- The documentation status is a v0.9 draft and will change before official release; the skills do not include timed reminders, so deadline checks rely on humans or the host's scheduling features.