execute-pending-tasks

Orchestrates pending task queues with multi-agent execution loops and git commits.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/alimtvnetwork/ui-prompts-cat --skill execute-pending-tasks-alimtvnetwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-pending-tasks
Source: https://github.com/alimtvnetwork/ui-prompts-cat/tree/main/.agents/skills/execute-pending-tasks
Command: npx skills add https://github.com/alimtvnetwork/ui-prompts-cat --skill execute-pending-tasks-alimtvnetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing a backlog of planned tasks stored as markdown files is error-prone: tasks get skipped, indexes go stale, commits are fragmented, and mistakes repeat. This Skill autonomously executes every pending task in .ai-memory/plans/pending/ in a continuous self-loop until the queue is empty, keeping plans, memory logs, and git history synchronized. ## Core Features & Use Cases - Continuous Multi-Agent Execution: Spawns up to 2 parallel sub-agents with isolated working directories, disjoint file assignments, and a 3-strike rollback rule for failed tasks. - Plan Lifecycle Management: Moves completed plans from pending/ to completed/, consolidates subtasks into single files, and updates all index files in the same turn. - Strict Git & CI/CD Discipline: Enforces atomic grouped commits, immediate pushes, relative-path-only references, and GitMap Pipeline-AI monitoring with dynamic ETA-based waiting instead of rapid polling. - Use Case: A team maintains feature plans as markdown files in .ai-memory/plans/pending/. Invoke this Skill to have the agent read every plan, execute them in sequenced waves (schemas, then services, then UI), record learnings, and push consolidated commits until nothing remains. ## Quick Start Execute all pending tasks in the .ai-memory/plans/pending folder using the execute-pending-tasks workflow and do not stop until the queue is empty.

Frequently Asked Questions about execute-pending-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute all pending tasks in a markdown plan queue automatically?

Invoke this Skill and it reads every file in .ai-memory/plans/pending/, groups them into execution waves, and loops continuously with up to 2 sub-agents until the queue is empty. Each completed plan is moved to plans/completed/ and all indexes are updated.

How does the multi-agent task execution avoid file conflicts?

Sub-agents are limited to 2 concurrent workers and must never touch the same files simultaneously, verified against .ai-memory/01-index.md. Each task gets an isolated directory under .ai-memory/temp-agents/ for state tracking and inter-agent handoff.

What happens when a sub-agent task fails repeatedly?

After 3 consecutive failures, the working tree is rolled back with git checkout for the modified files, the root cause is logged to .ai-memory/plan.md and .ai-memory/issues/, and execution proceeds to the next disjoint task.

Can this workflow run tests or builds to verify changes?

No. Running tests (go test, pytest) or builds (go build, npm run build) is strictly banned during routine execution turns. Verification is deferred to CI/CD, monitored remotely via GitMap Pipeline-AI with ETA-based waiting.

Why does the workflow forbid committing files one at a time?

Per-file commits pollute git history, create sub-agent lock collisions, and break atomic rollback. All modified files must be accumulated and committed together in a single grouped atomic commit, then pushed immediately.