plugins/github-copilot-modernization/skills/quality-gates/SKILL.md
Runs quality gate validation at each workflow stage. Supports 4 gate types: spec-quality, spec-to-plan, plan-to-tasks, completeness. Produces gate pass/fail reports with actionable feedback. Triggers: "run quality gate", "validate spec quality", "spec quality", "plan coverage", "check plan coverage", "validate plan to tasks", "check task traceability", "verify task completeness", "run completeness review", "review implementation", "check plan traceability", "check coverage", "completeness quality gate", "final sign-off", "feature parity sign-off", "completeness gate", "feature parity", "sign-off report", "verify all requirements". Requires `type` parameter to select the gate. NOT for: code review, implementation (use implementing-code), spec writing.
npx skillsauth add microsoft/github-copilot-modernization quality-gatesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You MUST consider the user input before proceeding (if not empty).
Reports and checkpoints are written under your task's Artifact path: (from task metadata).
checklists/requirements.md ← spec-quality gate
checkpoints/spec-to-plan.yaml ← spec-to-plan gate
traceability-matrix.yaml ← completeness gate
migration-summary.md ← completeness gate
type = spec-quality | spec-to-plan | plan-to-tasks | completeness
Load from cwd:
Load the checklist reference for the selected gate:
| type | Reference | Key Output |
|------|-----------|------------|
| spec-quality | references/gate-spec-quality.md | checklists/requirements.md |
| spec-to-plan | references/gate-spec-to-plan.md | checkpoints/spec-to-plan.yaml |
| plan-to-tasks | references/gate-plan-to-tasks.md | checkpoints/plan-to-tasks.yaml |
| completeness | references/gate-completeness.md | traceability-matrix.yaml + migration-summary.md |
Follow the process defined in the referenced gate file.
✓ [gate] PASSED.✗ [gate] FAILED. N critical issues. + remediation steps| Level | Meaning | |-------|---------| | CRITICAL | Checkpoint failed, broken traceability, constitution violation, requirement not implemented, testing strategy deviation without documented blocker | | HIGH | Partial requirement, implementation drift, untested acceptance criteria | | MEDIUM | Incomplete non-functional coverage, terminology drift | | LOW | Style/naming, documentation gaps |
references/gate-spec-quality.md — spec quality checklist and processreferences/gate-spec-to-plan.md — spec-to-plan checklist and processreferences/gate-plan-to-tasks.md — plan-to-tasks checklist and processreferences/gate-completeness.md — completeness checklist and process (includes plan coverage)templates/report-template.md — migration summary structuredevelopment
Scan dependency manifests against known CVEs and remediate by upgrading vulnerable dependencies to patched versions, then rebuild and re-scan to confirm. Self-contained scan→fix→verify loop for any project with a dependency manifest. Use when: a cve-remediation task is dispatched; dependency set changed (version bump, new framework); assessment flagged vulnerable or EOL dependencies; or user asked to "fix CVEs", "patch vulnerabilities", or "dependency security". Triggers: "cve", "remediate cve", "fix cves", "patch vulnerable dependencies", "vulnerability scanning", "dependency security", "vulnerable dependencies", "security advisories", "npm audit", "pnpm audit", "maven audit", "gradle audit", "dependency scan", "vulnerability remediation". NOT for: security audit of auth/input/secrets/OWASP code paths (use security-review).
development
Generate dependency map diagram from project build files
documentation
Generate data architecture and persistence layer documentation with data model diagram
documentation
Generate core business workflow documentation with sequence diagram