task-think

Orchestrate multi-phase repository implementation workflows with persistent .ai task artifacts.

4|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/lutit/UzbekGramDesktop --skill task-think-lutit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-think
Source: https://github.com/lutit/UzbekGramDesktop/tree/main/.agents/skills/task-think
Command: npx skills add https://github.com/lutit/UzbekGramDesktop --skill task-think-lutit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It coordinates a full implementation workflow for a codebase so a single prompt can gather context, plan work, implement changes, verify builds, and review results without losing track of artifacts.

Core Features & Use Cases

  • Context Gathering: Collects relevant source files, conventions, and reference patterns before coding.
  • Planning and Assessment: Produces a detailed phased plan and refines it against the actual codebase.
  • Implementation Handoffs: Splits work into bounded phases with clear write sets and review gates.
  • Use Case: Use it when you want an AI to manage a repository task from analysis through build verification and code review with persistent task logs.

Quick Start

Use the task-think skill to coordinate a repository change with subagents and persistent .ai task artifacts.

Frequently Asked Questions about task-think

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

FAQPage Schema
How do I orchestrate multi-phase code implementation with subagents?

Multi-phase code implementation is orchestrated by splitting work into bounded phases with clear write sets and review gates, using subagent-based execution for context gathering, planning, implementation, build verification, and code review loops.

What is task orchestration for repository workflows?

Task orchestration for repository workflows coordinates a full implementation cycle from context gathering to build verification, keeping work organized in persistent .ai project logs and task artifacts with phase handoffs and progress tracking.

How do I plan and verify code changes across multiple implementation phases?

Code changes across multiple phases are planned and verified by producing a detailed phased plan, refining it against the actual codebase, implementing changes via handoffs, and running build verification and review loops with retry handling.

Can I use subagents to manage build verification and code review loops?

Yes, subagents manage build verification and code review loops by executing bounded implementation phases, tracking progress in persistent task artifacts, and handling retries during the repository workflow handoffs.

When do I need persistent task artifacts for AI repository tasks?

Persistent task artifacts are needed when running first-time or follow-up repository tasks that require context gathering, phase handoffs, and progress tracking to prevent losing track of implementation work across multiple subagent execution cycles.

What are the limitations of orchestrating repository tasks with subagents?

Orchestrating repository tasks with subagents requires persistent .ai project logs and phase handoffs to function correctly, meaning workflows lacking clear write sets, review gates, or bounded implementation phases may lose track of task artifacts.