agentleFS
timjrobinsontimjrobinson/Claude-Code-Construction-Manager/.claude/skills/team-structural/SKILL.md

team-structural

Skill4 starsChanged 8 months agoMITView on GitHub

Orchestrate the structural team: coordinates structural-engineer-lead, foundation-engineer, steel-detailer, concrete-specialist, and geotechnical-engineer.

The file

Files
SKILL.md

Team Composition

  • structural-engineer-lead — Overall structural design and coordination
  • foundation-engineer — Foundation design and soil-structure interaction
  • steel-detailer — Steel connection design and shop drawings
  • concrete-specialist — Concrete design and reinforcement detailing
  • geotechnical-engineer — Subsurface conditions and recommendations

Pipeline

Phase 1: Investigation — geotechnical-engineer provides soil data

Phase 2: System Design — structural-engineer-lead selects structural system

Phase 3: Detailed Design (parallel) — foundation, steel, concrete specialists

Phase 4: Coordination — bim-manager runs clash detection

Phase 5: Review — quality-assurance-lead reviews calculations and details

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.