---
name: wireframe-coordinator
description: Coordinate the full hybrid wireframe generation workflow between the user, documentation-normalizer, ux-constructor, and figma-wireframe-builder. Use when Codex needs to route requests, initialize artifacts, normalize user intent, maintain decision_log, choose the next pipeline step, ask only blocking product questions, or explain current documentation-to-Figma status.
---

# Wireframe Coordinator

Route user requests through the documentation-to-wireframe pipeline.

## Load First

- `.agents/skills/_shared/references/artifact-contracts.md`
- `.agents/skills/_shared/references/quality-gates.md`
- `.agents/skills/_shared/references/alternative-landscape.md` when explaining market positioning or design choices.

## Request Routing

- New project or new docs: invoke `documentation-normalizer`.
- UX architecture, flows, screen list, or UX rationale: invoke `ux-constructor`.
- Create or update Figma screens: invoke `figma-wireframe-builder`.
- Status or explanation: inspect artifacts and summarize the current stage.
- Change request: identify affected artifacts, update only downstream outputs that depend on the changed requirement.

## Workflow

1. Initialize artifacts:
   `powershell -File scripts/wireframe/init-artifacts.ps1 -ArtifactDir workspace/artifacts/wireframe-gen`
2. Read existing artifacts to determine current stage.
3. Normalize the user request into one of:
   `new_project`, `add_sources`, `regenerate_normalized_project`, `regenerate_ux`, `build_figma`, `edit_figma`, `explain_decision`, `status`.
4. Run Open Questions Review Gate before UX construction and before Figma generation.
5. Execute the smallest safe next step only after blocking questions for that stage are resolved.
6. Update `decision_log.md` with user decisions, assumptions, and blockers.
7. Validate artifacts after each generation/update step.

## Open Questions Review Gate

Open questions are surfaced in dialogue. Do not silently continue when unresolved blocking questions exist.

Run stage validation before UX construction:

```powershell
powershell -File scripts/wireframe/validate-artifacts.ps1 -ArtifactDir workspace/artifacts/wireframe-gen -Stage pre-ux
```

Run stage validation before Figma generation:

```powershell
powershell -File scripts/wireframe/validate-artifacts.ps1 -ArtifactDir workspace/artifacts/wireframe-gen -Stage pre-figma
```

When the gate blocks, show the user:

- question ID and question text;
- why it blocks the stage;
- affected artifact or stage;
- available default assumption if present;
- requested answer format.

After the user answers, update the question with `status: "answered"` or `status: "resolved"`, fill `answer` and `answered_at`, then append the decision to `decision_log.md`.

## Decision Log Format

Append entries like:

```markdown
## 2026-05-03T12:00:00Z - Decision

- Request: Build first Figma wireframes.
- Decision: Use native Figma MCP and mid-fi fidelity.
- Affected artifacts: screen_blueprints.json, figma_build_manifest.json.
- Source: user.
```

## Coordination Rules

- Prefer local artifacts over conversation memory.
- Do not regenerate downstream artifacts if only an unrelated upstream detail changed.
- Keep unresolved product or Figma target questions explicit.
- Stop at the Open Questions Review Gate when unresolved blocking questions exist.
- If a question is not blocking, continue only after recording the default assumption in `decision_log.md`.
- Keep schema keys in English and summaries in Russian by default.
- Keep all client project artifacts under `workspace/`; do not place client-specific data in Origin system folders.
- Keep the user-facing response short: what changed, where, validation result, and next useful step.