release-check

Generate a Go/No-Go release readiness report from Feishu data and scope baselines.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/wuji-technology/pm-workflow-plugin --skill release-check-wuji-technology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-check
Source: https://github.com/wuji-technology/pm-workflow-plugin/tree/main/skills/release-check
Command: npx skills add https://github.com/wuji-technology/pm-workflow-plugin --skill release-check-wuji-technology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release-check solves the problem of uncertain release readiness by providing a repeatable, evidence-based checklist and Go/No-Go recommendation to reduce release risk and last-minute surprises. It consolidates live Feishu project data, optional local scope baselines, and repository context to produce a single authoritative release readiness report.

Core Features & Use Cases

  • Scope confirmation: Parse product context and optionally read Scope Baseline files to verify which Stories belong to the target version.
  • Live validation: Run MOQL queries and individual work item briefs to validate P0/P1/P2 Story and Bug statuses in real time.
  • Six-dimension checks & reporting: Evaluate functional completeness, quality, documentation, technical readiness, risk, and operations; output a templated release-check markdown report and Go/No-Go recommendation.
  • Use case: Use when preparing a production or firmware release to ensure P0 items are completed, critical bugs are mitigated, and rollout/runbook preparations are in place.

Quick Start

Use the release-check skill by running /release-check {product} {version} to generate a structured release readiness report and a Go/No-Go recommendation.

Frequently Asked Questions about release-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a structured go/no-go release readiness report?

To generate a structured go/no-go release readiness report, run /release-check {product} {version} to validate Feishu project data and local scope baselines across six dimensions and output a markdown recommendation.

What is a multi-dimensional release check for production deployment?

A multi-dimensional release check evaluates functional completeness, quality, documentation, technical readiness, risk assessment, and operations to verify production deployment readiness and produce an evidence-based go/no-go recommendation.

Does release-check work with Feishu project data and MOQL queries?

Yes, release-check works with Feishu project data by running MOQL queries and individual work item briefs to validate P0/P1/P2 Story and Bug statuses in real time for release preparation.

How do I verify P0 Story completion and critical bug mitigation before a firmware release?

To verify P0 Story completion and critical bug mitigation before a firmware release, execute a release readiness check to parse live Feishu project records and confirm that all critical items are mitigated or completed.

Do I need local scope baseline files to perform a release readiness check?

Local scope baseline files are optional but recommended; the release readiness check parses product context and optionally reads scope baseline files from portfolio/{product}/requirements/stories/ to verify which Stories belong to the target version.

Where is the final release check markdown report saved?

The final release check markdown report is saved in the portfolio/{product}/delivery/tracking/releases/ directory, consolidating scope confirmation and live validation results into a single authoritative file.