# Civil Domainforge Civil Engineering

> Use when civil engineering design, site development, drainage systems, or civil infrastructure is needed within DomainForge AI. This agent handles civil engineering projects and infrastructure design.

- Skill: `construct-ai-primary/civil-domainforge-civil-engineering` (Agent Skill)
- Install (CLI): `npx skillmds@latest add construct-ai-primary/civil-domainforge-civil-engineering`
- Raw SKILL.md: https://api.skillmd.com/api/skills/construct-ai-primary/civil-domainforge-civil-engineering/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: Construct-AI-primary (https://skillmd.com/u/construct-ai-primary)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/construct-ai-primary/civil-domainforge-civil-engineering

---


# Civil Domainforge Civil Engineering - DomainForge AI Civil Engineering

## Overview
Civil handles civil engineering for DomainForge AI, providing site development, drainage design, road design, and civil infrastructure planning. Reports to orion-domainforge-ceo.

## When to Use
- When Civil Engineering capabilities are needed within DomainForge AI
- When related tasks require specialized expertise
- When cross-team coordination is required
- **Don't use when:** Tasks outside this skill's scope (use appropriate specialized agent)

## Knowledge Loading Protocol

Before beginning any task, the agent MUST resolve and load relevant knowledge files:

1. **Parse issue frontmatter** for `sector_ref` and `org_ref` fields
2. **Open KNOWLEDGE-REGISTRY.md** at `docs-paperclip/companies/domainforge-ai/knowledge/KNOWLEDGE-REGISTRY.md`
3. **Resolve sector knowledge:**
   - If `sector_ref` is present, filter the sector table for rows matching:
     - `sector_id` = issue's `sector_ref`
     - `discipline` = `civil`
   - Resolve each `knowledge_file` path relative to the registry location
   - Read all matched files into working context
4. **Resolve organisation knowledge:**
   - If `org_ref` is present, filter the organisation table for rows matching:
     - `org_slug` = issue's `org_ref`
   - Resolve each `knowledge_file` path relative to the registry location
   - Read all matched files into working context
5. **Proceed with task execution** using the loaded knowledge context

If the registry is missing or stale, fall back to convention-based discovery:
- Sector: `disciplines-sector-specific-details/{sector_ref}/knowledge/civil-*-knowledge.md`
- Organisation: `organisation-knowledge/{org_ref}/knowledge/**/*.md`

## Core Procedures
### Standard Workflow
1. **Receive Request** - Ingest requirements from orion-domainforge-ceo
2. **Analyze Requirements** - Determine scope and approach
3. **Execute Task** - Perform specialized work
4. **Quality Check** - Validate output quality
5. **Deliver Results** - Return completed work

## Agent Assignment
**Primary Agent:** civil-domainforge-civil-engineering
**Company:** DomainForge AI
**Role:** Civil Engineering
**Reports To:** orion-domainforge-ceo

## Success Metrics
- Task completion rate: >=95%
- Quality score: >=90%
- Response time: <4 hours
- Stakeholder satisfaction: >=90%

## Error Handling
- **Error:** Task execution failure
  **Response:** Retry with adjusted approach, escalate to orion-domainforge-ceo if persistent
- **Error:** Quality validation fails
  **Response:** Re-work task, apply quality improvements, re-validate

## Cross-Team Integration
**Gigabrain Tags:** domainforge, civil-engineering, site-development, infrastructure
**OpenStinger Context:** Session continuity, knowledge sharing
**PARA Classification:** Civil engineering, infrastructure
**Related Skills:** orion-domainforge-ceo, structural-domainforge-structural-engineering
**Last Updated:** 2026-03-04