run-task
Execute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task <task>. Uses get_task, update_task, create_task_comment.
Install / Use
npx skills add hashgraph-online/awesome-codex-plugins --skill run-taskInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of run-task
run-task scores 82/100 on our quality scale, 3385th of 4,698 Development & Engineering skills we index.
Its SKILL.md is 8.8 KB long, split into 7 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,075 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so run-task is actively maintained.
- Our last check on 2026-11-07 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-06. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
run-task compared with similar skills
All 4 of these similar skills score higher than run-task; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| run-task (this skill)by hashgraph-online | 82 | 1.1k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install run-task?
- Run
npx skills add hashgraph-online/awesome-codex-plugins --skill run-task. The install tabs above show the steps for each supported agent. - Which AI agents does run-task work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is run-task safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is run-task still maintained?
- The repository was last updated about 2 months ago, so run-task is actively maintained.
Skill content
View source on GitHubname: run-task description: "Execute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task <task>. Uses get_task, update_task, create_task_comment." tags:
- agiflow
- mcp
- execution
- task metadata: mirrors: backend/apis/agiflow-api .../prompts/task.md
Invoked as
/agiflow:run-task. In hosts without slash-prompts, this skill is triggered by matching intent and drives AgiFlow via its MCP tools.
Usage:
/agiflow:run-task <task-slug-or-id>- Execute specific task/agiflow:run-task- List and select from available tasks
Examples:
/agiflow:run-task DXX-2(using slug)/agiflow:run-task 01K8FABMNEJG1XTA9JGHSNFV40(using ID)/agiflow:run-task(interactive selection)
Guardrails
- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
- Keep changes tightly scoped to the requested outcome within the task scope.
- A task represents a single, focused unit of work that can be completed in one session.
If a task slug/id is provided, load it with get_task; otherwise list available tasks with list_tasks for selection.
AgiFlow Project Management Guidelines
Follow the shared AgiFlow project-management guidelines in references/agiflow-agents.md — agent assignment, the task status workflow and transitions, work-unit best practices, and the tags strategy apply to this workflow.
Task Status Workflow
Tasks move through these statuses in order:
Planning → Todo → In Progress → Testing → Review → Done
Exception paths: Blocked (requires human intervention), Cancelled (terminal).
IMPORTANT: Planning Status Guard
This skill ONLY executes tasks in "Todo" or later status. Tasks in "Planning" have NOT been groomed and are NOT ready for execution. Use backlog-grooming to promote Planning tasks to Todo first.
Steps Track these steps as TODOs and complete them one by one.
1. Task Selection & Loading
If task slug/id NOT provided:
- Use
list_tasksMCP tool to show available tasks:- For the ready queue, filter by
status: "Todo"(sorted by priority automatically) - Do NOT pick up tasks in "Planning" status — they have not been groomed yet
- Display: slug, title, priority, assignee, acceptance criteria count
- For the ready queue, filter by
- Ask user to select which task to work on.
- Once user selects, proceed with the selected task slug/id.
If task slug/id IS provided: 4. Use get_task MCP tool with the provided slug/id to retrieve:
- Task: title, description, priority, status, acceptance criteria
- Comments: Previous progress updates and discussions
- Review the task details to understand:
- Complete requirements and deliverables
- Acceptance criteria that must be met
- Any blockers or dependencies noted in comments
5b. PLANNING STATUS GUARD (MANDATORY):
- If task status is "Planning": REFUSE to execute
- Report: "Cannot execute task [SLUG]: still in Planning status. Use backlog-grooming to promote it to Todo first."
- STOP execution — do not proceed
2. Start Task Execution
- If task status is "Todo", use
update_taskMCP tool to set status to "In Progress". - Create a TODO list of acceptance criteria in execution order (use TodoWrite tool).
- Document execution start in task via
update_taskdevInfo:devInfo: { currentSession: "<current-session-id>", startedAt: "<timestamp>" }
3. Implement Task
-
For each acceptance criterion:
- Review the specific requirement
- BEFORE editing any code: Use
vibe-lintMCPget-file-design-pattern(MANDATORY) - Implement the criterion keeping changes minimal and focused
- AFTER editing code: Use
vibe-lintMCPreview-code-change(MANDATORY) - Update task
devInfowith implementation notes:devInfo: { filesChanged: ["path/to/file.ts:42"], testResults: { passed: true, coverage: "85%" }, notes: "Implementation notes here", currentSession: "<session-id>" } - Mark acceptance criterion as checked via
update_task - Update your TODO list (mark criterion as completed)
-
Between acceptance criteria:
- Commit changes with meaningful commit messages
- Run tests to ensure no regressions
- Update task devInfo with progress
4. Testing Phase
-
When ALL acceptance criteria are met:
- Verify all criteria have status checked
- Use
update_taskto move status to "Testing" - Run the full test suite for affected code:
- Unit tests
- Integration tests
- Type checking and lint
-
If tests PASS:
- Update devInfo with passing test results
- Proceed to step 13 (Task Completion)
-
If tests FAIL:
- Increment
retryCountin devInfo:devInfo: { ...existing, retryCount: (existing.retryCount ?? 0) + 1, lastFailureReason: "<description of what failed>" } - If
retryCount >= maxRetries(default maxRetries = 2):- Use
update_taskto move status to "Blocked" - Use
create_task_commentto document the repeated failure and what human intervention is needed - Stop — do not retry
- Use
- If
retryCount < maxRetries:- Use
update_taskto move status back to "Todo" - Use
create_task_commentto document the failure reason - Stop — agent will re-pick from Todo queue on next cycle
- Use
- Increment
5. Task Completion
-
After tests pass, review all files changed (use git diff).
-
Draft a PR description for the task (DO NOT create the PR yet - just draft the text):
- Title format:
[TASK-SLUG] Task title(e.g.,[DXX-2] Add user authentication) - Body should include:
- Task reference and summary
- List of changes made
- Files modified (use
file.ts:42format) - Test results
- Title format:
-
Use
update_taskto set status to "Review" and save draft PR text and commit message:{ status: "Review", devInfo: { ...existing, draftCommitMessage: "feat(auth): add user authentication\n\n- Add login endpoint with session management\n- Add password validation\n- Add unit tests for auth flow", draftPr: { title: "[DXX-2] Add user authentication", body: "## Summary\n\nImplemented user authentication feature.\n\n## Changes\n\n- Added login endpoint\n- Added session management\n\n## Files Modified\n\n- src/auth/login.ts:42\n- src/auth/session.ts:15\n\n## Test Results\n\nAll tests passing." }, finalNotes: "All acceptance criteria met. Files changed: [...]. Tests passing.", completedBy: "<member-id>", totalDuration: "45 minutes" } }Note on draftCommitMessage: Write a conventional commit message that will be used for the final git commit. Format:
type(scope): descriptionwith optional body listing changes. -
Use
create_task_commentto add final summary:- Task scope and goals achieved
- All files created/modified (use
file.ts:42format) - Test coverage and results
- Any follow-up work needed
6. Handle Blockers
- If blocked at any point:
- Use
update_taskto set status to "Blocked" - Use
update_taskto update devInfo with blocker details:devInfo: { ...existing, blockedReason: "<why the task is blocked>", blockedBy: "<memberId or 'system'>" } - Use
create_task_commenton task with blocker information explaining what human intervention is needed
- Use
Reference
- Use
get_taskto review task details before starting - Use
list_task_commentsto see previous progress updates - Use
update_taskto track devInfo and acceptance criteria progress
Integration with Other Tools
- vibe-lint MCP: ALWAYS use before/after editing files for pattern compliance
- Scaffolding MCP: Document scaffolded code in task comments
Common Mistakes to Avoid
- ❌ Starting work without reviewing task details with
get_task - ❌ Not moving task to "In Progress" before starting
- ❌ Skipping vibe-lint MCP validation (MANDATORY for every file)
- ❌ Not tracking devInfo (files changed, tests, session ID)
- ❌ Marking acceptance criteria checked before actually completing them
- ❌ Moving to "Review" without going through "Testing" first
- ❌ Not documenting progress in comments
- ❌ Forgetting to add file references (file.ts:42 format) in final comment
- ❌ Not running tests before moving to "Review"
- ❌ Not committing changes incrementally
- ❌ Moving to "Blocked" without explaining what human intervention is needed
- ❌ Skipping retryCount increment when moving failed task back to "Todo"
- ❌ Starting work on a task in "Planning" status (must be promoted to "Todo" via
backlog-groomingfirst)
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
