# Workflow Orchestration

> Disciplined task execution with planning, verification, and self-improvement loops. Use when starting non-trivial tasks (3+ steps), fixing bugs, building features, refactoring code, or when rigorous execution with quality gates is needed. Includes subagent delegation, lessons tracking, and staff-engineer-level verification.

- Skill: `iwuchukwudivine/workflow-orchestration` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds@latest add iwuchukwudivine/workflow-orchestration`
- Raw SKILL.md: https://api.skillmd.com/api/skills/iwuchukwudivine/workflow-orchestration/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- License: MIT
- Author: IwuchukwuDivine (https://skillmd.com/u/iwuchukwudivine)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/iwuchukwudivine/workflow-orchestration

---


# Workflow Orchestration

Apply these practices for disciplined, high-quality task execution.

## Quick Reference

| Practice       | When to Apply                                     |
| -------------- | ------------------------------------------------- |
| Plan Mode      | Any task with 3+ steps or architectural decisions |
| Subagents      | Research, exploration, parallel analysis          |
| Lessons        | After ANY user correction                         |
| Verification   | Before marking any task complete                  |
| Elegance Check | Non-trivial changes only                          |

## 1. Plan Mode Default

- Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)
- If something goes sideways, STOP and re-plan immediately
- Use plan mode for verification steps, not just building
- Write detailed specs upfront to reduce ambiguity

## 2. Subagent Strategy

Keep the main context window clean:

- Offload research, exploration, and parallel analysis to subagents
- For complex problems, throw more compute at it via subagents
- One task per subagent for focused execution

## 3. Self-Improvement Loop

After ANY correction from the user:

1. Update `tasks/lessons.md` with the pattern
2. Write rules that prevent the same mistake
3. Review lessons at session start

See [references/lessons-format.md](references/lessons-format.md) for the template.

## 4. Verification Before Done

- Never mark a task complete without proving it works
- Diff behavior between main and your changes when relevant
- Ask yourself: "Would a staff engineer approve this?"
- Run tests, check logs, demonstrate corrections

## 5. Demand Elegance (Balanced)

- For non-trivial changes: pause and ask "is there a more elegant way?"
- If a fix feels hacky: "Knowing everything I know now, implement the elegant solution"
- Skip this for simple, obvious fixes—don't over-engineer

## 6. Autonomous Bug Fixing

- When given a bug report: Just fix it. Don't ask for hand-holding
- Point at logs, errors, failing tests—then resolve them
- Zero context switching required from the user

## Task Management Protocol

1. **Plan First**: Write plan to `tasks/todo.md` with checkable items
2. **Verify Plan**: Check in before starting implementation
3. **Track Progress**: Mark items complete as you go
4. **Explain Changes**: High-level summary at each step
5. **Document Results**: Add review to `tasks/todo.md`
6. **Capture Lessons**: Update `tasks/lessons.md` after corrections

See [references/task-templates.md](references/task-templates.md) for file templates.

## Core Principles

- **Simplicity First**: Make every change as simple as possible
- **No Laziness**: Find root causes. No temporary fixes. Senior developer standards
- **Minimal Impact**: Only touch what's necessary. Avoid introducing bugs