using-workflow

Orchestrate six-phase development workflows with mandatory approvals at Phases 3 and 5.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tasai-lab/fractal-dev-workflow --skill using-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-workflow
Source: https://github.com/tasai-lab/fractal-dev-workflow/tree/main/skills/using-workflow
Command: npx skills add https://github.com/tasai-lab/fractal-dev-workflow --skill using-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, automated orchestration for six-phase development workflows, enforcing critical approvals and consistent transitions between phases to reduce chaos and miscommunication.

Core Features & Use Cases

  • Orchestrates Phase 1 through Phase 6 with clear handoffs and status tracking.
  • Enforces mandatory approvals at Phases 3 (Planning) and 5 (Implementation).
  • Integrates with sub-skills like questioning, investigation, planning, codex-review, and implementation to guide teams from task inquiry to completion.

Quick Start

Describe your development task and invoke the dev-workflow orchestrator to begin the six-phase process.

Frequently Asked Questions about using-workflow

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

FAQPage Schema
How do I automate a structured software development workflow with mandatory approvals?

Automate a structured development workflow by invoking a central orchestrator to drive six phases, enforcing mandatory approvals at the planning and implementation stages to reduce chaos and miscommunication.

What is a six-phase dev workflow and how does it handle phase transitions?

A six-phase dev workflow guides teams from task inquiry to completion. It handles phase transitions through a central orchestrator that integrates sub-skills for questioning, investigation, planning, review, and implementation, tracking progress via a local JSON state file.

How do I enforce mandatory approval steps in an automated DevOps planning cycle?

Enforce mandatory approvals in a DevOps planning cycle by configuring the development workflow orchestrator to halt for user approval at Phase 3 (Planning) and Phase 5 (Implementation) before proceeding.

Can I use this workflow orchestration for investigations and coding efforts instead of just task planning?

Yes, you can use this workflow orchestration for investigations and coding efforts. It is applicable to software teams needing structured planning, review, and implementation cycles across diverse development tasks.

How do I track progress and state across multiple development workflow phases?

Track progress across multiple development workflow phases using a local JSON state file. The orchestrator automatically updates this file to maintain consistent handoffs and status tracking throughout the six phases.

What are the limitations of using a local JSON state file for workflow orchestration?

Using a local JSON state file for workflow orchestration limits state accessibility to the local environment, meaning distributed teams cannot share a single synchronization source without manual file transfers.