do

Orchestrate end-to-end feature tasks from planning to presentation via /do.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/manaporkun/claude-plugins --skill do-manaporkun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do
Source: https://github.com/manaporkun/claude-plugins/tree/main/plugins/task/skills/do
Command: npx skills add https://github.com/manaporkun/claude-plugins --skill do-manaporkun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, copilot, curl, and includes scripts (resource) components.

What problem does it solve?

Plan, coordinate, and automate a feature task from initial planning through external review, implementation, QA, and presentation using a single /do interface.

Core Features & Use Cases

  • End-to-end task orchestration across planning, external analysis, approval, implementation, QC, and presentation.
  • Supports multiple agents (Gemini, Codex, Ollama, Claude Code, Aider, OpenAI-compatible, Copilot) with graceful fallbacks.
  • Plan persistence to .claude/plans and provider/config management via .claude/do-config.json.

Quick Start

Execute /do <task description> to run the full workflow for a feature, bug fix, or task.

Frequently Asked Questions about do

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

FAQPage Schema
How do I automate software feature workflow from planning to presentation?

To automate software feature workflow, you can use a guided /do command to orchestrate end-to-end tasks from initial planning and external review through implementation, QA, and final presentation.

Does end-to-end task orchestration work with multiple external agents?

Yes, end-to-end task orchestration supports multiple external agents including Gemini, Codex, Ollama, Claude Code, Aider, OpenAI-compatible, and Copilot, providing graceful fallbacks during plan execution.

Do I need python3 and copilot to automate code review and task planning?

Yes, you need python3, copilot, and curl configured in your environment to automate code review and task planning, as these are required dependencies for executing the external agent workflows.

Where are automated workflow plans and provider settings persisted?

Automated workflow plans and provider settings are persisted locally, with plans saved to the .claude/plans directory and provider configurations managed via the .claude/do-config.json file.

What is the best way to enforce phased execution for bug fixes and refactoring?

The best way to enforce phased execution for bug fixes and refactoring is applying a structured workflow that separates plan creation, external analysis, implementation, and QC into distinct, persistent stages.