Explore skills
Showing 53161–53190 of 77079 skills
Reads a land survey the way a design team has to: establishes what kind of survey it is and therefore what it is certified to show, checks it against what the project actually needs, and reports the gaps before a scheme gets built on top of them. Separates what was measured from what was compiled from records, works the boundary, the encumbrances, the topography, the utilities and the datum in that order, and flags every place the drawing shows a line that no instrument supports. Trigger on "review the survey", "is this survey adequate", "what's missing from this survey", "ALTA survey review", "survey-review", or a survey handed over at the start of a project. Carries no survey standards and no certification requirements; the standard the survey was made to comes from its own certificate. It is not a survey, does not verify a boundary, and does not replace the surveyor or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds a variance or discretionary relief application around the findings the deciding body is legally required to make, rather than around why the project wants it: extracts each required finding from the jurisdiction's own criteria, works the evidence for each one separately, tests whether the hardship claimed is of the kind the criteria recognise, and assembles the record so the decision can survive an appeal. Trigger on "variance request", "zoning relief application", "hardship findings", "special exception", "what do we have to prove for a variance", "variance-request-builder", or a zoning requirement named as unmeetable with a request to seek relief. Carries no criteria, no precedent and no legal positions; the findings come from the jurisdiction's own text. It does not give legal advice and does not replace the land use attorney, the planner, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexKeeps one dated log of every change from the moment it is first raised, not from the moment it becomes a change order: records where each one came from, what instrument carried it, its cost and time position at every stage, and who it is sitting with, so that the work directed but not yet priced and the changes stalled between proposal and execution are both visible. Reports the running total against the contingency and the count of changes proceeding on direction alone. Trigger on "change order log", "track changes", "how much have we spent of the contingency", "what changes are outstanding", "work proceeding without a change order", "change-order-tracker", or a change register handed over to keep. Carries no cost data, no markup rates and no contract periods; all come from the contract and the proposals. It does not price, review, or negotiate a change — `change-order-review` does that for one — and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds and tracks the closeout deliverables list in docs/construction/closeout.md: O&M manuals, warranties, test and inspection reports, record documents, spare parts and attic stock, training, each with the spec section that requires it. Trigger on "closeout", "closeout checklist", "O&M manuals", "warranties", "attic stock", "record drawings", "as-builts", "turnover package", "handover", "closeout-check", or the end of construction approaching. The list is built by reading the closeout requirements out of your spec book or typed by you; the skill never invents a deliverable a spec did not require. Received items are recorded with dates; the report leads with what is outstanding, by division. Whether the contract's closeout conditions are met is the architect's certification, not this skill's.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexKeeps one dated log of conflicts between disciplines and follows each to the only ending that counts: both sets showing the same thing. Records which two documents disagree, what each says, who resolves it, and then the step everyone skips — whether the agreed answer reached both drawings and at which revision. Consolidates what the review skills find rather than leaving each discipline's findings in its own report. Trigger on "coordination log", "track the clashes", "did that conflict get fixed in both sets", "coordination issues", "coordination-log", or the output of a discipline review handed over to keep. Carries no positions of its own; the conflicts come from `mep-review`, `structural-drawing-review`, `civil-drawing-review`, `penetration-review` and `design-ceiling`. It does not resolve anything and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads any document with money in it — an estimate, a budget, a cost plan, a supplier quote, a contractor's proposal, a client's own number — and does the part an architect can do without being an estimator: establish what it covers, what it excludes, what it assumed, and what date it is on. Those four decide almost every argument about a price, and none of them require checking the arithmetic. Trigger on "read this estimate", "what does this quote actually include", "the budget came back", "is this number comparable", "cost-reader", or any priced document handed over. Carries no rates, no benchmarks and no cost data; `/lookup-cost` quotes a benchmark with its source and `senior-cost-estimator` gives judgement. It checks no arithmetic, prices nothing, and does not replace the estimator, the contractor, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexSorts a delay before it becomes a claim: establishes what is actually late against what baseline, whether the delayed activity was ever controlling the completion date, who caused it, and whether the contract makes it compensable, excusable, or neither. Separates the three questions that get merged — is it late, is it critical, and whose is it — because a delay can be real and cost nobody anything. Trigger on "we are behind", "the contractor says we delayed them", "is this a critical delay", "do we owe them time", "delay-triage", or a delay asserted with a letter likely to follow. Carries no contract terms and no float conventions; entitlement comes from the executed agreement you quote. It is not a delay analysis, which is forensic and has a methodology, and it does not replace the scheduler, the attorney, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexCompares two versions of a written document — an agreement, a specification section, a programme, a code analysis, an owner's requirements — and reports every change, not the ones the covering note listed. Separates a wording change from a change in obligation, flags every deletion because deletions are what a redline is worst at showing, and reports what moved rather than changed, since relocated text reads as unchanged in most comparisons. Trigger on "what changed between these two versions", "compare these contracts", "diff this spec section", "they sent a revised agreement", "document-diff", or two versions of anything written handed over together. Carries no view on what any clause should say; `contract-review` and `spec-review` read one version on its merits. It is not legal advice and does not replace the attorney or the Architect of Record. For drawings use `drawing-diff`.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexMaintains a drawing issue log in docs/drawings/log.md: every sheet in the set, its current revision, and every dated issuance with its purpose. Trigger on "drawing log", "issue log", "sheet log", "revision log", "what rev is", "when did we issue", "drawing register", "drawing-log", or a request to record that a set went out. The sheet list can be seeded from a drawing-set-bookmarker index or typed; revisions and issue dates come from you, never from a guess. Superseded sheets are marked, not deleted, so the log answers what was in force on any past date. It records what was issued to whom; the cover sheet for a package is create-transmittal's job, and what changed inside a sheet is drawing-diff's.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexSweeps a whole drawing set for the conventions that decide whether it can be read: whether the sheet index matches the sheets, whether every reference lands on something that exists, whether the title block is complete and consistent, whether symbols and abbreviations are used as the legend defines them, and whether the same information appears twice with two answers. Reports by frequency so the systematic problems separate from the isolated ones. Trigger on "drawing standards audit", "check the set for consistency", "do the references resolve", "title block check", "is this set ready to issue", "drawing-standards-audit", or a set handed over before issue. Carries no office standard, no layer convention and no line weight table; the standard comes from your office or the project's own set. It reviews conventions rather than content — `drawing-checklist` covers what a phase should contain and `spec-review` covers the book. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads 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
Stars: 1Claude CodeCodexAudits 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
Stars: 1Claude CodeCodexReads 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
Stars: 1Claude CodeCodexMaintains 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
Stars: 1Claude CodeCodexKeeps 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
Stars: 1Claude CodeCodexBuilds a drawing schedule of any type — door, window, finish, room, wall type, equipment — by settling the column set before any row is filled, since the columns are what the schedule is and adding one later means revisiting every row. Takes the items from your drawings or model, fills only what you supply, marks every gap rather than defaulting it, and checks the finished schedule against the plans for items scheduled but not drawn and drawn but not scheduled. Trigger on "build a door schedule", "window schedule", "finish schedule", "room data sheet", "wall type schedule", "make a schedule from these drawings", "schedule-builder", or a request to assemble any drawing schedule. Carries no default column sets, no hardware sets, no fire ratings and no product data; the columns come from your office standard and every value comes from you. For extracting a schedule that already exists in a PDF use `schedule-extractor`. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a contractor's construction schedule from the design team's side rather than as a planner: finds every activity that depends on the architect, the consultants or the owner and checks whether the durations allowed match the contract, traces the critical path to see what actually controls the end date, looks for the logic that makes a delay claim inevitable, and separates what is a genuine concern from what is only unfamiliar. Trigger on "review the contractor's schedule", "CPM schedule review", "is this baseline reasonable", "submittal durations in the schedule", "schedule update review", "schedule-review", or a programme submitted for comment. Carries no durations, no productivity rates and no float conventions; the contract sets the review periods and the schedule specification sets the rules. It is not planning software, does not re-plan the work, does not opine on means and methods, and does not replace the scheduler or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a complete drawing set rather than a drawing: works out what phase it actually is regardless of what the title block claims, what is in it and what is missing for that phase, which disciplines are present and at what revision, how the set is organised, and what somebody receiving it would have to ask about first. Built for the set that arrives from somewhere else — a previous architect, a client, a design-build partner, a project you are taking over. Trigger on "read this set", "what have we been given", "we are taking over this project", "is this set complete", "set-reader", or a whole set handed over. Carries no standards and no phase definitions; completeness is judged against what the set itself claims to be. `drawing-reader` reads one sheet, `plan-review` reads a plan, `drawing-standards-audit` sweeps for conventions. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds a specification's section list from the drawings rather than from the last project's table of contents: walks the set for every material, system and scope shown, maps each to a section, then runs the check in both directions — work drawn with no section, and sections carried forward with no work. Marks each section's status so the book's real completeness is visible rather than implied by a full-looking contents page. Trigger on "what spec sections do we need", "build the table of contents", "spec outline", "do we have a section for this", "spec-outline-builder", or a drawing set handed over before the book is written. Carries no section numbers, no titles and no master list; numbering comes from the format your office uses and `/lookup-csi` finds one number. For auditing a book that exists use `spec-review`; for one paragraph use `/draft-spec-snippet`.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a project specification section by section, pulls out every submittal each one calls for, classifies it, and assembles a submittal log ready to issue. Trigger on "build submittal log", "submittal log", "extract submittals from spec", "shop drawing log", "submittal register", "submittal-log-builder", or a pasted specification section list. Works with any specification format and any contract. The user supplies the spec text by pasting it, naming files to read, or pointing at an indexed PDF, and supplies the review durations from their own contract. The skill never invents a submittal, never carries a list of typical submittals, and never assumes a review duration: every row traces to a line in the user's spec, and anything it could not find is listed as a gap rather than filled in.
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 CodeCodexWorks the conversation every project has and most handle badly: the design costs more than the budget. Establishes first what each number actually is, since a client's budget often excludes things an estimate includes and half the gap disappears there. Then sorts the ways of closing it into the four that behave differently — less area, less quality, less scope, more money — and prices each move in what it costs the design rather than only in what it saves. Trigger on "we are over budget", "the estimate came back high", "what do we cut", "value engineering at design stage", "the client's budget will not cover this", "budget-reconciliation", or an estimate set against a budget with a gap between them. Carries no costs, no rates and no benchmarks; every figure comes from the estimator, the contractor, or a source you name. `value-engineering-advisor` sorts a cost-cutting list during construction; this is the design-stage conversation. It does not estimate and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexStudies circulation as a set of named journeys rather than as corridor area: establishes who moves through the building and why, traces each journey door to door, finds the places two journeys cross that should not, and reports where a route depends on something being unlocked, staffed or explained. Separates the circulation a plan needs from the circulation it happens to have. Trigger on "circulation study", "trace the routes", "do these flows cross", "clean and dirty separation", "public and staff routes", "wayfinding through the plan", "circulation-study", or a plan handed over with a question about how people move through it. Carries no corridor widths, no efficiency ratios and no separation requirements; egress widths and distances belong to `design-egress` and accessibility to the accessibility standard you quote. It does not lay out a plan and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWorks an addition or a renovation at the place it actually gets decided: the joint between new and existing. Settles the relationship the new work takes to the old, then works the six things that cross the joint — structure, envelope, services, levels, fire separation and finishes — and separately establishes what the work triggers in the existing building, since a change of use or a threshold crossed can require upgrades to parts of the building nobody was touching. Trigger on "addition", "extension", "renovation", "how does the new bit meet the old", "does this trigger an upgrade", "matching the existing", "design-addition", or new work proposed against a building that already exists. Carries no code thresholds and no structural values; existing-building provisions are jurisdictional text you quote and capacity is the engineer's. Read `existing-conditions-survey` first: an addition designed against unverified dimensions is designed twice. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexLays out a domestic bathroom or ensuite from the two things that actually constrain it — where the waste can run and which way the door swings — rather than from the fixtures. Works ventilation, the wet area and its waterproofing, storage, and the reach and clearance around each fixture, and separates what is fixed by the building from what is a choice. Trigger on "bathroom layout", "ensuite", "can we move the toilet", "powder room", "where does the shower drain go", "design-bathroom", or a bathroom to be laid out or moved. Carries no clearances, no fixture dimensions and no ventilation rates; each comes from the code you quote, the accessibility standard, or the fixture's own data. For an accessible restroom to a standard use `design-accessible-restroom`; for commercial fixture counts use `/count-plumbing-fixtures`. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWorks the entrance as a continuous sequence rather than as a door: how it is found from the street, what happens on the way in, what the threshold has to hold at once, and where somebody stands when they arrive and nobody is expecting them. Names the four things that meet at a doorway and cannot all be optimised — level access, weather, energy, and security — and says which one this project lets win. Trigger on "entrance design", "the entry sequence", "where is the front door", "vestibule", "the entrance is hard to find", "design-entry", or an entrance that is a door on a plan and nothing more. Carries no dimensions, no threshold limits and no requirements; accessible thresholds and vestibule requirements are code and standards you quote. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexThe door into interior work, and the step that is usually missing: before partitions, ceilings, millwork or finishes are drawn, establish what each space actually has to withstand, where the money should go, which spaces repeat and which get attention, and what the base building has already decided. Produces the strategy the specific skills then execute against, and hands each part off by name. Trigger on "design the interior", "interior strategy", "where do we spend on this fit-out", "what finishes for this project", "the interior feels arbitrary", "design-interior", or an interior scope with no strategy behind it. Carries no finishes, no specifications, no costs and no ratings; every requirement comes from the brief, the client's operation, or the code you quote. It details nothing itself — `design-partition`, `design-ceiling`, `design-millwork` and `schedule-builder` do that — and does not replace the interior designer or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexLays out a domestic or small commercial kitchen from the sequence of work rather than from a triangle: where things arrive, where they are stored, prepared, cooked, served and cleaned, and what has to be within reach of what. Then works the two things that decide whether the layout survives — where the services can actually go, and what the ventilation demands of the plan and the elevation. Trigger on "kitchen layout", "design the kitchen", "galley or island", "where does the hood vent", "kitchen work triangle", "design-kitchen", or a kitchen with appliances chosen and nowhere settled. Carries no clearances, no aisle widths, no appliance dimensions and no ventilation rates; each comes from the code you quote, the accessibility standard, or the appliance's own data. Commercial kitchens beyond a small back-of-house are a specialist consultant's. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexDetails built-in joinery to the point a shop can price it without asking: what is fixed and what moves, how it meets a floor and a wall that are neither level nor straight, what it hangs off and whether that backing exists, where the services in it come from, and which decisions are the shop's rather than the drawing's. Trigger on "millwork", "casework", "joinery detail", "built-in", "reception desk", "how does this cabinet meet the wall", "design-millwork", or a built-in element that has to be drawn for tender. Carries no dimensions, no clearances, no material thicknesses and no hardware; ergonomic and accessible dimensions come from the standard you quote and every material figure from the fabricator or the data sheet. It is not shop drawing — `submittal-review` reads those when they come back — and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWrites the project description that gets asked for again and again in different lengths and for different readers: a planning submission, a design review board, an award entry, a website page, a client's own report. Establishes who is reading and what they can do about it before writing a word, since a board that can refuse and a magazine that cannot are different documents, then builds one account of the project that the shorter versions are cut from rather than rewritten. Trigger on "design narrative", "project description", "write up the project", "we need a paragraph for the submission", "award entry text", "design-narrative", or a request for words about a building. Carries no house voice and no claims of its own; every fact comes from the project and every claim has to be true of the drawings. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodex