CWF Implementation Orchestrator FAQs

Question 1

How does it handle tasks that touch the same files?

Accepted Answer

It uses dependency detection heuristics to identify file overlaps; steps affecting the same files are grouped sequentially, while independent tasks are assigned to parallel agents.

Question 2

Do I need to create the plan manually?

Accepted Answer

While you can provide a manual plan, this skill is designed to work seamlessly with plans generated by 'cwf:plan', automatically detecting the most recent and relevant plan files.

Question 3

What is the primary purpose of the impl skill?

Accepted Answer

The impl skill takes a structured plan (plan.md) and orchestrates the actual coding work, managing multiple agents to execute tasks in parallel while respecting file dependencies and project constraints.

Question 4

What are the 'gates' mentioned in the documentation?

Accepted Answer

Gates are safety checks, such as the Branch Gate (ensuring you aren't on a base branch) and the Clarify Gate (ensuring the plan is ready), designed to prevent unpredictable execution.

Question 5

Can it handle browser-based debugging?

Accepted Answer

Yes, it includes a web-debug classification that triggers specialized protocols for runtime debugging, ensuring before-and-after evidence is captured for UI/UX changes.

CWF Implementation Orchestrator

Key Features

Use Cases

CWF Implementation Orchestrator

Key Features

Use Cases