协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
subcontractor-scorecard【开发与工程】Score a subcontractor's performance across schedule reliability, quality, safety, paperwork, and change-order behaviour with weighted anchors. Use when asked to evaluate a sub, build a subcontractor scorecard, decide whether to rebid or rehire a trade, review sub performance for prequalification, or justify removing a sub from the bid list. Produces …
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Every GC has a mental list of subs they'd hire again and subs they'd rather eat the higher bid to avoid. This skill turns that instinct into a defensible record: five weighted dimensions, anchored 1–5 scales so two reviewers score alike, evidence per rating, and a recommendation you can put in front of a preconstruction meeting — or a sub's principal — without it reading as a grudge.
Ask for what's missing; from partial data, score what's evidenced and mark unscored dimensions [insufficient data] rather than guessing:
Score each dimension 1–5 against the anchors, then weight:
| Dimension | Weight | 1 (fails) | 3 (solid) | 5 (excellent) |
|---|---|---|---|---|
| Schedule reliability | 30% | Chronic slips, ghost crews, drives the critical path late | Hits most dates; slips flagged early with recovery plan | Hits dates, staffs to plan, accelerates when asked without drama |
| Quality / rework | 25% | Repeated failed inspections, punch counts far above trade norm, back-charged rework | Normal punch volume, closes items promptly, rare rework | First-time-quality culture; punch list light and closed fast |
| Safety | 20% | Recordable(s) from ignored controls; fights the safety program | Compliant; participates in briefings; near-misses reported | Brings hazards to you first; crews self-police; clean record |
| Paperwork discipline | 10% | Chases required for waivers/certs; closeout drags months | Mostly on time with reminders | Billing, waivers, and closeout docs arrive right, first time |
| Change-order behaviour | 15% | Weaponises COs — lowball bid, then claims on every RFI | Prices changes fairly with backup; negotiates in good faith | Flags cost issues before they're changes; transparent pricing |
Composite = Σ(rating × weight) × 20, giving 0–100. Map to a recommendation:
Safety scores of 1–2 cap the overall recommendation at Conditional regardless of composite — a sub who hurts people isn't "preferred" at any price.
1. Composite score & recommendation tier — with the one-paragraph justification.
2. Dimension table — | Dimension | Weight | Rating (1–5) | Evidence |
3. Trend note — improving, stable, or declining vs. prior projects, if history given.
4. Conditions / feedback points — specific, evidence-backed items for the sub conversation.
5. Data gaps — dimensions scored on thin evidence, flagged [insufficient data].
[insufficient data] and say what record-keeping would fix it