zwright8 Engineering Policy Constraint Compiler
Why This Skill Exists
We need this skill because delivery speed must increase without sacrificing correctness. This specific skill turns governance language into enforceable runtime checks.
When To Use
Use this skill when the request explicitly needs "Engineering Policy Constraint Compiler" outcomes in the Software Engineering Automation domain.
Step-by-Step Implementation Guide
- Define the scope and success metrics for
Engineering Policy Constraint Compiler, including at least three measurable KPIs tied to regressions and brittle release pipelines. - Design and version the input/output contract for code changes, tests, incidents, and rollout data, then add schema validation and failure-mode handling.
- Implement the core capability using rule compilation, and produce executable policy bundles with deterministic scoring.
- Integrate the skill into swarm orchestration: task routing, approval gates, retry strategy, and rollback controls.
- Add unit, integration, and simulation tests that explicitly cover regressions and brittle release pipelines, then run regression baselines.
- Deploy behind a feature flag, monitor telemetry/alerts for two release cycles, and iterate thresholds based on observed outcomes.
Required Deliverables
- Capability contract: input schema, deterministic scoring, output schema, and failure modes.
- Runtime profile: contract-compiler using rule compilation to produce executable policy bundles.
- Orchestration integration: software-engineering-automation:contract-compiler routing, approval gates, retries, and rollback controls.
- Validation evidence: unit, integration, simulation, regression-baseline suites and rollout telemetry.
Operational Runbook
Preflight
- Confirm the Engineering Policy Constraint Compiler request scope, source evidence, and measurable success criteria before execution.
- Verify feature flag skill_0531_engineering-policy-constraint-co, approval gates, and rollback owner before autonomous use.
Execution
- Execute rule compilation with deterministic scoring and reproducible trace capture.
- Produce executable policy bundles plus scorecard, assumptions, and unresolved-risk notes.
Recovery
- Fail closed when required signals, evidence, or approval gates are missing.
- Rollback to the last stable baseline when posture is critical or validation fails.
Handoff
- Publish executable policy bundles, validation evidence, and telemetry links to downstream owners.
- Queue follow-up tasks for unresolved risks, threshold tuning, or approval review.
Guardrails
- [quality] Require deterministic scoring and validation evidence before promotion.
- [reliability] Preserve retries, rollback controls, and failure-mode evidence for every run.
- [safety] Route critical posture or missing approval gates to human review before autonomous action.