quality-gates

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.

Jump to install Review files

Repository: microsoft/github-copilot-modernization
Last source activity: July 17, 2026 at 03:11
Detected SKILL.md language: English
Stars: 53
Forks: 16

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/microsoft/github-copilot-modernization/tree/main/plugins/github-copilot-modernization/skills/quality-gates.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/microsoft/github-copilot-modernization --skill quality-gates

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

8 files

SKILL.md

Source instructions · Read-only preview

name: quality-gates
description: 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.

## User Input You **MUST** consider the user input before proceeding (if not empty). ## Output 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 ``` ## Input `type` = `spec-quality` | `spec-to-plan` | `plan-to-tasks` | `completeness` ## Workflow ### Step 1: Load Context Load from cwd: - constitution.md — **non-negotiable**; violations are always CRITICAL - spec.md, plan.md, tasks.md, checkpoints/ (as relevant for the gate type) ### Step 2: Gate Routing 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 | ### Step 3: Execute Gate Follow the process defined in the referenced gate file. ### Step 4: Verdict - **PASS**: all checklist items pass → `✓ [gate] PASSED.` - **FAIL**: any CRITICAL → `✗ [gate] FAILED. N critical issues.` + remediation steps ## Rules - **READ-ONLY**: never modify source code; only write checklists, checkpoints, reports. - **Max 50 findings** per gate. - **Deterministic**: rerunning without changes = same results. - **Never hallucinate**: if artifact is missing, report it. ## Severity | 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 | ## Resources - `references/gate-spec-quality.md` — spec quality checklist and process - `references/gate-spec-to-plan.md` — spec-to-plan checklist and process - `references/gate-plan-to-tasks.md` — plan-to-tasks checklist and process - `references/gate-completeness.md` — completeness checklist and process (includes plan coverage) - `templates/report-template.md` — migration summary structure

View on GitHub

Back to search Back to installation

analyzing-architecture

Architect analysis for rewrite/migration: produces structured architecture artifacts plus global prose research views (project-structure, tech-stack, data-model) for planning, implementation, feature-inventory, and gates. This is the single architect task. Triggers: "analyze architecture", "analyze existing application", "analyze the codebase", "codebase architecture analysis", "analyze for migration", "prepare migration analysis", "produce migration artifacts", "analyze before rewrite". NOT for: greenfield projects, pure syntax/version migrations (Python2→3, Java 8→17 — no paradigm shift), runtime validation (use runtime-validation), infrastructure/deployment analysis (use analyzing-operations), feature inventory/spec writing (use feature-inventory).

2026-09-22

assessment-report-converter

Convert an arbitrary CSV report (e.g. a Black Duck export or a custom migration-issue inventory) into a schema-valid assessment `report.json` the modernization pipeline can consume — so it appears in the assessment UI and migration solutions resolve automatically. This skill is LLM-driven: you read and interpret the CSV yourself and author `report.json` by hand against the schema. A small helper script only does deterministic lookups (migration solutions, the ruleId for a solution) and validates the finished report. There is NO "convert everything" script and NO assumed column layout. Triggers: "convert csv to assessment report", "import csv report", "turn this spreadsheet into a report.json", "Black Duck csv to report", "build report.json from csv", "migrate a third-party assessment export". NOT for: AppCAT-style analysis from source (use `assessment`), generating a modernization plan (use `create-modernization-plan`), or editing a report.json the pipeline already produced.

2026-09-22

assessment

Run a fully local application assessment for one Java, .NET, or JavaScript/TypeScript repository

2026-09-22

View all from this repository

quality-gates

Source facts

Install options

Install with an AI assistant

Review the source files

More from this repository

Install with an AI assistant

More from this repository