do-task
Execute a task through plan, implement, evaluate phases with automatic retry logic until completion
What this skill does
# Task Runner — Plan, Implement, Evaluate You are orchestrating a multi-phase task execution workflow. Follow these phases exactly. ## Setup 1. Parse the task description from: `$ARGUMENTS` 2. Scan the `task-results/` directory for existing folders. Determine the next task number by finding the highest existing number and adding 1. If no folders exist, start at `001`. 3. Generate a task slug from the description: `<NNN>-<short-kebab-case-name>` (e.g., `001-add-user-auth`). The kebab name should be 3-5 words max, derived from the task description. 4. Create the directory: `task-results/<slug>/` 5. Write `task-results/<slug>/request.md` with the original user request. Format: ```markdown # Request <the full task description from $ARGUMENTS> ``` 6. Announce the task: print the task number, slug, and description. ## Phase 1 — Plan Delegate to the **dt-task-planner** subagent with this prompt: > **Task**: <the full task description> > > **Working directory**: <current working directory> > > **Output path**: <full path to task-results/<slug>/plan.md> > > Explore the codebase, analyze the task requirements, and write a detailed implementation plan to the output path. After the planner finishes, read `plan.md` to confirm it was written. Print a brief summary of the plan. ## Phase 2 — Implement Set the attempt counter to 1. Delegate to the **dt-task-implementer** subagent with this prompt: > **Task**: <the full task description> > > **Plan**: <contents of plan.md> > > **Attempt**: <attempt number> > > **Previous evaluation feedback** (if retry): <contents of the most recent evaluation-summary, if this is a retry> > > **Working directory**: <current working directory> > > **Output path**: <full path to implementation-summary.md or implementation-N-summary.md> > > Implement the task according to the plan. Write a summary of all changes to the output path. For the first attempt, the output file is `implementation-summary.md`. For subsequent attempts, use `implementation-<N>-summary.md` (e.g., `implementation-2-summary.md`). After the implementer finishes, read the implementation summary to confirm it was written. Print a brief summary of what was implemented. ## Phase 3 — Evaluate Delegate to the **dt-task-evaluator** subagent with this prompt: > **Task**: <the full task description> > > **Plan**: <contents of plan.md> > > **Implementation summary**: <contents of the latest implementation summary> > > **Attempt**: <attempt number> > > **Working directory**: <current working directory> > > **Output path**: <full path to evaluation-summary.md or evaluation-N-summary.md> > > **Evaluation scripts path**: <full path to task-results/<slug>/> > > Evaluate the implementation. You MUST produce a runnable verification — not just a subjective review. Write the evaluation report to the output path. The report MUST include a clear `## Result` section with either `PASS` or `FAIL`. For the first attempt, the output file is `evaluation-summary.md`. For subsequent attempts, use `evaluation-<N>-summary.md`. After the evaluator finishes, read the evaluation summary. ## Retry Logic 1. Read the evaluation summary and check the `## Result` section. 2. If the result is **PASS**: announce success, print a final summary with the task slug and all generated files. Done. 3. If the result is **FAIL**: - Increment the attempt counter. - Print what failed and that you are retrying. - Go back to **Phase 2** with the evaluation feedback included in the prompt to the implementer. - Continue the loop until the evaluation passes. ## Important Notes - Always use the **dt-task-planner**, **dt-task-implementer**, and **dt-task-evaluator** subagents by name. - Each subagent runs in its own context. Pass all necessary information in the delegation prompt — subagents do not have access to the main conversation. - Write all output files to the `task-results/<slug>/` directory. - The evaluation must always include a runnable check, not just a code review. - If a subagent encounters an error, report it and attempt to recover.
Related in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.