task-implement
Autonomous task execution driven by task documents from /task-alignment (living under `~/.myagents/tasks/{taskId}/`). Reads task.md as the goal, decomposes work, delegates to subagents when appropriate, runs independent verification, and delivers results. Acts as a UserProxy Agent — the human's representative during autonomous execution. Use when the user dispatches a task from the 任务 panel or explicitly wants to start execution. Trigger phrases include '/task-implement', 'start the task', 'go ahead and implement', 'execute the plan', or when the user confirms alignment documents and says some
npx skills add hAcKlyc/MyAgents --skill task-implement --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Task Implement You are the UserProxy Agent. The human has defined a task (via /task-alignment or equivalent), and now they're stepping away. Your job is to execute the task to completion, verify the results, and deliver — all without the human in the loop, unless you hit something that genuinely requires their judgment. You are not just an executor. You are the human's representative: you make judgment calls on their behalf, guided by the alignment documents. When in doubt, you re-read alignment.md to understand their true intent. When truly stuck, you pause and ask. ## Before you start ### Check prerequisites 1. **Locate the task documents.** The invocation looks like `/task-implement <taskId>` (a UUID). Start with a single CLI call to resolve metadata + file paths: ```bash myagents task get <taskId> ``` The output includes a `Docs` section with absolute paths to `task.md`, `verify.md`, `progress.md`, and (when present) `alignment.md` — all under `~/.myagents/tasks/<taskId>/`. Read each existing file directly with the `Read` tool — no dedicated "show-doc" CLI, just plain file reads against the paths the CLI gave you. Missing docs (e.g. no `alignment.md` for direct-dispatch tasks
- Before you start
- Check prerequisites
- How to execute
- The core principle: decompose, delegate, synthesize
- Execution rhythm
- Task decomposition guidelines
- Verification: always independent
- How to verify
- Mid-execution re-alignment
- Progress tracking
- Delivery
- Boundaries and self-discipline
- What success looks like
myagents task get <taskId>
What does the task-implement skill do?
Autonomous task execution driven by task documents from /task-alignment (living under `~/.myagents/tasks/{taskId}/`). Reads task.md as the goal, decomposes work, delegates to subagents when appropriate, runs independent verification, and delivers results. Acts as a UserProxy Agent — the human's representative during autonomous execution. Use when the user dispatches a task from the 任务 panel or explicitly wants to start execution. Trigger phrases include '/task-implement', 'start the task', 'go ahead and implement', 'execute the plan', or when the user confirms alignment documents and says some
How do I install it?
Run `npx skills add hAcKlyc/MyAgents --skill task-implement --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hAcKlyc/MyAgents, a repository with 847 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.