executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
inbox-triageClassify a construction office email, letter, or message pack and return severity, artefact type, one next action, and an unsent draft. Use when the user says triage, inbox, what do I do with this, email pack, letter from superintendent, or sort these messages.
Independent GitHub snapshot · Automated classification · Original documentation governs
Sort first. Draft second. Never send.
| Code | Meaning | Typical clock |
|---|---|---|
| S1 | Safety, structural, stop-work, statutory | same shift |
| S2 | Time-bar / notice / hold-point blocker / payment schedule | this week, often days |
| S3 | Normal commercial or information | register + draft |
| S4 | FYI / spam / already closed | file or ignore |
If a contract notice period is unknown, still flag S2 when the text looks like a notice, direction, or claim. Do not invent the bar date.
Pick one primary, plus secondary tags.
RFI DIRECTION VARIATION EOT NCR PROGRAMME PAYMENT INSURANCE WHS MEETING TENDER ADMIN UNKNOWN
If it is an RFI, next skill = rfi-drafter.
If it is extra work or delay = variation-eot-draft.
If it is a defect = ncr-punch-writer.
If it is a meeting = meeting-minutes-actions.
UNSENT.Follow assets/triage-card.md. For a pack, emit a table first then cards for S1/S2 only.
HOLD POINT — no message sent