execute-parent-task

Orchestrates parent tasks by decomposing them into subtasks and executing continuous N-step agent loops.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large development tasks often fail when handled in a single pass: specs get skipped, sub-agents hallucinate, coding guidelines are ignored, and work is left uncommitted. This Skill enforces a disciplined, multi-phase orchestration loop that plans, delegates, verifies, and ships complex tasks autonomously. ## Core Features & Use Cases - Spec-First Decomposition: Writes a detailed implementation spec into .ai-memory/plans/pending/ and breaks it into focused subtask files before any code is written. - N-Step Continuous Loop: Runs a configurable number of steps (default N=130), splitting the run between spec writing and execution with strict coding guideline enforcement. - Sub-Agent Management: Spawns lean, task-focused sub-agents, kills and rolls back failing ones, and enforces a 3-strike failure rule with logging. - Guardrails & Bans: Prohibits test running, build checking, per-file commits, and rapid CI/CD polling, deferring verification to CI/CD pipelines. - Use Case: Hand a large feature request (e.g., implementing a new standard UI alongside an existing modern UI) to the agent, which writes the spec, decomposes it into subtasks, executes them under strict naming/error-handling rules, and finishes with a single atomic commit and push. ## Quick Start Ask the agent to execute the parent task for your feature request using the execute-parent-task workflow and let it plan, decompose, and implement it end to end.

Frequently Asked Questions about execute-parent-task

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

FAQPage Schema
How do I break a large coding task into subtasks for an AI agent?

Write a detailed implementation spec into .ai-memory/plans/pending/ first, then split it into focused subtask files under .ai-memory/plans/subtasks/. Each subtask should contain lean, domain-focused instructions with strictly relative git paths so sub-agents can execute independently.

How does the N-step continuous loop work in this workflow?

The loop runs a configurable number of steps (default N=130). The first half is dedicated to spec writing and task decomposition, and the second half executes the created subtasks while enforcing coding guidelines and error management rules.

Can I run tests or builds during the execution loop?

No. Test running, build checking, and background runner scripts are totally banned during routine execution turns. All build and test verification is deferred to the remote CI/CD pipeline, which is monitored via GitMap Pipeline-AI with ETA-based waiting.

What happens when a sub-agent fails or produces bad code?

The orchestrator kills the failing sub-agent immediately, rolls back its dirty working tree, and spawns a new one. A 3-strike rule applies, and failed tasks are logged to last-failure.md for tracking.

What coding conventions does this workflow enforce?

It enforces boolean names starting only with is or has, bans negative booleans and generic names like temp or data, limits functions to 15 lines, requires domain-specific AppError types, PascalCase acronyms, and behavior-driven test names.

How are commits handled at the end of a task run?

All modified files, plans, and memory records are staged together and committed in a single atomic conventional commit, then pushed to the remote branch. Per-file commits are strictly forbidden to keep history clean and avoid sub-agent lock collisions.