From xlfg-engineering
Apply production-readiness gates to an xlfg run without recreating duplicated planning state.
npx claudepluginhub flrngel/xlfg --plugin xlfg-engineeringThis skill uses the workspace's default tool permissions.
Use these gates to keep an xlfg run production-ready.
Creates structured quality gates for workflow boundaries like pre-merge checklists, deployments, and phase transitions with pass/fail criteria, exact commands, and escalation procedures.
Runs strict quality gate orchestration via team-plan -> team-prd -> team-exec -> team-verify pipeline, with team-fix loops until validation passes or blockers noted. Summarizes evidence, risks, release decision.
Validates AI agent claims like 'tests pass' or 'fixed' against evidence trails and tool outputs. Detects stubs and unproven assertions. Auto-triggers at workflow end.
Share bugs, ideas, or general feedback.
Use these gates to keep an xlfg run production-ready.
A run is only done when all relevant gates apply.
memory-recall.md exists and captures strong prior lessons or an explicit no-hitspec.md is the single source of truth for request truth, why, harness choice, solution, task map, and proof summaryspec.md makes false success explicitresearch.md, diagnosis.md, solution-decision.md, flow-spec.md, env-plan.md, proof-map.md, risk.md)test-contract.md exists, stays concise, and the run followed it honestlytest-readiness.md was READY before implementation or the run explicitly returned to planningworkboard.md reflects stage and task truthspec.mdverification.mdAsk:
spec.md still describe the shipped change?