Introduction¶

Most people working on landscape design Agent workflows likely encounter two types of problems: one is the lack of a unified orchestrator between stages, where stages 01 to 06 proceed independently, making it easy for stages to be skipped or outcomes to be verbally approved at handover points. The second is blurred validation boundaries, where the orchestrator casually judges image quality and concept compliance, undermining the expertise of the stage-specific Skills.

LandscapeFlow AI | Director introduced below is an orchestration Skill specifically designed to solve these two problems. It does not draw images, write PPTs, or perform any specific design tasks. It is responsible for only one thing: managing the pace of a landscape design project. It routes between stages, gates stage completion, while professional judgment always remains in the hands of the stage-specific Skills.

What is this¶

LandscapeFlow AI | Director (Landscape Design Director) is an orchestration Agent Skill for the entire landscape design workflow, coordinated at @user_3bc8c30f/landscapeflow-director. It is version 1.0.0, sourced from the community, categorized as ai-agent, published by user_3bc8c30f, and requires no API Key (tag requires_api_key=false).

It is positioned as a project-level orchestration brain that does only four things:

1. Take over a project (or resume from an interruption);
2. Determine the current stage;
3. Invoke the Stage Skill corresponding to the current stage;
4. Control the Human Gate, i.e., process gates that require human confirmation.

It also explicitly declares three things it will not do: it will not rewrite professional deliverables of stages, it will not replace Stage Skills, and it will not perform any specific design. This means the output of the Director is process state and Gate decisions, not the design content itself.

On the SkillHub page, this Skill has a rating of 100000 and 1142 downloads (data as of this capture).

Core Functions¶

The Sole Authority for Cross-Stage Routing¶

The Director holds the sole authority for cross-stage routing and uniformly manages three types of process Gates: B, C, and D. Unlike most orchestration Skills, it strictly controls when to proceed to the next stage: it cannot invoke the next stage without obtaining Human Confirmation, and the final project status: COMPLETED is written only by the Director after the Project Closeout Gate.

The practical effect of this rule is: there is only one writer and one timing for the project closing state. Stage Skills cannot declare project completion on their own, nor can humans push the status to the end directly during the process.

Four Types of Gates¶

The materials define four types of Gates with non-overlapping responsibilities:

The meanings of the three process Gates need to be remembered separately:

• Type B EXTERNAL_HANDOFF_GATE: Hands over stage deliverables to the designer for external production. The completion of the handoff action does not represent stage completion; the stage itself remains unclosed.
• Type C STAGE_CLOSEOUT_GATE: After all work in the stage is completed, the Director asks the human for confirmation, who chooses one of four paths: continue / modify / review / pause.
• Type D PROJECT_CLOSEOUT_GATE: Performs the final project closeout after 06C is completed. The project COMPLETED status is written only after this closeout.

Type A Gates are explicitly excluded from the Director’s management scope: internal stage decisions are professional judgments managed autonomously by the corresponding Stage Skills.

Validation Boundaries¶

The division of validation labor between the Director and Stage Skills is the most critical point to note in this mechanism:

• Director validates delivery completeness: File existence / readability / quantity / naming / type / missing pages / corruption / stage status formation. Essentially, whether the “accounting” of deliverables is correct.
• Stage Skills validate professional correctness: Image quality / landscape rationality / concept compliance / Blueprint consistency / PPT graphic-text accuracy. Essentially, whether the judgment at the content level is correct.

The Director must not judge professional outcomes itself; it must delegate professional validation to Stage Skills. The practical constraint here is: the orchestrator cannot deem a design professionally qualified just because “all files are there.” Professional validation must go through the Stage Skill layer, while the Director only performs completeness checks and Gate control.

pending_gate Cross-Session Recovery¶

The Director implements cross-session recovery via the pending_gate field. The flow is:

1. When the project enters a Gate requiring user decision, the Director writes pending_gate;
2. After the user completes the decision, the Director clears this field;
3. In any subsequent takeover, the Director prioritizes checking pending_gate.

The decision rule upon takeover is: if pending_gate is in the WAITING_FOR_HUMAN status, the Director first validates if the Gate and stage status are consistent; if consistent, it resumes the process; if contradictory, it invokes report_gate_conflict to stop, rather than continuing with the conflict.

