Explore skills
Showing 53371–53400 of 77104 skills
Reads a letter from an authority — a correction letter, a completeness notice, a staff report, a conditional approval, a denial — and separates the four things inside it that behave differently: what must change, what must be shown, what must be answered, and what is a comment with nothing to do. Then finds the parts that carry a clock, since a response period or an appeal window is usually one line in the middle of a page. Trigger on "they sent this back", "read this correction letter", "what does the city actually want", "plan check comments came in", "submission-reader", or any letter from an authority handed over to work out. Carries no procedures and no periods; every deadline comes from the letter or from the jurisdiction. `plan-check-response-builder` writes the response; this works out what the letter asked. It does not replace the code consultant, the expeditor, or the Architect of Record.
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 CodeCodexReads 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 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 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 CodeCodexWorks views in both directions, because a window is two things at once: what a room looks at, and what looks back into it. Establishes what is worth seeing and whether it will still be there, what each room needs to see and what it must not, where privacy runs both ways between this building and its neighbours, and which views depend on land somebody else owns. Trigger on "view analysis", "what does this room look at", "will we still have this view", "overlooking", "privacy from the neighbours", "view-analysis", or a scheme where the windows have been placed by elevation rather than by what they see. Carries no angles, no distances and no separation requirements; overlooking rules are local text you quote and sun angles come from `shadow-study`. It does not model and does not replace 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 CodeCodexKeeps one dated record of a project's airtightness target from the moment it is written into the specification to the moment it is tested: what the target is and where it came from, which surface the enclosure boundary follows, every junction that has to be sealed and who owns it, every intermediate test and what it found, and every change that moves the number or the boundary. Trigger on "airtightness tracker", "blower door target", "track the air leakage requirement", "who owns this junction", "air barrier sign-off log", "airtightness-tracker", or an air leakage target named with a request to keep track of it. Carries no target values, no test standards and no unit conversions; the target, its units and its test method all come from the specification or the certification the project is chasing. It is not a test, does not model leakage, and does not replace the enclosure consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexAssembles an alternative means and methods request as an argument rather than a form: establishes the prescriptive requirement that cannot be met and why, states the intent behind that requirement in the code's own words, sets out what is proposed and how it meets that intent, and gathers the evidence, the compensating measures and the conditions the applicant is willing to accept. Trigger on "alternative means and methods", "AMMR", "code modification request", "equivalency request", "we cannot meet this section, what now", "alternative-means-builder", or a prescriptive requirement named as unachievable with a request to make the case. Carries no code text, no precedent from other jurisdictions and no performance criteria; the requirement, its stated intent and any referenced standard all come from documents you supply. It does not approve anything, does not perform fire modelling or engineering analysis, and does not replace the fire protection engineer, the code consultant, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexTakes any requirement — a code section, a standard, an ordinance, a lease clause, an owner's design standard, a certification credit — and answers the question that comes before every other one: does this apply to this project at all. Works the six tests that decide it: is the document adopted or binding here, does the project fall inside its stated scope, has the trigger been met, does an exemption remove it, is this the edition that binds, and is something else more restrictive. Trigger on "does this apply to us", "is this section relevant", "do we have to comply with this", "they say this applies", "applicability-check", or a requirement quoted at you. Carries no text and no thresholds: every answer comes from the document you supply or the jurisdiction's own source. It does not interpret the requirement — `code-reader` takes it apart — and does not replace the code consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexTakes any envelope assembly you are handed — a wall, a roof, a floor, a below-grade construction, from a consultant, a contractor, a manufacturer or an earlier phase of your own project — and reads it for what it is trying to do and where it does not. Locates the four control layers, checks each is continuous through the stack and has somewhere to go at the edges, names every layer with no job, and reports which direction it can dry. Trigger on "review this assembly", "is this wall build-up any good", "they sent us a section", "read this stack", "assembly-review", or any layered construction handed over for an opinion. Carries no R-values, permeance figures or code minimums; every value comes with the assembly or is marked missing. The `design-` assembly skills build one from demands; this reads one that already exists. It runs no arithmetic — `condensation-check` does — and does not replace the enclosure consultant or 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 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 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 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 CodeCodexTakes a citation somebody handed you — in a review comment, a consultant's report, a contractor's letter, a manufacturer's claim, or your own earlier drawing — and checks the three things that make it usable: does the document exist and in which edition, does the section number resolve inside it, and does the text actually say what it is being used to say. Reports which of the three could be verified and which could not, rather than a yes or a no. Trigger on "is this citation right", "check this code reference", "they quoted a section at us", "does this clause say that", "cite-check", or a section number pasted with a claim attached. Carries no code text: verification comes from the document you supply or from the jurisdiction's own published source, never from recall and never from a search result that is not the publisher. It does not interpret the clause — `explain-code` does — and does not replace the code consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a civil set against the architectural set for the disagreements that only show up where the two meet: the finished floor against the finished grade at every door, the accessible route against the actual slopes, where utilities enter the building against where the risers are, and what the civil drawings assume about a building they were not drawn from. Reports every conflict with both values and rules on neither. Trigger on "review the civil drawings", "do the civil and architectural agree", "grading around the building", "utility entry coordination", "civil-drawing-review", or a civil set issued for coordination. Carries no slope limits, no cover requirements and no utility standards; accessibility limits come from the standard you quote and utility requirements from the utility. It is not civil engineering, does not check drainage design, and does not replace the civil engineer or 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 CodeCodexTakes a code section, a standard, or an ordinance you paste and pulls it apart into the separate requirements inside it: what each one applies to, what it demands, what triggers it, what exempts it, and which other section it hands off to. A single paragraph routinely contains four requirements and two exceptions, and reading it as one sentence is how half of it gets missed. Trigger on "read this code section", "what does this clause actually require", "pull the requirements out of this", "code-reader", or a pasted section that has to be worked through. Carries no code text and recalls no section: everything comes from what you paste or from the jurisdiction's own published source. `explain-code` puts one clause in plain English; this takes the clause apart into a table you can check a design against. It does not check the design — `compliance-check` does — and does not replace the code consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexTakes a drawing and the code text that governs it and works through them together, one requirement at a time: what the text demands, what the drawing shows, and whether the drawing shows enough to tell. The third answer is the common one and it is the useful one, because a drawing that does not say is not a drawing that complies. Trigger on "does this drawing meet this code", "check this against the code text", "we pasted the section, now check the plan", "compliance-check", or a drawing and a quoted requirement handed over together. Carries no code text and recalls no limit: everything comes from what you paste. `code-compliance-review` audits a plan across eight fixed axes without being given text; this checks whatever text you bring against whatever drawing you bring. It does not interpret the clause, does not certify anything, and does not replace the code consultant 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 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 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 CodeCodexReads 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
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 CodeCodexLays out an accessible restroom or toilet room as a set of overlapping clearances rather than as a list of items to tick: establishes which clearances may overlap and which may not from the standard you quote, places the fixtures in the order that constrains the plan most, works the door swing against the clear floor space it eats, and reports every dimension as a question rather than an answer. Trigger on "accessible restroom layout", "toilet room won't fit", "ADA bathroom", "single-user accessible washroom", "turning circle in the toilet", "design-accessible-restroom", or a toilet room plan with a request for whether it works. Carries no dimensions, no clearances and no reach ranges; every one is text you quote from the standard your jurisdiction adopts, which is not always the one you expect. For checking one clearance already dimensioned use `/test-ada`; for a project-wide record use `ada-tracker`. It does not replace the accessibility consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodex