Showing 53431–53460 of 77205 skills
Keeps one dated record of a discretionary land use approval, which behaves nothing like a permit: the decision-maker is a body that meets on a calendar, the outcome is negotiated rather than checked, and the conditions attached at the end become obligations the project carries for its life. Logs every submission, every hearing, every commitment made in a room, and every condition with what discharges it and who owns it. Trigger on "entitlement tracker", "track the rezoning", "planning approval log", "what did we commit to at the hearing", "conditions of approval", "entitlement-tracker", or a discretionary application handed over to keep track of. Carries no process, no timelines and no hearing calendars; all come from the jurisdiction. It does not track building permits — `permit-tracker` does — and does not replace the land use attorney, the planner, or the Architect of Record.
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
Reads 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
Plans and records a measured survey of an existing building so that every dimension later designed against carries its provenance: what to capture before going, how to close a measurement so errors are caught on site rather than in the office, and the discipline of marking every line as measured, taken from a record drawing, or assumed. Produces the record and the list of what still has to be opened up or verified. Trigger on "measure the existing building", "as-built survey", "existing conditions", "we only have the old drawings", "what do I measure on the site visit", "existing-conditions-survey", or a renovation starting with no reliable information. Carries no tolerances and no survey standards; the level of accuracy needed comes from what the drawings will be used for. It is not a land survey — `survey-review` reads one — and not a structural, hazardous materials, or condition assessment, each of which is a specialist's and is named as a hand-off.
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
Reads a geotechnical report from the architect's side: separates what was actually investigated from what was inferred between boreholes, pulls out every recommendation that becomes a design obligation, finds the conditions the report makes contingent on something happening later, and reports what it means for the building rather than for the foundation engineer. Trigger on "review the geotech report", "what does this soils report mean for us", "read the geotechnical recommendations", "borehole log review", "geotech-report-review", or a soils report handed over at the start of design. Carries no bearing values, no soil classifications and no design parameters; every figure comes from the report, quoted. It is not geotechnical engineering, does not verify a recommendation, and does not replace the geotechnical engineer, the structural engineer, or the Architect of Record. For one recommendation in plain English use `/explain-soils`.
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
Builds and maintains one file per project that records the limits a code sets, each with the clause it came from, so the checking skills stop asking for the same number on every run. Trigger on "jurisdiction profile", "set up the code profile", "record the code limits", "reuse my code values", "where do the limits come from", or a request to fill in or extend an existing profile. Works in any jurisdiction. The profile ships empty: every value is typed, pasted from the clause, or read out of a file the user names, and a row without a clause is marked as such rather than being treated as verified. Does not look a code value up, does not carry a default, and does not decide which code governs.
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
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 a marked-up drawing — a redline, a scanned sketch over a print, a PDF with comments, a photograph of a drawing somebody wrote on — and turns it into a numbered list of what each mark asks for, who it is for, and whether it can be acted on as drawn. Separates the marks that instruct from the marks that ask, and flags every mark whose meaning cannot be determined, because a guessed markup is worse than an unread one. Trigger on "read this redline", "they marked up the drawing", "what does this markup say", "turn these comments into a list", "markup-reader", or a marked drawing handed over. Carries no conventions: what a colour or a symbol means is the office's or the marker's, and it is asked rather than assumed. `drawing-diff` compares two issued revisions; this reads what somebody wrote on one. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Reviews 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
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
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
Audits a building model for the practices that decide whether it stays usable: what the model is actually for and whether it is being built to that, whether geometry is modeled or drafted over, whether the data the project committed to deliver is present and consistent, what is warning or duplicated, and whether the file can be shared with consultants without an explanation. Reports by frequency and separates what will get worse from what is merely untidy. Trigger on "model health check", "audit this Revit model", "why is the model so slow", "is the model ready to share", "BIM standards audit", "model-health-audit", or a model handed over before an exchange. Carries no software-specific counts, no thresholds and no office BIM standard; the standard and the delivery requirements come from your BEP or your office. It reviews practice rather than drawings — `drawing-standards-audit` reads the sheets. It does not replace the BIM manager or the Architect of Record.
DavidCho1999/archaiflow-skills
Works the organizing idea of a scheme rather than its appearance: states the parti in one sentence, tests whether the plan actually obeys it, finds the places it breaks and asks whether each break is a compromise or a second idea competing with the first, and checks the parti against the constraints it has to survive. Generates alternatives only as different organizing ideas from the same constraints, never as variations of one. Trigger on "parti", "what is the organizing idea here", "is this scheme actually about anything", "concept diagram", "the plan feels arbitrary", "parti-study", or a scheme handed over with a question about what holds it together. Carries no formal vocabulary and no house style; the idea is yours and the skill tests whether the drawing keeps it. It does not critique the design — `design-critic` and `independent-critic` do that, deliberately separately — and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Works 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
Keeps one dated log of every approval a project has to obtain, from the agencies you name rather than from an assumed list: what each permit is, which agency issues it, what it depends on, who owns it, what has been submitted and when, every comment received and its response, and every expiry. Reads back what is on the critical path and what is waiting on somebody. Trigger on "permit tracker", "track the approvals", "what permits do we need", "permit log", "who owns this approval", "when does the permit expire", "permit-tracker", or a list of agencies named with a request to keep track of them. Carries no agency lists, no review durations, no fee schedules and no permit types; every one comes from the jurisdiction, because they differ between adjacent municipalities and change without notice. It does not file anything, does not predict a duration, and does not replace the expediter, the code consultant, or the Architect of Record.
DavidCho1999/archaiflow-skills
Reads any photograph an architect ends up with — a site visit, an existing building, a defect somebody wants explained, a phone picture from a client, a product on a shelf — and separates what is visible from what is inferred, because a photograph is the most persuasive and least complete document on a project. Establishes when and where it was taken and which way the camera faced before reading anything, since a photograph with no location is evidence of nothing. Trigger on "read this photo", "what am I looking at here", "the client sent a picture", "is this a problem", "photo-reader", or an image handed over with a question. Carries no dimensions and measures nothing from an image. It diagnoses nothing: a photograph of a stain is not a diagnosis, and `leak-triage` takes it from there. 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
Turns a plan check or plan review comment set into a response matrix that answers every comment individually and on the record: splits comments that contain more than one question, sorts each into agreed, clarification, or disagreement, points every response at the specific sheet and detail that changed, and keeps the disagreements civil and evidenced because those are the ones that get read twice. Trigger on "plan check comments", "respond to the plan reviewer", "correction letter", "plan review response", "resubmittal response matrix", "plan-check-response-builder", or a set of reviewer comments pasted with a request to answer them. Carries no code positions of its own and never argues a clause from memory; every response either cites the drawing that changed or quotes the code text you supply. For a letter to the department rather than a comment matrix use `/draft-letter`; for tracking the submission itself use `permit-tracker`.
DavidCho1999/archaiflow-skills
Reads any floor plan you hand it and reports three things separately: what is drawn, what a plan of this kind should show and does not, and what the plan commits to without saying so. Works whatever the project type, whatever the phase, and whether the plan is yours, a consultant's, a client's previous architect's, or one found in a property listing. Trigger on "read this plan", "what do you make of this floor plan", "review this layout", "they sent us a plan", "plan-review", or a plan handed over with no particular question attached. Carries no dimensions and no standards; anything measured comes from what is on the drawing. `design-critic` judges a design, `code-compliance-review` audits against eight code axes, and `circulation-study` traces the journeys; this reads the drawing first, which is what the other three assume has happened. It does not replace the Architect of Record.
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
Critiques the user's scheme through lenses extracted from reference projects the user supplies, instead of a generic rubric. Trigger on "critique this through these precedents", "hold my scheme against these references", "critique this like these projects", "precedent-critique", or a scheme shared alongside two or more admired projects. The user supplies both sides: their own scheme (concept text, plans, sections, images) and material for each reference (project descriptions, photographs, drawings, published texts). The skill derives three to five lenses from the supplied material, confirms them with the user, then reads the scheme through each lens. It never characterizes a firm or a project from memory: a name without material stops the run. Divergence from the references is reported and questioned, never scored. It does not design, does not rank, and does not replace the designer's judgment or a design review.
DavidCho1999/archaiflow-skills
Reads any brief or programme document — a client's schedule of accommodation, a spreadsheet from a user group, a consultant's brief, a previous architect's programme — and establishes what its numbers actually are before anybody designs against them: which are measured, which are standards, which are wishes, what area basis they are on, whether the total is the sum of the parts, and what the document counts that a building would not. Trigger on "read this brief", "they sent a schedule of accommodation", "what does this programme actually say", "is this area realistic", "program-reader", or a brief handed over. Carries no area standards and no benchmarks; the basis comes from the document or from `area-measurement`. `brief-review` interrogates a brief for gaps and contradictions; this reads one for what its figures rest on, and it runs first. 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
Turns a project deck PDF, renders, site photos or drawing images into one web page that reads on a phone and can be sent as a link. Uses only the words and numbers in the files or typed in the chat, lists what it found and asks how each part should be shown (full width or grid, side by side or slider, one scroll or one section per screen) before building, keeps PDF drawings sharp when zoomed, and writes the page as one index.html that a drag-and-drop host can put online. Trigger on "make this a website", "project website", "send the deck as a link", "shareable project page", "a page the client can open on their phone", "project-website-builder", or files attached with a request for something a client can open. It does not write project copy, and it does not put anything online by itself.
DavidCho1999/archaiflow-skills
Maintains a project punch list in docs/construction/punch-list.md. Trigger on "punch list", "punch item", "snag list", "deficiency list", "defect list", "punch walk", "punch-list", or a pasted site visit report whose observations should become tracked items. Each item carries a location, a description, the responsible trade, the date raised, its source, and a status that separates completed from verified, because a contractor marking work done is not the same as the architect seeing it done. The skill never invents an item, a responsible party, or a completion; what it was not told stays open. Feeds on create-site-visit-report output. It does not decide substantial completion and does not certify anything; those are contract acts.
DavidCho1999/archaiflow-skills
Keeps one dated RFI log and reads what the log says that no single RFI does: every RFI with who owns it, when it arrived, when the contract required an answer, when the answer went, and how it was classified, plus the running counts that reveal a pattern — a sheet generating a stream of questions, a contractor sending already-answered ones, a consultant consistently late, a set of clarifications quietly accumulating into a change. Trigger on "RFI log", "RFI tracker", "how many RFIs are open", "are we late on RFI responses", "which drawings are generating RFIs", "rfi-tracker", or an RFI register handed over to keep. Carries no response periods and no classifications of its own; the contract sets the turnaround and each RFI's class comes from whoever answered it. It does not answer RFIs — `/draft-rfi-response` does — and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills