Premmodhaofficial Nfr Pipeline Environment Prerequisites Check

environment-prerequisites-check

SDK-pipeline additions — Go pack (checked when target_language: go)

SDK-pipeline additions — Python pack (checked when target_language: python)

Shared (every pack)

Environment Prerequisites Check

Phase leads MUST verify runtime tool availability before launching agent waves. Missing runtimes cause cascading guardrail failures that produce zero quality signal.

When to Use

• At the START of any phase (before Wave 1)
• When guardrails report SKIP or FAIL due to missing tools
• Used by: implementation-lead, testing-lead, frontend-lead, detailed-design-lead

Origin

Feedback run-2: Missing runtimes caused cascading guardrail failures across 4 phases — Go runtime missing in implementation/testing, Node.js missing in frontend (11 guardrails skipped, 100% skip rate), gcc missing in implementation.

Go Phase Prerequisites

Frontend Phase Prerequisites

Verification Script Template

#!/bin/bash
# Phase prerequisites check — run before Wave 1
set -e
PHASE=$1
MISSING=()

check_tool() {
  if ! command -v "$1" &>/dev/null; then
    MISSING+=("$1")
    echo "FAIL: $1 not found (required for: $2)"
  else
    echo "PASS: $1 ($($1 --version 2>/dev/null | head -1))"
  fi
}

case "$PHASE" in
  implementation|testing)
    check_tool go "compilation, tests"
    check_tool gcc "race detector, CGO"
    check_tool golangci-lint "lint guardrail"
    ;;
  frontend)
    check_tool node "build, tests"
    check_tool npm "dependencies"
    ;;
esac

if [ ${#MISSING[@]} -gt 0 ]; then
  echo "BLOCKER: ${#MISSING[@]} tools missing. Guardrails will produce zero quality signal."
  exit 1
fi
echo "All prerequisites satisfied."

Missing Tool Impact Matrix

Phase Lead Protocol

1. Run prerequisites check script at phase start
2. If tools are missing: a. Log a "type":"event" decision entry with severity "high" listing missing tools b. Estimate scope impact (how many guardrails will be affected) c. Decide: proceed with degraded quality gates OR block until tools are available d. If proceeding, log the decision with explicit risk acceptance
3. Include prerequisites status in the phase report

MCP dependencies (optional, non-blocking)

MCP servers extend agent capability but are never on the correctness path. Phase leads check availability at phase start; any MCP unavailable → WARN entry in the decision log; pipeline proceeds with the documented fallback.

Policy: any MCP unavailable → WARN; pipeline proceeds. A missing MCP is NEVER a BLOCKER. Guardrail G04 mcp-health records the verdict at phase start; agents consult that verdict instead of probing per-call.

Source: PremModhaOfficial/NFR-pipeline — distributed by TomeVault.