user-guide

Orchestrate a six-phase development workflow with mandatory approvals between Architect, TechLead, Coder, and QA roles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The User Guide clarifies how to operate and troubleshoot the fractal-dev-workflow plugin so AI agents follow a clear, codified process and avoid drifting from the specification.

Core Features & Use Cases

  • Role-specific architecture with Architect, TechLead, Coder, and QA, including their responsibilities, permissions, and invocation methods.
  • Clear workflow commands to start, resume, check status, and cancel workflows.
  • Built-in troubleshooting guidance to maintain context integrity and ensure approvals are obtained at Phase 3 and Phase 5.

Quick Start

Start a new workflow by describing your task with /dev [task description].

Frequently Asked Questions about user-guide

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

FAQPage Schema
How do I start an autonomous development workflow with plugin guidance?

To start an autonomous development workflow, use the command /dev followed by your task description. This initiates a six-phase process with mandatory approvals to prevent scope drift across Architect, TechLead, Coder, and QA roles.

What is the six-phase development workflow and how does it prevent scope drift?

The six-phase development workflow is a structured process guiding AI agents through formal handoffs between Architect, TechLead, Coder, and QA roles. It prevents scope drift by requiring mandatory approvals at Phase 3 and Phase 5 to maintain project alignment.

How do I check status or cancel a workflow-management process if something goes wrong?

You can check status or cancel a workflow-management process using explicit built-in commands. The system provides troubleshooting guidance to maintain context integrity and ensure required approvals are properly obtained during execution.

Do I need a SKILL.md file to use the plugin-guided development workflow?

Yes, you need a valid SKILL.md file with YAML frontmatter containing name and description to use the plugin-guided workflow. Optional scripts, references, and assets directories can also be loaded at runtime for additional support.

Why are mandatory approvals required at Phase 3 and Phase 5 during troubleshooting?

Mandatory approvals at Phase 3 and Phase 5 are required to prevent scope drift and maintain context integrity. These formal handoffs ensure each role validates the work before the next phase begins, avoiding specification deviations.