iterative-work

Implement a single planned task from a ticket document with validation and review.

7|3|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/Aidbox/aidbox-hl7v2-example --skill iterative-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iterative-work
Source: https://github.com/Aidbox/aidbox-hl7v2-example/tree/main/.claude/skills/iterative-work
Command: npx skills add https://github.com/Aidbox/aidbox-hl7v2-example --skill iterative-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a disciplined, single-task workflow for implementing a feature or fixing a bug from a ticket that includes a step-by-step plan, preventing multitasking and ensuring each change is validated and reviewed before moving on.

Core Features & Use Cases

  • Single-task focus: Always work on one checkbox-defined task at a time to reduce context switching and merge conflicts.
  • Built-in validation loop: Run validation and testing commands after completing task checkboxes and before requesting reviews.
  • Independent review orchestration: Spawn an external reviewer agent to produce an impartial code review and address all findings before final validation.
  • Use Case: Implement a small bug fix from a feature ticket, mark sub-tasks as completed, run the test suite, obtain a reviewer report, fix issues, and re-run tests until green.

Quick Start

Use the iterative-work skill to implement the next unchecked task in the ticket document, mark it done, run the specified validation commands, spawn a reviewer, and address all review findings before proceeding.

Frequently Asked Questions about iterative-work

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

FAQPage Schema
How do I implement a single task from a ticket without losing focus on the overall plan?

To implement a single task from a ticket, follow its checkbox-driven plan to enforce single-task focus, preventing multitasking and reducing merge conflicts. The workflow ensures each change is validated and reviewed before moving on to the next step.

What is the best way to automate code review and validation for step-by-step bug fixes?

Automate code review and validation by running specified testing commands after completing ticket checkboxes, then spawning an independent reviewer agent. The workflow iterates until tests pass and all review findings are addressed before proceeding.

How does checkbox-driven task orchestration work for software development workflows?

Checkbox-driven task orchestration works by executing one planned task at a time from a ticket document, marking checkboxes as completed, running validation commands, and obtaining an impartial code review before final validation.

Does this iterative workflow require a specific testing framework to run validation commands?

No specific testing framework is required. The workflow runs the explicit validation and testing commands provided within your ticket document, applying to any software development or bug-fix environment that uses step-by-step implementation plans.

Can I use this for large feature implementations or is it limited to small bug fixes?

You can use this for both large features and small bug fixes, provided the ticket document contains a step-by-step implementation plan. The strict single-task focus ensures reliable delivery regardless of the feature scope.