do

Orchestrate phased implementation plans with subagent verification and commit control.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/dwaynimay/IoTProject --skill do-dwaynimay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do
Source: https://github.com/dwaynimay/IoTProject/tree/main/.agents/skills/do
Command: npx skills add https://github.com/dwaynimay/IoTProject --skill do-dwaynimay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you reliably execute a multi-phase implementation plan by coordinating specialist subagents and enforcing evidence-based progress, verification, and quality checks.

Core Features & Use Cases

  • Phased orchestration: Breaks work into ordered phases and dispatches fresh subagents where context is large or unclear.
  • Evidence requirements: Ensures each subagent reports completion with proof (commands run, outputs produced, and files changed) before moving forward.
  • Built-in guardrails: Adds verification, anti-pattern checks, and code quality review, and only commits after verification passes with explicit approval.
  • Use case: Turn an AI-generated implementation plan into a safely executed workflow for a codebase change, such as updating IoTProject firmware or server logic, without skipping validation.

Quick Start

Ask your AI to run the do plan for your previously created plan and require each phase to include verification evidence before proceeding.

Frequently Asked Questions about do

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

FAQPage Schema
How do I execute a multi-phase implementation plan with verified subagents?

Phased orchestration coordinates specialist subagents to execute implementation plans, requiring completion evidence like command outputs and changed files before advancing to the next phase.

What is the best way to prevent bad commits during automated codebase changes?

Built-in guardrails block commits until verification succeeds, enforcing anti-pattern checks, code quality reviews, and explicit approval before allowing changes to be committed.

How do I orchestrate subagents for deterministic plan execution?

Subagent orchestration dispatches fresh subagents where context is unclear, utilizing checklists and documentation-accurate copying to ensure deterministic, evidence-backed progress across handoffs.

Does subagent orchestration work for infrastructure changes like firmware updates?

Subagent orchestration applies to coding or infrastructure changes, safely executing workflows for codebase updates like IoTProject firmware or server logic without skipping validation.

When do I need evidence-backed progress checks for code quality verification?

Evidence-backed progress checks are needed when executing multi-phase plans with large context, ensuring each subagent reports proof of completion before moving forward.

Why does plan execution fail without anti-pattern checks and code quality review?

Without anti-pattern checks and code quality review, phased execution lacks necessary guardrails, allowing unverified changes to bypass validation and potentially commit problematic code.