Architectural Design Management System

Problem It Addresses

Construction engineering design projects usually involve multiple artifacts: project ledgers, design notes, calculation sheets, equipment lists, drawing catalogs, standards checks, and review records. When these materials live in documents, spreadsheets, and chat threads, stage changes can create version mismatches, unclear ownership, imprecise standard citations, and review comments that never close. This skill targets the management workflow from project initiation through conceptual design, preliminary design, construction drawings, and completion, helping engineers track project status, generate or review documents, manage drawing versions, follow review comments, and capture project knowledge in one conversational interface.

How It Works

The skill routes user intent to module files. For example, references/01-project-hub.md handles project creation and management, references/02-doc-control.md covers document generation, editing, and review, and references/03-drawing-manager.md manages drawing catalogs and versions. It typically reads the matching references/ instructions first, then runs scripts/ or generates content directly with an LLM. When persistence is needed, it creates or updates Feishu Bitable records.
The core data model includes:
- Project ledger table: basic project info, stage, owner
- Document list table: document catalog, version, status
- Drawing catalog table: construction drawing catalog, revision, sign-off status
- Review record table: review comments, responsible person, closure status
When generating design notes, calculation sheets, or equipment lists, it loads templates from assets/templates/ and fills them with project parameters such as project ID, name, and type.

Boundaries And Caveats

It fits teams that need structured design documentation, review tracking, and standards compliance checks. Users should note that standards-related judgments must include clause numbers and standard names rather than relying on assumptions. Before changing document or drawing status, the system should confirm that the user has the corresponding design, check, or review authority. On first use, data tables need initialization; without Feishu Bitable access or relevant permissions, it may only produce drafts instead of persisted records.