construction-risk-workflow

Guides construction risk consultations through a six-phase gated decision workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Construction project owners (developers) facing wage arrears, safety, quality, schedule, or compliance risks often receive unstructured advice that skips evidence verification and legal boundary checks. This Skill enforces a mandatory six-phase gated workflow that classifies the risk scenario, walks a node-by-node decision tree with credential verification, and produces legally grounded action plans from the owner's perspective. ## Core Features & Use Cases - Six-Phase Gated Flow: Enforces Phase 0 input intake, Phase 1 three-question chain plus rule-engine scanning, Phase 1.5 wage-arrears decision tree, Phase 2 situation conversion judgment, Phase 3 three-round self-attack validation, Phase 4 eight-element plan output, Phase 5 measure-goal alignment, and Phase 6 monitoring and case closure. - Credential-Gated Decision Tree: Each decision node requires both a user answer and uploaded evidence (bank statements, wage ledgers, contracts) before unlocking the next node, preventing unsupported conclusions. - Rule Engine and Situation Library: References 30+ if-then risk rules (A1-A22 wage arrears, B safety, C quality, D schedule, E compliance) and 13 wage-arrears situations with conversion paths and special-account hard boundaries. - Use Case: A developer discovers workers protesting unpaid wages at a project site. The Skill classifies the event, walks the payment-status decision tree node by node with voucher uploads, locates the terminal situation, and outputs an eight-module plan including evidence lists, document templates, and external communication scripts. ## Quick Start Describe your construction project risk event with the project name, parties involved, amounts, and timeline, and upload the relevant contracts and payment records to begin the gated assessment.

Frequently Asked Questions about construction-risk-workflow

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

FAQPage Schema
How do I handle a construction wage arrears risk as the project owner?

Describe the event with project name, parties, amounts, and timeline. The workflow runs a three-question chain to classify the mode, then walks a decision tree asking about payment status, split accounts, and special account balances, requiring voucher uploads at each node before locating your situation and outputting an action plan.

What documents do I need to upload for the wage arrears decision tree?

Each node specifies required evidence such as financial statements, payment bank records, construction contracts, wage special account statements, wage tables signed by workers, and valuation approval forms. The workflow will not advance to the next node until all required credentials for the current node are uploaded and verified.

Can I skip the workflow and go directly to a specialized skill?

Only when you explicitly state that you want to bypass the workflow and query a specific specialized skill directly. Otherwise all construction risk consultations must pass through the six-phase gated flow first, and directly triggering downstream skills is treated as a routing error.

What happens if my answers contradict my uploaded documents?

The workflow pauses and asks you to reconcile the contradiction, such as inverted dates, mismatched amounts, or wrong entities. It will not advance the decision tree until the inconsistency between your answers and the uploaded evidence is resolved.

What are the limitations of this construction risk workflow?

Events outside the rule engine coverage are flagged as boundary cases requiring manual judgment rather than forced matching. Schemes failing three consecutive self-attack rounds trigger a recommendation to consult a professional lawyer, and illegal-contract scenarios have no compliant downgrade path.