Build

You are running /evyasys:Build $ARGUMENTS.

Step 0 — Load workflow

First — find the plugin's installed workflow directory (do this before any file read):

macOS / Linux — run via Bash:

EVYA_AI=$(find "$HOME/.claude/plugins" -maxdepth 6 -type d -name ".ai" 2>/dev/null | grep -i "EvyaGovernance" | head -1); [ -z "$EVYA_AI" ] && EVYA_AI=".ai"; echo "$EVYA_AI"

Windows — run via PowerShell:

$EVYA_AI = (Get-ChildItem "$env:USERPROFILE\.claude\plugins" -Recurse -Directory -Filter ".ai" -ErrorAction SilentlyContinue | Where-Object { $_.FullName -like '*EvyaGovernance*' } | Select-Object -First 1 -ExpandProperty FullName); if (-not $EVYA_AI) { $EVYA_AI = ".ai" }; Write-Output $EVYA_AI

Use the printed path in place of .ai for every workflow file read below, and as $EVYA_AI in the script commands the prompt gives you ($EVYA_AI/../scripts/lib/…). If a file is not found at the plugin path (older install), fall back to the same path under .ai/. Project files under .evyasys/workflows/build/ override same-named plugin files.

Load these from <plugin-ai>/workflows/build/:

1. AGENT.md — your role, mandate, test-writing standard and non-negotiables
2. PROMPT.md — the phased workflow, the gates and the exact output contract
3. CHECKLIST.md — the self-review checklist
4. QUESTIONING.md — Gate 1, including the unit-test question

The templates (DEVSUMMARY_TEMPLATE.md here; brainstorm, review and test-plan templates from this pack and the Qa pack) are loaded in Phase 0 of the prompt.

Then follow PROMPT.md exactly. Never claim a check passed unless project-checks.js reported it for the code as it is now — the hook compares a fingerprint of the changed files and will downgrade any claim the evidence does not support.