This mechanism solves the session interruption issue: if the session breaks during a mid-process decision, the next takeover will not lose the Gate state, nor will it misjudge when states are inconsistent.

Stage Completion vs. Project Completion¶

The materials explicitly emphasize: Stage 06 COMPLETED is not equal to Project COMPLETED. Stage closeout and project closeout belong to Type C and Type D Gates respectively. The project status is written as COMPLETED by the Director only after passing the Project Closeout Gate following 06C.

This boundary is easily ignored in practice: even if all six stages are completed, the project is still in an unclosed state, and the final closeout remains an independent step.

Installation and Activation¶

The official materials do not provide a command-line installation method, so installation commands are not provided here. Please refer to the official address for activation:

https://api.skillhub.cn/user_3bc8c30f/landscapeflow-director

There are two known points regarding configuration: First, this Skill requires no API Key; Second, the project side needs to maintain a project-status.yaml. The Director relies on the stage status within it to determine the current stage and proceed or closeout. The pending_gate field is also stored in the project status as a basis for cross-session recovery.

According to the materials, this Skill does not inject any professional methods into 01–06, does not modify the 01–06 Stage Skills, and does not modify confirmed Blueprint design content. Therefore, it can coexist with existing Stage Skills upon activation without requiring changes to the Stage Skills’ behavior.

Typical Usage¶

The trigger scenarios for the Director come from official materials and include five categories:

1. Need to “take over / resume / advance a landscape design project”;
2. A stage in project-status.yaml needs to be advanced or closed out;
3. Need to hand over to the designer after 05A / 06A completion;
4. Need to validate and continue after the designer completes external outputs;
5. Need for final closeout after 06C completion.

We can look at how it operates through a complete project sequence:

1. Take over project: Director reads project-status.yaml, checks pending_gate first, and determines the current stage if there are no remnants;
2. Invoke Stage Skill: Calls the Skill for the corresponding stage to produce professional deliverables. The Director does not interfere with design content;
3. Stage Closeout: After the stage is completed, the Director performs a completeness check, then asks for human confirmation via Type C STAGE_CLOSEOUT_GATE. The human chooses to continue / modify / review / pause;
4. External Handoff: For processes involving 05A / 06A, it first passes Type B EXTERNAL_HANDOFF_GATE to hand over to the designer for external production. After external outputs return, the Director validates completeness and continues;
5. Final Closeout: After 06C completion, the Director proceeds through Type D PROJECT_CLOSEOUT_GATE, and writes the project as COMPLETED after human confirmation.

Among these, the Type B Gate in step 4 is an easily misinterpreted link: handover completion only means “the designer can start external production,” the stage itself is not closed out, and stage closeout still requires the Type C Gate.

Applicable Scenarios and Considerations¶

The suitable usage mode is: the project is already divided into stages 01–06, each stage has a corresponding professional Skill, and a unified entry point is needed to manage stage transitions and human confirmation. The Director acts as an entry layer overlaid on existing Stage Skills without changing the Stage Skills themselves.

A few points to note:

1. The Director does not make professional judgments; it requires scenario Skills to possess independent validation capabilities. If a stage lacks a delegable professional validation party, completeness checks cannot pass the professional correctness hurdle, and the process will stop at the Gate.
2. Type B and Type C Gates cannot be understood as merged. Handing over for external production is not stage completion. If the next stage is advanced directly after handover, it is a process misjudgment.
3. pending_gate and stage status must remain consistent. In case of contradiction, the correct action is to stop via report_gate_conflict, rather than manually clearing the status to continue.
4. Stage 06 COMPLETED is not equal to project completion. Project COMPLETED can only be written by the Director after the Project Closeout Gate.
5. The materials do not provide installation commands or runtime environment requirements. Please confirm installation and configuration methods at the official address before implementation.

Conclusion¶

The value of LandscapeFlow AI | Director lies in completely separating “process” and “design”: routing, completeness validation, and Gate control belong to the Director; professional validation belongs to Stage Skills; and human confirmation is latched at every Gate. For teams that already have a staged Skill system but lack a unified orchestration entry, it is an orchestration layer that can be overlaid on existing workflows.

Official Address: https://api.skillhub.cn/user_3bc8c30f/landscapeflow-director