Files
EVOLV/.agents/skills/evolv-commissioning-validation/SKILL.md

55 lines
2.0 KiB
Markdown
Raw Normal View History

---
name: evolv-commissioning-validation
description: Plan and verify EVOLV commissioning readiness. Use when defining FAT/SAT test plans, acceptance criteria, loop checks, simulation-to-field validation, startup sequencing evidence, and rollout gates for operational deployment.
---
# EVOLV Commissioning Validation
## Mission
Convert implementation changes into deployment-ready evidence with clear acceptance gates.
## Harness Execution Contract
- Start from impacted contracts, modes, and site-operational constraints.
- Define invariants before edits:
- validation criteria are measurable and reproducible
- startup and failover behavior is proven, not assumed
- rollback path is explicit
- Produce evidence artifacts tied to concrete tests/checks.
## Scope
- Cross-node behavior spanning control, measurement, and integrations
- Test plans and validation docs under repository documentation paths
- Node-level suites where commissioning evidence is derived
## Workflow
1. Build FAT/SAT matrix from impacted contracts and risk areas.
2. Define pass/fail criteria and required instrumentation visibility.
3. Execute or script reproducible validation checks.
4. Capture evidence with timestamps, commands, and outcomes.
5. Define rollout gates and rollback triggers.
## Standards
- Prefer deterministic replayable checks over ad-hoc validation.
- Include negative-path and recovery-path tests.
- Tie each acceptance criterion to a concrete artifact.
- Keep operator handoff notes concise and actionable.
## Test Expectations
Cover:
- startup/shutdown commissioning sequences
- failover and reconnect scenarios
- alarm/interlock behavior under commissioning cases
- post-deploy smoke checks and regression shortlist
## Deliverables
Return:
- FAT/SAT-style validation matrix
- executed evidence summary
- go/no-go risks and mitigations
- rollback plan and monitoring checklist
Decision interview triggers:
- reduced commissioning scope under schedule pressure
- acceptance of unresolved high-severity risks
- rollout sequencing choices with operational impact