Domainspec Ui Pipeline

1. Read domainspec/CHANGELOG.md and extract current-framework constraints.
2. Validate feature prerequisites: a. Confirm docs/features/{feature}/SPEC.md exists → BLOCK if missing. b. Confirm docs/features/{feature}/interfaces.md exists and has HTTP endpoints → BLOCK if missing. c. Load all available aspect files (operations, queries, states, events, STORIES, capabilities).
3. If --dry-run, output the plan and stop.

Step 1 — Ensure UI Architecture

4. Check if docs/UI-ARCHITECTURE.md exists.
   • If missing → delegate to domainspec-ui-architecture skill (interactive questions, scaffolding, dependency install).
   • If exists → read it as the authoritative constitution.
5. Verify the web app builds: run build + type check. BLOCK if build fails.

Step 2 — Generate UI-SPEC

6. Delegate to domainspec-ui-phase-bridge {feature}:
   • Reads SPEC.md, interfaces.md, operations.md, queries.md, states.md, STORIES.md
   • Constrained by UI-ARCHITECTURE.md
   • Produces docs/features/{feature}/UI-SPEC.md
7. Present UI-SPEC summary to user for review.
8. If --spec-only, stop here and return summary.

Step 3 — Generate E2E Tests

9. Delegate to domainspec-generate-tests --ui --scaffold {feature}:
   • Derives E2E test obligations from UI-SPEC.md (rules 15–20)
   • Appends UI E2E section to TEST-SPEC.md
   • Scaffolds Playwright test files under {web-app}/e2e/{feature}/

Step 4 — Implement Frontend

10. Delegate to domainspec-ui-implement {feature}:
    • Creates pages, components, hooks, mutations from UI-SPEC + UI-ARCHITECTURE
    • Updates navigation sidebar
    • Updates query-keys.ts
11. Run build + type check. If build fails, fix issues and retry (max 2 iterations).

Step 5 — Visual Audit

12. If --skip-audit, skip to step 13.
13. Delegate to domainspec-ui-audit-bridge {feature}:
    • 6-pillar visual review (copywriting, visuals, color, typography, spacing, registry safety)
    • Produces docs/features/{feature}/UI-REVIEW.md
    • Maps findings to DomainSpec concept IDs

Completion

14. Return pipeline summary:
    • Artifacts created/updated (file paths)
    • E2E test count (by category)
    • Build status (pass/fail)
    • Audit verdict (PASS/FLAG/BLOCK per pillar, or skipped)
    • Concept coverage (which SPEC concepts now have UI representation) </process>