Explore skills
Showing 53221–53250 of 77079 skills
Works out what kind of water is appearing before anyone opens a wall: rain driven in, groundwater, a plumbing failure, condensation, or air-carried moisture, which look identical inside and have entirely different causes, owners and repairs. Reads the evidence that separates them — when it appears, what the weather was doing, whether it is warm or cold, whether it is clean, whether it stops — then narrows the source and names what would confirm it. Trigger on "there is a leak", "water is coming in", "a stain appeared on the ceiling", "is this condensation or a leak", "where is this water coming from", "leak-triage", or water appearing anywhere with no agreed cause. Carries no dew points, no rainfall figures and no test standards; every value comes from the building's own data or the tester. It diagnoses rather than repairs, does not apportion liability, and does not replace the enclosure consultant, the plumber, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReviews a built enclosure mockup, visual or performance, against the documents rather than against how it looks: establishes what this mockup was built to prove before anyone walks up to it, works the observation in a fixed order so the buildable-but-wrong conditions get seen, separates what the mockup demonstrated from what it merely did not contradict, and records what becomes the accepted standard for the rest of the work. Trigger on "mockup review", "reviewing the visual mockup", "performance mockup results", "what do we check at the mockup", "mockup punch list", "mockup-review", or a mockup photographed or described with a request for what to look at. Carries no tolerances, no test criteria and no acceptance thresholds; every one of those comes from the specification. It is not a test report, does not witness testing, does not accept or reject on the Architect's behalf, and does not replace the enclosure consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds an agenda for any project meeting from the decisions it has to produce rather than from the topics somebody wants to raise. Establishes who has to be there for each decision and whether they are coming, what has to be sent in advance for a decision to be possible, and what is being discussed with nobody present who can decide it — which is how a meeting produces a follow-up meeting. Trigger on "agenda for tomorrow", "what should we cover in this meeting", "build the agenda", "prep for the client meeting", "agenda-builder", or a meeting coming up with nothing prepared. Carries no meeting formats and no standard agendas; the items come from what this project actually needs settled. `meeting-notes-cleaner` handles what comes out of the meeting; this handles what goes in. It does not replace the principal or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads an owner-drafted or heavily amended professional services agreement for the provisions that shift risk onto the architect, working in the order the money moves rather than the order the document is written: standard of care, indemnity, limitation of liability, insurance, scope creep, payment and termination, ownership, and the dispute path. Reports each finding with the clause quoted, what it changes from the industry-standard position, whether it is insurable, and whether it is usually negotiable. Trigger on "review this contract", "the client sent their own agreement", "is this indemnity clause standard", "can we sign this", "contract-review", or an agreement handed over before signing. Carries no standard-form text and no legal positions; comparisons to a standard form require you to supply it. It is not legal advice and does not replace the attorney, the broker, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexScores a pursuit before the proposal is written, against the factors that actually predict whether a project is won and whether it is worth winning: the relationship, the client's decision process and funding, the competition, the fit with what the practice does, the fee and terms, and the capacity to deliver it. Records the decision and the reasoning so it can be read back against the outcome. Trigger on "go no go", "should we chase this", "pursuit review", "is this RFP worth answering", "go-no-go-review", or an opportunity raised for a decision. Carries no scoring weights and no thresholds; the practice sets what matters to it and what score means yes. It does not write the response — `rfp-response-builder` does — and does not decide. It records a decision somebody made, with the reasoning, so the next one is better informed.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexKeeps a lessons-learned log in docs/practice/lessons.md: what happened, what it cost or saved, why it happened as stated, and what to do differently, each entry tagged by phase and topic so it can be found when the situation recurs. Trigger on "lessons learned", "post-mortem", "what went wrong", "remember this for next time", "add a lesson", "lessons-learned", the close of a project, or the start of one, when the right move is reading the log rather than writing it. Lessons are recorded as you state them: the skill never invents a lesson, softens one, or assigns blame beyond what you said. At project start or before a phase it reads back the entries whose tags match, which is the entire return on writing them. A lesson is one incident; recurring patterns become visible because the log accumulates, not because the skill generalizes.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads minutes written by somebody else — a contractor, a client, a project manager, a consultant — for the thing that matters and gets skipped: what they recorded about you. Minutes become the record if nobody objects within the period the contract or the covering note sets, so an action assigned to you that you did not accept, or a decision recorded that was not made, hardens into fact by silence. Trigger on "read these minutes", "the contractor sent minutes", "do we need to correct these", "did we agree to that", "minutes-reader", or minutes received from anybody else. Carries no contract terms; the objection period comes from the agreement or the minutes themselves. `meeting-notes-cleaner` turns your own raw notes into actions; this reads somebody else's finished document. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexKeeps one dated record of every pursuit the practice is chasing, from the first mention of a project — a call, a rumor, a client hint — through qualification, the go decision, the proposal, and the outcome, with the effort each pursuit consumed and the reason each loss happened. Leads every read-back with the pursuits consuming effort that have no go decision on record, because chasing without deciding is where business development money quietly goes. Trigger on "pipeline tracker", "what are we chasing", "track our pursuits", "proposals out right now", "did we ever hear back on that RFP", "what is our win rate", "pipeline-tracker", or a pile of pursuit emails handed over to make sense of. Carries no win-rate benchmarks, no hit-rate targets, and no probability weightings; the practice's history is the only pattern it reports.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexGoes back to a finished building and finds out what actually happened: what people do that the design did not expect, what they have changed, what they work around, and what performs differently from what was intended. Separates observation from opinion and from measurement, keeps the visit away from the questions that only produce politeness, and ends by naming who each finding is for, since a finding nobody receives is a visit nobody should have made. Trigger on "post occupancy", "POE", "how is the building working", "go back and see how it is used", "soft landings", "post-occupancy-evaluation", or a building in use with a question about it. Carries no benchmarks and no satisfaction scales; targets come from what the project set and measurements from whoever takes them. `lessons-learned` records what a project taught the practice; this finds out what the building is doing. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexKeeps one dated log of a project's issues, decisions, risks, and action items in docs/project/tracker.md. Trigger on "project tracker", "decision log", "issue log", "risk register", "action items", "track this", "log this decision", "what did we decide", "who owns this", "project-tracker", or when meeting notes produce action items worth keeping past the meeting. Every entry carries a date and a person; closed items move to a closed section rather than being deleted, so the log is also the project's history. The skill never invents a status, an owner, or a deadline. What it was not told, it records as unassigned and says so. Feeds on meeting-notes-cleaner output and is what generate-weekly-report reads. Not a construction schedule and not a CA log; RFIs and submittals have their own logs.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds an RFP or RFQ response around the evaluation criteria rather than around the practice's usual material: pulls every requirement and every question out of the document into a compliance matrix, follows the issuer's structure and numbering exactly, and checks before submission that every requirement has an answer and every page limit and format rule is met. Trigger on "respond to this RFP", "RFQ response", "build the proposal response", "do we answer everything in this RFP", "rfp-response-builder", or a solicitation handed over to answer. Carries no boilerplate and no standard firm material; everything comes from the practice's own content. For a federal qualifications package use `sf330-builder`; to decide whether to respond at all use `go-no-go-review` first. It does not decide the fee and does not replace the principal.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexAssembles a federal qualifications submission section by section, and does the part that decides the score: selecting the example projects and writing them so that each one demonstrates a specific evaluation criterion rather than being included because it is good work. Builds the team organisation against the projects named, keeps résumés consistent with the projects they claim, and checks every section against the solicitation's own instructions before submission. Trigger on "SF330", "federal qualifications package", "which projects go in Section F", "architect-engineer qualifications", "sf330-builder", or a federal solicitation handed over to answer. Carries no form instructions and no evaluation criteria; both come from the current form and the specific solicitation, which override any general guidance. It does not replace the principal, who signs.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexThe first hour on a new project: separates the decisions that have to be made before anything is drawn from the ones that can wait, because most projects reverse that and spend a month on the ones that could have waited. Establishes who decides what, what the project is actually being measured on, which unknowns block work and which do not, and what has to be commissioned now to arrive in time. Produces the decision list and the commissioning list, and hands each part off by name. Trigger on "we just won a project", "where do I start", "kick off", "what do we need before we start designing", "start-the-project", or a new commission with nothing set up. Carries no schedules, no fees and no checklists of deliverables; `drawing-checklist` holds what a phase produces and this holds what a phase has to decide. It does not replace the principal or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads subconsultant agreements against the prime agreement to find the gap the architect is standing in: obligations promised to the owner that were never passed down, insurance required upstream and not required downstream, payment terms that oblige payment before you are paid, and scope that appears in neither agreement. Works clause by clause across both documents and reports every mismatch with what each side says. Trigger on "review the subconsultant agreement", "does our consultant agreement match the prime", "flow down check", "who carries this obligation", "subconsultant-agreement-review", or a consultant agreement handed over before execution. Carries no standard-form text and no legal positions; both agreements come from you. It is not legal advice and does not replace the attorney or the Architect of Record. Read `contract-review` on the prime first.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a thread of emails or messages and answers the question that starts most disputes: what did we actually agree. Separates what was decided from what was proposed and never answered, tracks who was on the thread at each point since a decision made after somebody dropped off is a decision they never saw, finds the requests that were never replied to, and flags anything that quietly accepted scope, cost or time. Trigger on "read this thread", "what did we agree on this", "go through this email chain", "did we ever answer this", "thread-reader", or a chain of correspondence handed over. Carries no contract terms; whether something is binding comes from the agreement. `draft-email` writes one message; this reads a chain of them. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexKeeps one dated record of hours against fee at the level where it can still be acted on: by phase and by person rather than by project total, with the percentage of work complete recorded separately from the percentage of fee spent, since a project can be on budget and forty percent behind. Records what caused each overrun so the pattern separates from the incident, and flags the hours that should have been additional services before they are written off. Trigger on "utilization tracker", "are we over on this project", "hours against fee", "track the team's time by phase", "utilization-tracker", or a timesheet export handed over to make sense of. Carries no rates, no utilization targets and no benchmarks; the practice sets those. It does not replace the accounting system — it reads what that produces — and it does not replace `fee-tracker`, which follows the fee itself.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads any calculation an architect is handed — structural, thermal, egress, drainage, load, acoustic — and checks the part an architect can and should check: the inputs, the assumptions, the standard it was worked to, and the version of the design it was worked from. The arithmetic is sealed by somebody and is not the architect's to verify; the inputs frequently describe a building that has changed since. Trigger on "read this calculation", "they sent calcs", "what did the engineer assume here", "is this calc still valid", "calculation-reader", or any calculation handed over. Carries no formulas, values or code limits. It verifies no arithmetic, has no engineering opinion, and does not replace the engineer of record or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a drawing from any consultant — structural, mechanical, electrical, plumbing, fire protection, civil, landscape, acoustic, kitchen, security — against the architectural set, from the architect's side. Checks the things that go wrong the same way whatever the discipline: the background it was drawn on, the grids and levels, what it lands in that has to stay clear, what it defers to somebody else, and where the two sets simply disagree. Trigger on "review the consultant drawings", "read this engineer's drawing", "do these agree with our plans", "they issued a set, what do we check", "consultant-drawing-review", or any consultant's drawing handed over. Carries no engineering values and checks no engineering. `mep-review`, `structural-drawing-review` and `civil-drawing-review` go deeper on those three; this is the one that works for the disciplines that have no skill of their own. It does not replace the engineers or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWorks acoustic separation between two spaces as a whole rather than as a wall or floor rating: establishes what the source is and what the receiver needs, then traces every path sound can take between them, because the assembly's tested rating describes the direct path only and the built result is set by whatever flanks around it. Names the structural decisions that have to be made early and cannot be fixed later. Trigger on "acoustic separation", "STC between these units", "impact noise from above", "flanking", "why is this wall not working acoustically", "design-acoustic-separation", or two spaces with a noise problem between them. Carries no ratings, no laboratory values and no criteria; the target comes from the code, the brief or the acoustician, and every assembly value is a tested figure you cite. It is not acoustic engineering and does not replace the acoustician or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexLays out an electrical, communications or service entrance room around the working clearances that surround the equipment rather than around the equipment itself, because those clearances are code, they are volumes, and they appear on no architectural drawing by default. Works the utility's own requirements separately from the code's, since a service entrance room is designed to the utility's standard and they will refuse a room that meets the code and not their manual. Trigger on "electrical room layout", "how big does the switchgear room need to be", "working clearance in front of the panel", "service entrance room", "transformer vault", "design-electrical-room", or an electrical equipment schedule with a room to put it in. Carries no clearance dimensions, no equipment sizes and no utility requirements. It does not do electrical design and does not replace the electrical engineer or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexHolds the architectural space an elevator installation needs from the consultant's or manufacturer's data: the hoistway, the pit below the lowest landing, the overrun above the highest, the machine and controller wherever the product puts them, and the lobby and door dimensions at every level. Works the constraints that decide the building — what the pit does to the foundation, what the overrun does to the roof or the height limit, and where the machine has to be if there is no machine room. Trigger on "elevator pit depth", "lift overrun", "machine room-less", "how big is the hoistway", "elevator shaft coordination", "design-elevator", or an elevator specification handed over to fit into a building. Carries no dimensions, no capacities, no speeds and no code requirements; every one comes from the manufacturer, the elevator consultant, or the code you quote. It does not do traffic analysis and does not replace the elevator consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexLays out a mechanical plant room from the equipment schedule the engineer gives you, and adds the four things that make it bigger than the equipment: the service clearances each unit needs, the route to get equipment in during construction and out at replacement, the air the room itself has to take in and exhaust, and the connections that leave it. Reports the required footprint and height against what is drawn. Trigger on "size the mechanical room", "plant room layout", "will the AHU fit", "how do we get the chiller in", "mechanical room design", "design-mechanical-room", or an equipment schedule handed over with a room to put it in. Carries no equipment dimensions, no clearances, no ventilation rates and no code requirements; all come from the engineer, the manufacturer and the code text you quote. It does not select or size equipment and does not replace the MEP engineer or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads any product or equipment data sheet and pulls out the six things a building has to provide for it: the space it occupies, the clearance it needs on each side to be serviced, the route to get it in and out, the services it needs and from where, what it weighs and what carries it, and what it does to the room around it in heat, noise and vibration. Works for a rooftop unit, a lift, a range, a transformer, a door closer or a light fitting. Trigger on "read this cut sheet", "what does this unit need", "they sent product data", "will this fit", "equipment-reader", or a data sheet handed over with a question about space. Carries no dimensions or clearances of its own: every figure comes off the sheet, and a figure absent from the sheet is reported missing rather than assumed from a similar product. It does not select or size equipment and does not replace the engineers or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReviews a mechanical, electrical, and plumbing drawing set against the architectural and structural drawings across eight coordination axes: shafts and risers, ceiling and plenum depth, equipment rooms, horizontal distribution, intake and exhaust, service entries, maintenance access, and document coordination. Trigger on "MEP review", "MEP coordination", "check the MEP set", "will the ducts fit", "plenum depth", "shaft coordination", "is there room for the equipment", or a shared MEP sheet with a fit question. The skill supplies no dimensions of its own: every clearance, depth, and area comes from the drawings or from you. Writes a dated review file and appends to a project index, with every unverified axis counted on the face of the review. Does not size equipment and does not replace the Engineer of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWorks through every penetration of a rated, acoustic or structural assembly and asks the three questions that get answered separately and should be answered together: what performance the assembly has to keep, what physically closes the hole, and whether a listed or tested system exists for that penetrant in that assembly. Builds the register across disciplines, since penetrations are made by trades who never see each other's drawings. Trigger on "penetration review", "firestopping check", "what closes this hole", "acoustic penetrations", "sleeve schedule review", "penetration-review", or an MEP set laid over the rated wall plan. Carries no listings, no ratings and no acoustic values; the required performance comes from your code analysis and every closure is a listed or tested system you cite. For the assembly's own continuity use `design-fire-barrier`; for air and water use `air-barrier-trace`. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads any engineer's or consultant's schedule — mechanical equipment, plumbing fixtures, electrical panels, lighting, fire protection devices, structural members — and translates it into the architectural consequences: what has to fit somewhere, what needs a room, what needs access, what needs a route, what lands on a wall or a ceiling, and what weighs something the structure has to carry. Trigger on "read this equipment schedule", "what does this mechanical schedule mean for us", "they sent a schedule", "schedule-reader", or any consultant's schedule handed over. Carries no dimensions, capacities or clearances; every figure comes from the schedule or the product data. Not to be confused with `schedule-review`, which reads a contractor's construction programme — a different document entirely. `explain-panel-schedule` goes deeper on one electrical panel. It does not check the engineering and does not replace the engineers or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a structural set the way an architect has to: not to check the engineering, but to find where the structure and the architecture disagree, where the frame lands in a space that has to stay clear, where a member's depth eats a ceiling, where the drawings defer something to a delegated design nobody has scoped, and where the structural set assumes an architectural layout that has since changed. Reports every conflict with both values and rules on neither. Trigger on "review the structural drawings", "does the structure work with the plan", "beam depth coordination", "is this deferred to a delegated design", "structural-drawing-review", or a structural set issued for coordination. Carries no loads, no spans and no code requirements; it does not check or second-guess the engineering. The counterpart for MEP is `mep-review`. It does not replace the structural engineer or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds a programme adjacency matrix from movement and constraint rather than from stated preference: takes the room list, asks for each pair what actually travels between them and how often, separates a required adjacency from a desired one and from a required separation, then reads the finished matrix for the rooms that want to be everywhere at once and the conflicts that no plan can satisfy. Trigger on "adjacency matrix", "bubble diagram", "which rooms need to be near each other", "programme relationships", "adjacency-matrix", or a room list handed over with a request for how it should be organised. Carries no adjacency conventions for any building type, because who has to be near whom is the client's operation and not a rule. Reads a room list from `space-program` where one exists and does not duplicate its area tracking. It does not lay out a plan and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds an agenda for any project meeting from the decisions it has to produce rather than from the topics somebody wants to raise. Establishes who has to be there for each decision and whether they are coming, what has to be sent in advance for a decision to be possible, and what is being discussed with nobody present who can decide it — which is how a meeting produces a follow-up meeting. Trigger on "agenda for tomorrow", "what should we cover in this meeting", "build the agenda", "prep for the client meeting", "agenda-builder", or a meeting coming up with nothing prepared. Carries no meeting formats and no standard agendas; the items come from what this project actually needs settled. `meeting-notes-cleaner` handles what comes out of the meeting; this handles what goes in. It does not replace the principal or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexTraces each of the four enclosure control layers, air first, then water, vapor, and thermal, around a building section as one continuous line, and reports every joint where that line changes material, changes plane, or is crossed by something: foundation, slab edge, wall base, floor lines, window and door openings, corners and cladding changes, parapets and eaves, roof level changes, and every penetration. Each joint records what carries the layer on either side, what makes the connection, and which drawing shows it. Trigger on "air barrier continuity", "trace the air barrier", "control layer check", "where does the air barrier break", "is the WRB continuous", "air-barrier-trace", or a wall section handed over with a continuity question. The drawings, the layer assignments, and any airtightness target come from the user; the skill supplies the joint sequence and the questions asked at each one, and never names a membrane, tape, sealant, or leakage rate.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodex