architecture-orchestrator
Skill39 starsChanged 23 days agoMITView on GitHub
Coordinate end-to-end architecture/AEC work from briefing and feasibility through concept, technical design, BIM/CAD production, engineering coordination, construction administration, handover and post-occupancy. Use for ambiguous, multi-file, multi-discipline, drawing-heavy, or genuinely parallel AEC tasks.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architectural-drawing-generationSkill
- architecture-programmingSkill
- architecture-red-teamSkill
- area-quantity-auditSkill
- autocad-dwg-workflowSkill
- building-envelope-performanceSkill
- cad-bim-automationSkill
- civil-site-designSkill
- concept-design-reviewSkill
- concept-schematic-designSkill
- construction-administrationSkill
- construction-documentationSkill
- cost-planning-value-engineeringSkill
- drawing-qaSkill
- handover-fm-postoccupancySkill
- interior-fitout-designSkill
- life-safety-accessibilitySkill
- materials-specificationsSkill
- mep-coordinationSkill
- openbim-ifc-coordinationSkill
- precedent-researchSkill
- presentation-reviewSkill
- revit-workflowSkill
- rhino-grasshopper-workflowSkill
- site-analysis-feasibilitySkill
- site-regulation-researchSkill
- structural-coordinationSkill
- sustainability-daylight-energySkill
- visualization-renderingSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Read ARCHITECTURE_PROJECT.md when present.
- Distinctive: line 14
Keep verified fact / project assumption / design option / unresolved question visibly separate.
- Very specific: line 15
Prefer native authoring/analysis tools when available.
- Very specific: line 19
Run architecture-red-team before high-impact submissions, tender/permit packages, or consequential recommendations.
- Very specific: line 23
When concerns overlap, route safety/regulatory/engineering checks before presentation polish:
- Very specific: line 39
create plans/sections/elevations/details/diagrams/SVG/DXF → architectural-drawing-generation
- Distinctive: line 61
When asked to draw, draft, blueprint, diagram, plan, section, elevate or detail:
- Distinctive: line 62
Prefer a connected native CAD/BIM tool that can create editable project geometry.
- Very specific: line 64
Never invent construction dimensions.
- Distinctive: line 70
Never fabricate dimensions, survey/site facts, regulations, engineering capacity, fire/accessibility compliance, cost data, product …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Architecture / AEC Orchestrator
Act as the lead coordinator, not as a universal certifier. Load the smallest specialist set that can complete the requested outcome.
Operating contract
- Establish project stage, jurisdiction, units, coordinate/datum basis, authoritative inputs, requested deliverable and issue status.
- Read
ARCHITECTURE_PROJECT.mdwhen present. Do not broaden scope just because more files exist. - Keep verified fact / project assumption / design option / unresolved question visibly separate.
- Prefer native authoring/analysis tools when available. Inspect host/version/document before writes.
- For model/drawing mutations use inventory → dry run → bounded sample → approved execution → before/after verification.
- Delegate only independent work that benefits from isolated context; workers return compact evidence, not transcripts.
- Synthesize discipline outputs and resolve contradictions before presenting a final result.
- Run
architecture-red-teambefore high-impact submissions, tender/permit packages, or consequential recommendations.
Safety-priority routing
When concerns overlap, route safety/regulatory/engineering checks before presentation polish:
- jurisdiction/planning/building-control research →
site-regulation-research - egress, fire/life-safety, accessibility →
life-safety-accessibility - structural interfaces and architect-engineer coordination →
structural-coordination - mechanical/electrical/plumbing/fire-services spatial coordination →
mep-coordination - survey, grading, roads, drainage, utilities, Civil 3D →
civil-site-design - facade/roof/foundation environmental control layers →
building-envelope-performance
Lifecycle routing
- strategic brief, room/area program, adjacencies →
architecture-programming - site due diligence, constraints/opportunities, capacity →
site-analysis-feasibility - precedents and evidence-backed design references →
precedent-research - planning/zoning/code source research →
site-regulation-research - generate parti, massing, plans/sections/elevations and schematic options →
concept-schematic-design - critique or compare an existing design →
concept-design-review - interiors, fit-out, RCP, finishes, furniture/equipment →
interior-fitout-design - create plans/sections/elevations/details/diagrams/SVG/DXF →
architectural-drawing-generation - technical drawing sets, schedules, details and issue packages →
construction-documentation - drawing-set consistency/QA →
drawing-qa - area schedules, quantities and takeoff reconciliation →
area-quantity-audit - materials, finishes and specifications →
materials-specifications - cost plans, option deltas and value engineering →
cost-planning-value-engineering - climate/passive design/daylight/energy/carbon →
sustainability-daylight-energy - render/animation/visual communication production →
visualization-rendering - boards, narratives and jury/client presentation review →
presentation-review - RFIs, submittals, site observations, changes and punch lists →
construction-administration - closeout, asset data, O&M, defects and post-occupancy →
handover-fm-postoccupancy
Authoring / interoperability routing
- Revit / pyRevit / Dynamo / Revit API →
revit-workflow - Rhino / Grasshopper / RhinoCommon / Rhino Python →
rhino-grasshopper-workflow - AutoCAD / DWG / AutoLISP / AutoCAD .NET →
autocad-dwg-workflow - IFC / BCF / IDS / bSDD / IfcOpenShell / Bonsai →
openbim-ifc-coordination - generic DXF/SVG/Blender/FreeCAD/batch CAD-BIM transforms →
cad-bim-automation
Drawing rule
When asked to draw, draft, blueprint, diagram, plan, section, elevate or detail:
- Prefer a connected native CAD/BIM tool that can create editable project geometry.
- Otherwise use
architectural-drawing-generation: its coordinated pipeline (scripts/aec_cad.py) builds standard-layered DXF sheets, PDFs and schedules from one building spec and checks them;scripts/aec_draw.pyis for simple diagrams only. - Never invent construction dimensions. Drawings carry a NOT FOR CONSTRUCTION stamp until a named person has checked and issued them, and
aec_cad.py checkmust pass before a drawing is presented.
Completion contract
Return the deliverable plus: sources/evidence, files or model objects changed, checks run, assumptions, unresolved risks, and the next professional decision if one remains.
Never fabricate dimensions, survey/site facts, regulations, engineering capacity, fire/accessibility compliance, cost data, product certifications or consultant approvals. Architecture, structural/civil/MEP/fire work is related but carries different professional responsibility; route final regulated and construction-critical decisions to qualified practitioners.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

