flagship-docs-review

Audit and repair documentation, issuing a PASS/BLOCKED verdict.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AmirTlinov/magray-marketplace --skill flagship-docs-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flagship-docs-review
Source: https://github.com/AmirTlinov/magray-marketplace/tree/main/flagship-team/skills/flagship-docs-review
Command: npx skills add https://github.com/AmirTlinov/magray-marketplace --skill flagship-docs-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of ensuring documentation meets a high, consistent standard across a project or organization, identifying and rectifying gaps and inconsistencies.

Core Features & Use Cases

  • Documentation Auditing: Assesses documentation completeness, consistency, determinism, and traceability against defined criteria.
  • Repair and Improvement: Fixes identified gaps and inconsistencies to elevate documentation quality.
  • Use Case: When a new feature is developed, this Skill can be used to review all associated technical documentation, ensuring it aligns with the project's flagship quality standards before release.

Quick Start

Use the flagship-docs-review skill to audit and repair the documentation for the 'user-authentication' module.

Frequently Asked Questions about flagship-docs-review

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

FAQPage Schema
How do I audit technical documentation for consistency and completeness?

Documentation auditing assesses completeness, consistency, determinism, and traceability against defined criteria. It involves inventorying docs, scoring by axes, identifying gaps, and issuing a PASS/BLOCKED verdict based on risk, security, and operational coverage.

What is the best way to repair inconsistent project documentation?

To repair inconsistent project documentation, the process fixes identified gaps and inconsistencies directly, rebuilds traceability across the document set, and elevates content to meet a consistent flagship quality standard before release.

How do I review technical documentation before a feature release?

Reviewing technical documentation before a feature release requires auditing all associated documents to ensure alignment with project quality standards. The process scores completeness, consistency, and traceability, issuing a final PASS or BLOCKED verdict.

Can I use documentation review to check traceability and security coverage?

Yes, documentation review can check traceability and security coverage. The audit process specifically scores documents across multiple axes including traceability, security, risk, and operational aspects to identify missing coverage gaps.

What does a PASS or BLOCKED documentation review verdict mean?

A PASS or BLOCKED documentation review verdict indicates whether audited documents meet the required flagship quality standard. PASS confirms successful quality assurance and repair, while BLOCKED highlights unresolved gaps in consistency, determinism, or traceability.