rhzy-functional-coverage-audit

Audit construction-unit departmental responsibility coverage and classify events into four compliance modes.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/pinedu/xmc-work-wiki --skill rhzy-functional-coverage-audit-pinedu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rhzy-functional-coverage-audit
Source: https://github.com/pinedu/xmc-work-wiki/tree/main/skills/rhzy-functional-coverage-audit
Command: npx skills add https://github.com/pinedu/xmc-work-wiki --skill rhzy-functional-coverage-audit-pinedu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Construction project owners often cannot tell which internal department owns an incoming event, whether the event is even within the company's functional scope, or how to respond without overstepping compliance boundaries. This Skill maps any construction-phase event to a 5-department functional whitelist (pre-development, engineering management, cost & contracts, finance, general administration) and produces a lead/co-department verdict plus a coverage conclusion. ## Core Features & Use Cases - Functional Coverage Audit: Classifies events as covered, missing-capability, or needs-more-info against a fixed 5-department whitelist, with strict rules against inventing departments outside the whitelist. - Four-Mode Event Judgment: Routes events into pre-event (risk avoidance), in-event (loss mitigation), post-event (accountability), or severance (self-exoneration and liability transfer) modes, each with a fixed output structure. - Locked Output Formats: Enforces a 6-field alert format, a standard 6-field audit format, and an ultra-compact 2-3 line mode, with anti-pattern rules (RM-1 to RM-14) distilled from repeated boss corrections. - Use Case: A project owner asks "the contractor submitted a progress payment request, who handles it and when will it be paid?" The Skill answers with the lead department (cost & contracts), co-departments, the T+5/T+13 timeline, and a compliance alert without expanding into unnecessary checklists. ## Quick Start Describe a construction project event and ask which department owns it and whether the company's functions cover it.

Frequently Asked Questions about rhzy-functional-coverage-audit

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

FAQPage Schema
How do I determine which department owns a construction project event?

Match the event against the 5-department functional whitelist covering pre-development, engineering management, cost & contracts, finance, and general administration. The Skill outputs a lead department, co-departments, and a coverage conclusion of covered, missing, or needs-more-info.

What is the four-mode judgment method for construction events?

Events are classified by three checks: whether the owner acted, whether trouble has occurred, and whether the owner is at fault. This yields pre-event avoidance, in-event loss mitigation, post-event accountability, or severance mode for self-exoneration and liability transfer.

When should an event be flagged as a functional coverage gap?

Flag a gap whenever the event requires capabilities outside the whitelist, such as legal negotiation, after-sales maintenance, municipal coordination outside the site boundary, or IT platform operations. The Skill forbids inventing new departments to force a fit.

Can the Skill cite specific legal articles in its risk alerts?

Only when the original legal text exists in the archived reference files. If the source text is unavailable, the Skill must mark the citation as unverified rather than quoting article numbers or penalty amounts from memory.

What output formats does the coverage audit support?

Three locked formats: a 6-field compliance alert with risk quantification and action buttons, a standard 6-field audit with verdict and basis, and an ultra-compact 2-3 line answer for direct questions about timing, feasibility, or responsible parties.

What are the limitations of this functional coverage audit?

It only applies during the construction phase; events after completion handover are treated as transferred to operations. It also refuses to judge events missing key facts such as project stage, warranty status, or liability attribution, returning a needs-more-info verdict instead.