ai-dev-workflow

Orchestrate multi-agent development workflows with session persistence across task phases.

5|2|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/horuz-ai/claude-plugins --skill ai-dev-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-dev-workflow
Source: https://github.com/horuz-ai/claude-plugins/tree/main/plugins/core/skills/ai-dev-workflow
Command: npx skills add https://github.com/horuz-ai/claude-plugins --skill ai-dev-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured workflow system that orchestrates sub-agents to execute development tasks with full state persistence across sessions.

Core Features & Use Cases

  • Task-driven workflow with stages: Task → Explore → Research → Spec → Build → Review → Refactor
  • Session persistence via .tasks/{task-name}/ for continuity
  • Sub-agent coordination and cross-stage information sharing
  • Plan-driven execution with clear handoffs between phases

Quick Start

Start a new task with /task, which creates .tasks/{task-name}/ and supporting files. Then follow with /explore, /research, /spec, /build, /review, and /refactor as the task progresses. Status updates are written to status.md.

Frequently Asked Questions about ai-dev-workflow

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

FAQPage Schema
How do I coordinate multiple AI agents working on the same development task?

Multi-agent coordination uses a structured workflow system that manages sub-agent communication and state across sequential phases: Task, Explore, Research, Spec, Build, Review, and Refactor. Each phase creates persistent files in `.tasks/{task-name}/` so agents can hand off work with full context, enabling cross-agent collaboration without losing state between sessions.

Can I maintain workflow state and session persistence across development phases?

Yes. The workflow creates a per-task directory structure with dedicated files for each phase (task.md, explore.md, research.md, spec.md, review.md, refactor.md) and a status.md log. This persists all decisions, findings, and progress across sessions so you can pause and resume work without losing context.

What's the best way to structure multi-stage development tasks with clear handoffs between phases?

Start with `/task` to initialize `.tasks/{task-name}/`, then progress sequentially through `/explore`, `/research`, `/spec`, `/build`, `/review`, and `/refactor`. Each command writes outputs to its phase file and updates status.md, creating clear checkpoints and enabling plan-mode decision points between phases.

How do I track progress and decisions across a complex development workflow?

Status updates and activity logging write to status.md within the task directory, creating an audit trail of decisions and phase transitions. Each phase generates its own output file, so you can review what happened at each stage and trace dependencies across the entire workflow.

Do I need to manage agent communication manually, or does the workflow handle it automatically?

The workflow manages sub-agent communication and state automatically. Phase-specific files and shared task context enable agents to pass information forward without manual coordination, reducing handoff friction and ensuring each stage has the context it needs.

Related Skills