31 tools for this part of the work. Skills load themselves when the conversation matches; commands are typed with a slash; agents review in their own context and report back.
Write the project email, and check whether it should be an email at all
Build the agenda around what has to be decided, not what to talk about
Turn technical language into client-ready wording, and back
Render Markdown into Word, Excel, or PDF for transmittal
Record what a project taught you, and read it back next time
Read somebody else's minutes for what they recorded about you
Keep issues, decisions, risks, and action items in one dated log
Read an email or message thread for what was actually decided
Read an owner-drafted agreement for what it moves onto you
Find the next required step and notice deadline in a dispute
Draft an additional services request before the work is done, not after
Explain a certificate of insurance and what it does not prove
Generate a weekly project status report
Score a pursuit before it costs you, on the things that actually predict
Recommend policy types, limits, and a wrap-up structure
Track every pursuit from first whisper to won or lost, and what each cost
Find out how the building is actually used, and tell someone
Build a response that answers what was asked, in their order
Assemble an SF330 with the project sheets that actually match the scope
Settle what has to be decided now, and what can wait
Check that your subconsultant agreements match what you promised the owner
Track hours against fee by phase, and see the overrun while it is small
A licensed architect's read on what you are about to seal
A construction lawyer's read on a contract or claim
Establish which area standard governs and what actually counts in it
Close the gap between the programme and the budget, and price what goes