execute-task

Automate ARF task execution from intake to PR merge.

16|8|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/GliteTech/glite-arf --skill execute-task-glitetech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-task
Source: https://github.com/GliteTech/glite-arf/tree/main/arf/skills/execute-task
Command: npx skills add https://github.com/GliteTech/glite-arf --skill execute-task-glitetech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end ARF task execution from intake to PR merge, reducing manual orchestration and human error.

Core Features & Use Cases

  • End-to-end task orchestration across prestep, task steps, and poststep lifecycles.
  • Spawns subagents for phase-specific skills (research, planning, implementation, and verification) to ensure isolation and traceability.
  • Enforces guardrails: dependency checks, budget considerations, and artifact verification before merging changes to main.

Quick Start

Run a full ARF task through all mandatory stages and merge the final PR to main.

Frequently Asked Questions about execute-task

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

FAQPage Schema
How do I automate ARF task execution from intake to PR merge?

You can automate ARF task execution by orchestrating the entire workflow from intake to PR merge in isolated worktrees. This process enforces strict commit rules, dependency checks, and artifact verification before merging changes to main.

What is the best way to orchestrate decentralized subagents for phase-specific tasks?

Orchestrating decentralized subagents involves spawning isolated agents for planning, implementation, and verification. This approach ensures traceability and meets prestep and poststep lifecycle requirements defined in ARF specifications.

How do prestep and poststep lifecycles work in task orchestration?

Prestep and poststep lifecycles in task orchestration define mandatory phases before and after the main task steps. They enforce guardrails like dependency checks and artifact verification to ensure automated workflow integrity before PR merge.

Can I enforce guardrails and strict commit rules during automated workflow execution?

You can enforce guardrails and strict commit rules during workflow execution by applying automated dependency checks, budget considerations, and artifact verification. These constraints prevent human error and ensure code quality before merging to main.

Does isolated worktree execution support decentralized subagent verification?

Isolated worktree execution supports decentralized subagent verification by spawning phase-specific agents for research and testing. This ensures traceability and prevents cross-contamination of changes before they are merged to the main branch.