Showing 53341–53370 of 77205 skills
Reads a curtain wall or unitised facade submittal package as a system rather than as a set of sections: checks that the drainage and pressure-equalisation strategy is coherent through every joint, that the thermal break line is continuous and lands where the wall's insulation does, that movement is provided for at stack joints and anchors, that the tested system and the drawn system are the same system, and that the interfaces to every adjoining assembly have an owner. Trigger on "curtain wall shop drawing review", "unitised facade submittal", "review the glazing submittal", "stack joint detail review", "is the thermal break continuous", "curtain-wall-submittal-review", or a facade shop drawing package handed over for comment. Carries no performance criteria, no test values and no tolerances; all come from the specification and the test reports, quoted. It reviews and comments, does not stamp or approve, and does not replace the facade engineer or the Architect of Record.
DavidCho1999/archaiflow-skills
Works a balcony, terrace or projecting deck as the place where the envelope is deliberately broken: something structural passes through the insulation, the waterproofing has to turn up and drain away from a door, and a guard has to fix to whatever is left. Establishes the structural relationship first, since a cantilevered slab, a thermally broken connection and an independently supported balcony are three different buildings, then works the falls, the threshold, the drainage and the guard. Trigger on "balcony detail", "cantilever slab thermal bridge", "terrace over occupied space", "balcony door threshold", "where does the balcony drain", "design-balcony", or a projecting floor with a wall behind it. Carries no dimensions, no thermal values, no loads and no code requirements; guard and drainage requirements are code you quote and the structure is the engineer's. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Builds a below-grade wall or slab assembly from the water condition first: takes the groundwater regime, the soil, the structure, how the space below grade will be used and whether the waterproofing can ever be reached again, then places the water, thermal and vapor control layers in an order, gives every layer a job, and works the joints, penetrations and the at-grade transition where below-grade work actually fails. Trigger on "below grade waterproofing", "basement wall build-up", "foundation wall assembly", "slab on grade vapor barrier", "blindside waterproofing", "design-below-grade-assembly", or a foundation wall and a water table named with a request for what goes between them. Supplies the ordering logic and the questions each condition has to answer; supplies no thickness, no permeance, no hydrostatic head, no code requirement and no proprietary product. It does not size drainage, does not do geotechnical or structural work, and does not replace the waterproofing consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
The door into envelope work, and the step usually skipped: before any assembly is built up, decide how many envelope types the building actually has, which face gets which, where the junctions between them fall, and what each one has to achieve. Produces the schedule of types and junctions that the assembly and junction skills then execute against, and hands each part off by name. Trigger on "design the envelope", "how many wall types do we need", "what should this facade be", "envelope strategy", "where do the assemblies change", "design-envelope", or an envelope scope with no strategy behind it. Carries no R-values, no assemblies and no code minimums; performance requirements come from the code and the brief you quote. It builds nothing itself — `design-wall-assembly`, `design-roof-assembly` and the junction skills do — and does not replace the enclosure consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Works movement in the enclosure as two questions rather than one: where the joints have to be, given the movements you can name and where they accumulate, and then how each of the four control layers (water, air, vapor, thermal) crosses a gap that opens and closes for the life of the building. Trigger on "expansion joint", "movement joint", "control joint", "where do the joints go", "building separation joint", "how does the air barrier cross a joint", "design-expansion-joint", or a long facade or a structural break named with a request for how the enclosure handles movement. Supplies the reasoning about movement sources, accumulation and joint hierarchy, and the questions each crossing has to answer; supplies no joint spacing, no movement coefficient, no joint width, no code requirement and no proprietary product. It does no structural or thermal calculation and does not replace the enclosure consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Works a parapet as the junction of two assemblies rather than as a wall that continues past the roof: takes the wall build-up and the roof build-up you already have, then carries each of the four control layers (water, air, vapor, thermal) up the inside face, over the top and down the outside, naming where each one transfers from one assembly to the other and what happens at the coping, the through-wall flashing, the corners and every interruption. Trigger on "design a parapet", "parapet detail", "coping", "where does the air barrier turn at the roof", "through-wall flashing at the parapet", "parapet thermal bridge", "design-parapet", or a wall and a roof named with a request for how they meet at the top. Supplies the ordering and transfer logic and the questions each condition has to answer; supplies no height, no thickness, no slope, no code requirement and no proprietary product. Requires the two assemblies as input and does not design either of them.
DavidCho1999/archaiflow-skills
Builds a low-slope or steep-slope roof assembly from what the roof has to do rather than from a remembered stack: takes the membrane or covering, the deck, the climate, the interior humidity, the equipment landing on it and the slope you have to work with, then places the four control layers (water, air, vapor, thermal) in an order, gives every layer a stated job, and works the curbs, drains, penetrations and edges where roofs actually leak. Trigger on "design a roof assembly", "roof build-up", "compact roof", "what goes above the deck", "insulation above or below the deck", "vented or unvented roof", "design-roof-assembly", or a membrane and a deck named with a request for what sits between them. Supplies the ordering logic and the questions each condition has to answer; supplies no R-value, no permeance, no slope minimum, no code requirement and no proprietary product. The arithmetic belongs to condensation-check and the continuity audit to air-barrier-trace, both of which this hands off to.
DavidCho1999/archaiflow-skills
Works roof drainage as the architectural half of a problem the plumbing engineer sizes: where the falls come from and what they cost the build-up, where the drains land against the structure and the spaces below, where the secondary drainage goes and whether anyone would notice it running, and what the roof weighs if the primary drains block. Trigger on "roof drainage", "where do the drains go", "tapered insulation layout", "overflow scuppers", "is the roof ponding", "design-roof-drainage", or a roof plan with a question about falls. Carries no drain sizes, no rainfall intensities, no slope minimums and no code requirements; sizing is the plumbing engineer's against the code you quote, and the ponding load is the structural engineer's. `design-roof-assembly` builds the stack and names this as out of its scope. It does not replace the engineers or the Architect of Record.
DavidCho1999/archaiflow-skills
Builds an exterior wall assembly from what the wall has to do rather than from a remembered stack: takes the cladding, the structure, the climate, the fire and acoustic demands and the drying direction you state, then places the four control layers (water, air, vapor, thermal) in an order, gives every layer a stated job, and works each interface where two layers meet and each transition where the wall stops. Trigger on "design a wall assembly", "wall build-up", "what goes in this wall", "layer the exterior wall", "where does the air barrier go", "rainscreen build-up", "design-wall-assembly", or a cladding and a structure named with a request for what sits between them. Supplies the ordering logic and the questions each interface has to answer; supplies no R-value, no permeance, no code minimum and no proprietary product. The arithmetic on the finished stack belongs to condensation-check and the continuity audit to air-barrier-trace, both of which this hands off to.
DavidCho1999/archaiflow-skills
Details the three sides of an opening as a sequence rather than as three sections: takes the wall assembly, the window type and how it is anchored, then works the head, the jamb and the sill in the order the trades actually build them, laps each control layer over the one below it, and names where water that gets past the window is collected and put back out. Trigger on "window head jamb sill", "window perimeter detail", "sill pan", "flashing sequence at an opening", "how does the air barrier close at a window", "punched opening detail", "design-window-perimeter", or a window and a wall build-up named with a request for how they meet. Supplies the sequencing and lap logic and the questions each side has to answer; supplies no dimension, no shim space, no sealant joint size, no code requirement and no proprietary product. Requires the wall assembly as input and does not design it. It does no structural work and does not replace the enclosure consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Keeps one dated record of a project's embodied carbon as the design changes: quantities from your own take-off, factors from the data source you name, and the result kept per element and per life-cycle stage rather than as one number, because a single figure hides which decision moved it. Records the boundary and the data vintage on every entry, since two projects' figures are comparable only when both are stated. Trigger on "embodied carbon", "track the carbon on this design", "whole life carbon", "EPD", "upfront carbon", "A1-A3", "embodied-carbon-tracker", or a material change with a question about its carbon. Carries no emission factors and no benchmarks; every factor comes from an EPD or a database you name, with its vintage. `decarbonization-strategist` plans the operational path over years; this counts what the materials carry. It is not an LCA and does not replace the sustainability consultant.
DavidCho1999/archaiflow-skills
Builds the envelope checklist for one project rather than handing over a generic one: takes the assemblies this building actually has and the phase it is at, and produces what should be resolved by now, what can still wait, and what is already late. Works from the junction list rather than from the assemblies, because assemblies get drawn and junctions get discovered. Trigger on "envelope checklist", "what should be resolved by DD", "are we ready to issue the envelope", "what have we missed on the facade", "envelope-checklist", or an envelope scope at a phase change. Carries no standard checklist and no performance values; the items come from the assemblies and junctions this project has. `drawing-checklist` covers the drawing set by phase; this covers the envelope by what it is made of. It does not replace the enclosure consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Compares two versions of an envelope assembly or detail and reports what the change does rather than what it looks like: which control layer moved, what continuity was gained or lost, which junction details are now wrong, and whether the drying direction changed. Built for the moment a contractor proposes an alternate, a manufacturer's detail replaces yours, or a value-engineering round comes back, because those changes arrive one layer at a time and their consequences arrive at the junctions. Trigger on "what changed in this assembly", "they proposed a different build-up", "compare these two sections", "is this substitution equivalent", "envelope-diff", or two versions of an envelope construction handed over together. Carries no values; every figure comes with the versions. `document-diff` compares written documents and `drawing-diff` drawing revisions; this compares what an assembly does. It does not replace the enclosure consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Works out how every part of a building's envelope will be reached after it is built: cleaned, inspected, repaired, and, for glass, replaced. Inventories the envelope by zone, holds candidate access methods against each one — reach from grade, rope descent, davits, a building maintenance unit, interior access — and reports what each method demands of the design now: roof space, structure, anchors, parapets, and ground kept clear. Trigger on "facade access", "how do we clean this", "window washing", "BMU", "davits", "rope access", "facade-access-study", "how does the glass get replaced", or a tall or complex envelope with no maintenance story. The zoning of the envelope and the demands table are the skill's method; every load, every regulation, and every equipment figure comes from elsewhere: anchor and davit loads are the structural engineer's, the rules for suspended access are regulatory text the user quotes, and reach figures come from the equipment's own data.
DavidCho1999/archaiflow-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
Reviews 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
Builds 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
Reads 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
Scores 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
Keeps 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
Reads 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
Keeps 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
Goes 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
Keeps 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
Builds 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
Assembles 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
The 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
Reads 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
Reads 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
Keeps 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