team-shinchan:micro-execute

Name: team-shinchan:micro-execute
Availability: InStock
Author: Seokan

Execute micro-tasks with enforced spec and code-quality reviews.

8|2|Updated Feb 3, 2026

Search Tags:#workflow #verification #subagents #code-review #micro-tasks #progress-tracking #task-automation

Ready to run

npx skills add https://github.com/seokan-jeong/team-shinchan --skill team-shinchan-micro-execute

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-shinchan:micro-execute
Source: https://github.com/seokan-jeong/team-shinchan/tree/main/skills/micro-execute
Command: npx skills add https://github.com/seokan-jeong/team-shinchan --skill team-shinchan-micro-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces small, time-boxed implementation steps with mandatory spec and code-quality reviews to prevent drift, hallucination, and low-quality commits during AI-assisted development.

Core Features & Use Cases

Micro-task Planner: Breaks phases or a freeform task into 2-3 minute concrete tasks with exact file paths, steps, and verification commands.
Sequential Implement-Review Loop: For each task, dispatches an implementer subagent, a spec compliance reviewer, and then a code quality reviewer with defined retry limits.
Evidence-Driven Verification: Requires running verification commands, capturing outputs, updating PROGRESS.md, and a final integration review across all micro-tasks.
Use Case: Ideal for safely turning a high-level PROGRESS.md plan into incremental, reviewable code changes in CI-driven engineering workflows.

Quick Start

Run the micro-execute skill on a PROGRESS.md plan to execute each 2-3 minute micro-task with spec and quality reviews.

Frequently Asked Questions about team-shinchan:micro-execute

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

FAQPage Schema

How do I enforce small micro-tasks and code reviews during AI-assisted development?▼

To enforce micro-tasks and code reviews during AI-assisted development, break work into 2-3 minute steps with exact file paths and sequential implement-review cycles. This approach uses fresh subagents per task to prevent drift and low-quality commits.

What is the best way to execute a PROGRESS.md plan into incremental code changes?▼

Executing a PROGRESS.md plan into incremental code changes requires generating explicit micro-task plans, dispatching implementer subagents, and running verification commands for each task. Spec compliance and code quality reviewers with retry limits ensure reliable, reviewable outputs.

How does two-stage subagent review work for micro-task automation?▼

Two-stage subagent review for micro-task automation works by dispatching a spec compliance reviewer followed by a code quality reviewer for each task. Both stages operate with defined retry limits to prevent hallucination and ensure quality before moving to the next task.

Can I use sequential implement-review loops for CI-driven engineering workflows?▼

Yes, you can use sequential implement-review loops for CI-driven engineering workflows. This process breaks phases into 2-3 minute concrete tasks, requires capturing verification command outputs, and concludes with a final integration review across all micro-tasks.

Why does AI-assisted coding drift from project specifications during long sessions?▼

AI-assisted coding drifts from project specifications due to unmanaged context expansion. Preventing drift requires time-boxed implementation steps, mandatory spec compliance reviews, and fresh subagents per micro-task to maintain strict alignment with the original plan.

What are the limitations of using micro-task execution for software development?▼

Limitations of micro-task execution include the need to define exact file paths, verification commands, and explicit plans upfront. It requires overhead for small phases and is constrained by defined retry limits for spec and quality reviewers during the implement-review cycle.