{"slug": "orgframework-537-hand-written-role-files-for-claude-code", "title": "OrgFramework – 537 hand-written role files for Claude Code", "summary": "OrgFramework, a new open-source tool for Claude Code, provides 537 hand-written organizational role files, 31 org presets, crisis templates, and compensation data to help the AI construct context-specific organizational structures. The tool allows users to describe their situation—such as company size, region, industry, and stage—and receive dynamically generated department, role, and reporting line recommendations.", "body_md": "This is for Claude Code\n\n**537 hand-written reference roles — 31 org presets — crisis templates — compensation data — region/industry/stage adaptation**\n\nNo fixed org chart builder. Describe your situation, and Claude Code dynamically constructs the optimal organizational structure for that specific context — with the right departments, roles, reporting lines, and regional/industry nuance.\n\n```\n/orgframework we're a 50-person fintech in Berlin expanding to Brazil\n/orgframework design a respiratory therapy department for a regional hospital\n/orgframework our Series B SaaS startup needs a compliance structure\n/orgframework what's the right team structure for a remote-first design agency\n```\n\n[What it is](#what-it-is)[Quick start](#quick-start)[Installation](#installation)[Usage](#usage)[What's inside](#whats-inside)[Architecture](#architecture)[Context dimensions](#context-dimensions)[Example](#example)[Development](#development)[Roadmap](#roadmap)[License](#license)\n\norgframework is a **reference library and skill for Claude Code** that helps Claude build better organizational structures. Instead of guessing what departments a fintech company needs or what a \"Head of Compliance\" in Germany should report to, Claude reads from:\n\n**537 hand-written roles**— each with responsibilities, KPIs, career paths, tools, cross-functional relationships, and regional/industry variations**31 org presets**— complete org structures for common scenarios (Series A SaaS, hospital system, fintech, restaurant kitchen, etc.)** 6 crisis templates**— pre-built command structures for breach, layoff, acquisition, founder departure, PR crisis, regulatory investigation** Compensation data**— salary bands for 50+ roles across 4 regions and 4 levels** Region/industry/stage profiles**— laws, norms, metrics, and patterns that shape org design\n\nThe AI is **never limited** to these references. They exist to give Claude concrete, detailed examples to draw from — and to ground its recommendations in real-world patterns rather than generic guesses.\n\n```\n# 1. Install into your Claude Code project\nbash path/to/orgframework/bin/install.sh\n\n# 2. Use it in Claude Code\n/orgframework we're a 30-person Series A SaaS company in Berlin, what's my org structure\n```\n\nShortcodes for explicit context:\n\n- Region:\n`@na`\n\n`@emea`\n\n`@apac`\n\n`@latam`\n\n- Industry:\n`@saas`\n\n`@fintech`\n\n`@health`\n\n`@mfg`\n\n`@ecom`\n\n- Stage:\n`@startup`\n\n`@scaleup`\n\n`@enterprise`\n\n```\n/orgframework @fintech @emea @scaleup we're expanding our payments team\n# Clone the repo somewhere\ngit clone https://github.com/korishnn/orgframework.git\n\n# Install into your project (from project root)\nbash path/to/orgframework/bin/install.sh\n\n# Or install into a specific directory\nbash path/to/orgframework/bin/install.sh /path/to/your/project\n```\n\nThis copies all roles, presets, and profiles into `.claude/orgframework/`\n\nand the skill definition into `.claude/skills/orgframework/`\n\n.\n\n```\nnode path/to/orgframework/bin/diagnose.js\n```\n\nShould show all components present and healthy.\n\n```\n/orgframework I need to hire a senior backend engineer in Berlin\n/orgframework what does my Series A SaaS org look like with 25 people\n/orgframework design the management structure for a 200-person manufacturing plant\n/orgframework we're launching a new product line, what's the team structure\n/orgframework design the compliance structure for a UK fintech\n/orgframework what departments does a hospital need for respiratory therapy\n/orgframework org structure for an ecommerce company during Black Friday\n/orgframework US company expanding to Japan — what's the org plan\n/orgframework we're opening a Brazil office from Berlin\n/orgframework we just had a data breach — what's the command structure\n/orgframework our CTO is leaving suddenly, what's the transition plan\n/orgframework diagnose    # Show system health and learned preferences\n/orgframework debug       # Show what was detected from your input\n/orgframework reset       # Clear learned preferences\n```\n\n**537 hand-written markdown files** in `.claude/orgframework/styles/`\n\n. Each covers one real-world role with:\n\n| Field | What it contains |\n|---|---|\n| Summary | One-line description of the role |\n| Level | IC, Manager, Head, VP, C-Suite |\n| Reports to | Typical reporting structure |\n| Responsibilities | 10-20 concrete responsibilities |\n| Core Competencies | Skills and knowledge required |\n| Tools & Technology | Common tools used in the role |\n| KPIs & Success Metrics | How performance is measured |\n| Career Progression | Typical ladder from junior to principal |\n| Day-to-Day Workflow | What a typical week looks like |\n| Cross-Functional Relationships | Who they work with and how |\n| Regional Nuances | How the role varies by region |\n| Industry Variations | How the role shifts by industry |\n| Common Challenges | Pain points and pitfalls |\n| Key Regulations & Compliance | Regulatory context |\n\n**Domains covered:**\n\n| Prefix | Domain | Example roles |\n|---|---|---|\n`eng-` |\nEngineering | backend, frontend, devops, sre, ml, data, security, qa, mobile |\n`mkt-` |\nMarketing | brand, content, seo, growth, social, pr, marketing-ops |\n`sls-` |\nSales | enterprise, sdr, solutions, customer-success, partnerships |\n`hr-` |\nHR | recruiting, hrbp, people-ops, compensation, l&d |\n`fin-` |\nFinance | controller, fp&a, tax, treasury, audit |\n`ops-` |\nOperations | operations, supply-chain, procurement, facilities |\n`lgl-` |\nLegal | counsel, compliance, privacy, contracts |\n`prd-` |\nProduct | product-manager, product-ops, program-manager |\n`cs-` |\nCustomer Support | support-engineer, success-manager, support-ops |\n`exec-` |\nExecutive | ceo, coo, cfo, cto, chief-of-staff |\n`dsg-` |\nDesign | product-design, ux, visual, brand, design-ops |\n`da-` |\nData & Analytics | data-engineer, data-scientist, analyst, bi |\n`sec-` |\nSecurity & Compliance | security-engineer, grc, soc-analyst |\n`hlth-` |\nHealthcare | physician, nurse, surgeon, pharmacist, therapist |\n`edu-` |\nEducation | teacher, professor, principal, librarian |\n`cre-` |\nCreative | director, producer, designer, editor, artist |\n`trade-` |\nTrades | carpenter, electrician, plumber, welder, mechanic |\n`tran-` |\nTransportation | driver, warehouse-manager, logistics |\n`avi-` |\nAviation | pilot, flight-attendant, atc, mechanic |\n`hosp-` |\nHospitality | hotel-manager, chef, concierge, housekeeping |\n`govt-` |\nGovernment | policy, administrator, inspector, diplomat |\n`mil-` |\nMilitary | officer, nco, specialist, strategist |\n`sci-` |\nScience | researcher, lab-manager, field-scientist |\n`np-` |\nNonprofit | director, grant-writer, program-manager |\n`beauty-` |\nBeauty | barber, cosmetologist, esthetician, nail-tech |\n`acad-` |\nAcademia | professor, researcher, anthropologist, economist |\n`agri-` |\nAgriculture | farmer, agronomist, forester, vineyard-manager |\n\n**31 complete org structure templates** in `.claude/orgframework/presets/`\n\n. Each is a JSON file containing departments, roles with headcount, reporting lines, key cross-functional relationships, and an org chart.\n\n| Preset | Headcount | Best for |\n|---|---|---|\n`seed-startup` |\n1-10 | Founders building MVP, pre-product-market fit |\n`series-a-saas` |\n10-30 | First functional departments emerging |\n`series-b-saas` |\n30-80 | Scaling with VPs, growing management layer |\n`fintech-org` |\n10-500+ | Regulated fintech with embedded compliance |\n`hospital-system` |\n200-10,000+ | Full hospital with clinical and admin departments |\n`dental-practice` |\n3-50 | Dental clinic with clinical and front office |\n`urgent-care-clinic` |\n5-50 | Walk-in clinic with providers and support |\n`mental-health-practice` |\n3-50 | Therapy/counseling practice |\n`home-health-hospice` |\n10-300 | Home health agency with field staff |\n`vet-clinic` |\n3-30 | Veterinary practice |\n`hardware-medical-device` |\n20-5,000+ | Medical device manufacturing and sales |\n`pharma-biotech-rd` |\n10-5,000+ | Drug development and research |\n`ecommerce-retail` |\n30-10,000+ | Online retail with fulfillment |\n`marketplace-platform` |\n15-500+ | Two-sided marketplace |\n`manufacturing-plant` |\n— | Factory/production facility |\n`restaurant-kitchen` |\n10-100 | Commercial kitchen |\n`hotel-property` |\n50-500 | Full-service hotel |\n`architecture-firm` |\n5-500 | Design and architecture practice |\n`consulting-firm` |\n10-5,000+ | Management consulting |\n`law-firm` |\n10-2,000+ | Legal practice with partners and associates |\n`agency-creative-digital` |\n10-300 | Creative/digital agency |\n`film-production-crew` |\n30-500 | Film/TV production |\n`school-k12` |\n50-500 | K-12 school |\n`university-higher-ed` |\n500-20,000 | University |\n`research-lab` |\n3-30 | Scientific research lab |\n`nonprofit-ngo` |\n5-500+ | Nonprofit organization |\n`government-agency` |\n50-5,000 | Government department or agency |\n`military-unit` |\n300-1,200 | Battalion/regiment |\n`sports-team` |\n50-400 | Professional sports organization |\n`construction-site` |\n10-200 | Construction project |\n`remote-first-company` |\n10-500 | Distributed/remote org with async culture |\n`public-enterprise` |\n500+ | Large public company |\n\n**6 crisis command structures** in `.claude/orgframework/crisis/`\n\n. Each defines a clear chain of command, roles, responsibilities, and escalation paths for a specific crisis type:\n\n| Template | Crisis scenario |\n|---|---|\n`breach-cyber.json` |\nData breach — containment, forensics, notifications |\n`mass-layoff.json` |\nWorkforce reduction — legal, comms, severance |\n`founder-departure.json` |\nFounder/CEO leaving — succession, board, comms |\n`acquisition-integration.json` |\nPost-acquisition org integration |\n`pr-crisis.json` |\nReputational crisis — media, legal, internal comms |\n`regulatory-investigation.json` |\nRegulator inquiry — legal defense, document production |\n\n**50+ roles with salary bands** in `.claude/orgframework/compensation/bands.json`\n\n. Four regions (NA, EMEA, APAC, LATAM), four levels (junior, mid, senior, lead). NA figures are total comp (base + bonus + equity); other regions vary by market norms.\n\n```\n\"eng-backend\": {\n  \"junior\": { \"na\": \"80K-120K\", \"emea\": \"50K-74K EUR\", ... },\n  \"mid\":   { \"na\": \"120K-180K\", \"emea\": \"74K-112K EUR\", ... },\n  \"senior\":{ \"na\": \"180K-280K\", \"emea\": \"112K-174K EUR\", ... },\n  \"lead\":  { \"na\": \"250K-400K\", \"emea\": \"155K-248K EUR\", ... }\n}\n```\n\n4 profiles in `.claude/orgframework/regions/`\n\n. Each covers employment laws, cultural norms, benefits expectations, currency, and reporting standards for that region.\n\n| Region | Key characteristics |\n|---|---|\n| NA | At-will employment, direct communication, 401(k)/health, FLSA |\n| EMEA | Strong protection, works councils, GDPR, 20+ vacation days, IFRS |\n| APAC | Hierarchy, bonus culture, social insurance, data localization |\n| LATAM | 13th salary mandatory, CLT (Brazil), unions, nearshoring |\n\n5 profiles in `.claude/orgframework/industries/`\n\n. Each covers the metrics, regulatory framework, and operational patterns specific to that vertical.\n\n| Industry | Key metrics | Regulatory context |\n|---|---|---|\n| SaaS | MRR/ARR, churn, NRR, CAC | SOC 2 |\n| Fintech | TPV, take rate, default rate | KYC/AML, PSD2, PCI DSS, BaFin/FCA/SEC |\n| Healthcare | Patient outcomes, readmission | HIPAA, FDA, EU MDR |\n| Manufacturing | OEE, yield, safety incidents | ISO, OSHA |\n| Ecommerce | GMV, AOV, conversion, returns | Consumer rights, cross-border tax |\n\n3 profiles in `.claude/orgframework/stages/`\n\n. Each adjusts org depth, decision-making speed, specialization level, and compensation philosophy.\n\n| Stage | Org style | Comp approach |\n|---|---|---|\n| Startup | Flat, founder-led, multi-hat | Equity-heavy |\n| Scaleup | Emerging departments, VPs | Market salary + options |\n| Enterprise | Deep hierarchy, matrix | RSUs, structured bands |\n\n12 additions in `.claude/orgframework/additions.json`\n\n— these are structured prompts that tell Claude how to think about org design for specific dimensions:\n\n| Addition | What it does |\n|---|---|\n| Org Architect | Build custom org structure from scratch for every request |\n| Context Classifier | Detect region, industry, stage, task type from natural language |\n| Region Adapt | Apply local employment law, culture, currency |\n| Industry Adapt | Apply industry metrics, regulations, patterns |\n| Stage Adapt | Adjust org depth for company maturity |\n| Meeting Format | Auto-format output by meeting type |\n| Scope Guard | Flag decision rights, budget limits, regulatory gates |\n| Urgency Adapt | Adjust depth — blunt for hotfixes, structured for planning |\n| Cross-Function Weaver | Show how perspectives connect and decisions flow |\n| Auto Troubleshoot | Self-evaluate and learn from corrections |\n| Adaptive Learning | Track preferences within a conversation |\n| Systems Integration | Coordinate across all available systems and data |\n\n```\norgframework/\n├── .claude/\n│   ├── skills/\n│   │   └── orgframework/\n│   │       └── SKILL.md                  # Skill definition for Claude Code\n│   └── orgframework/\n│       ├── index.json                    # Master index and configuration\n│       ├── additions.json                # 12 cross-cutting guidance additions\n│       ├── styles/                       # 537 hand-written role files\n│       │   ├── eng-backend.md\n│       │   ├── hlth-physician.md\n│       │   ├── fin-cfo.md\n│       │   └── ...\n│       ├── presets/                      # 31 org structure templates\n│       │   ├── series-a-saas.json\n│       │   ├── fintech-org.json\n│       │   ├── hospital-system.json\n│       │   └── ...\n│       ├── crisis/                       # 6 crisis command structures\n│       │   ├── breach-cyber.json\n│       │   ├── mass-layoff.json\n│       │   └── ...\n│       ├── compensation/\n│       │   └── bands.json                # Salary bands, 50+ roles, 4 regions\n│       ├── regions/                      # 4 region profiles\n│       │   ├── na.json\n│       │   ├── emea.json\n│       │   ├── apac.json\n│       │   └── latam.json\n│       ├── industries/                   # 5 industry profiles\n│       │   ├── saas.json\n│       │   ├── fintech.json\n│       │   ├── healthcare.json\n│       │   ├── manufacturing.json\n│       │   └── ecommerce.json\n│       ├── stages/                       # 3 stage profiles\n│       │   ├── startup.json\n│       │   ├── scaleup.json\n│       │   └── enterprise.json\n│       ├── expansion/                    # Cross-region expansion playbooks\n│       │   ├── us-to-emea.json\n│       │   ├── us-to-latam.json\n│       │   └── ...\n│       ├── diagnostics/\n│       │   └── troubleshoot.json         # Self-correction rules\n│       ├── adaptations/                  # User preference tracking\n│       │   ├── profile.json\n│       │   └── resolver.guidance.md\n│       ├── comparison/                   # Org structure diff engine\n│       │   ├── comparison.guidance.md\n│       │   └── comparison.js\n│       ├── visualizer/                   # Mermaid.js org chart generator\n│       │   ├── generate.js\n│       │   └── templates.json\n│       ├── hiring/\n│       │   └── hiring.guidance.md\n│       ├── maturity/\n│       │   └── maturity.guidance.md\n│       ├── raci/\n│       │   └── raci.guidance.md\n│       ├── relationship-map/\n│       │   └── relationship-map.js\n│       ├── similarity/\n│       │   └── similarity.js\n│       ├── health-monitor/\n│       │   └── monitor.guidance.md\n│       ├── budget/\n│       │   └── budget.guidance.md\n│       ├── culture/\n│       │   └── culture.guidance.md\n│       ├── reverse-org/\n│       │   └── reverse-org.js\n│       ├── role-to-task/\n│       │   └── role-to-task.js\n│       ├── timeline/\n│       │   └── timeline.guidance.md\n│       └── vacancy/\n│           └── vacancy.js\n├── bin/\n│   ├── install.sh                        # Shell installer\n│   ├── install.js                        # Node.js installer\n│   └── diagnose.js                       # Self-diagnostic tool\n├── tests/\n│   ├── validate-roles.js                 # Validates all role files exist\n│   ├── validate-presets.js               # Validates preset structure\n│   └── validate-index.js                 # Validates index and config\n├── .github/\n│   └── workflows/\n│       └── ci.yml                        # CI pipeline\n├── package.json\n├── README.md\n└── LICENSE\n```\n\nWhen a user runs `/orgframework <request>`\n\nin Claude Code:\n\n```\nUser: \"we're a 50-person fintech in Berlin expanding to Brazil\"\n                          │\n                          ▼\n┌─────────────────────────────────────────────┐\n│          1. Context Classifier               │\n│  ┌────────┬────────┬────────┬────────────┐  │\n│  │Region  │Industry│ Stage  │ Task type  │  │\n│  │ EMEA   │Fintech │Scaleup │ Expansion  │  │\n│  └────────┴────────┴────────┴────────────┘  │\n└─────────────────────────────────────────────┘\n                          │\n                          ▼\n┌─────────────────────────────────────────────┐\n│         2. Preset Matcher                    │\n│  Check presets/ for fintech org template.   │\n│  Found: fintech-org.json — use as starting  │\n│  point, adapt for EMEA + Brazil context.    │\n└─────────────────────────────────────────────┘\n                          │\n                          ▼\n┌─────────────────────────────────────────────┐\n│         3. Org Architect                     │\n│  Construct departments, roles, reporting    │\n│  lines. Read relevant styles/*.md files     │\n│  for depth. Create whatever roles fit.      │\n└─────────────────────────────────────────────┘\n                          │\n                          ▼\n┌─────────────────────────────────────────────┐\n│         4. Region/Industry/Stage Adapt       │\n│  Apply Brazil labor law (CLT, 13th salary). │\n│  Apply fintech compliance (BCB licensing).  │\n│  Apply scaleup depth (first VPs, emerging). │\n└─────────────────────────────────────────────┘\n                          │\n                          ▼\n┌─────────────────────────────────────────────┐\n│         5. Deliver                          │\n│  Custom org structure with context header.  │\n│  Region, industry, stage, task type shown.  │\n└─────────────────────────────────────────────┘\n```\n\nEach reference role is a markdown file with a consistent structure. Example: `eng-backend.md`\n\n```\n# eng-backend\n\n**Summary:** Backend Engineer designs, builds, and maintains server-side logic,\nAPIs, data services, and system integrations that power the product experience.\n\n**Level:** IC\n**Reports to:** Engineering Manager\n**Region variants:** NA, EMEA, APAC, LATAM\n\n## Responsibilities\n- Design, develop, test, and deploy RESTful and GraphQL APIs\n- Implement business logic and server-side application features\n- Optimize database schemas, queries, and indexing strategies\n- Write comprehensive unit, integration, contract, and end-to-end tests\n- ...\n\n## Core Competencies\n- Strong programming skills in Python, Go, Java, or TypeScript\n- Deep understanding of relational and NoSQL databases\n- Knowledge of API design (REST, GraphQL, gRPC)\n- ...\n\n## Tools & Technology\n- Languages: Python, Go, TypeScript, Java, Rust, Ruby\n- Databases: PostgreSQL, MySQL, MongoDB, Redis, Elasticsearch\n- ...\n\n## KPIs & Success Metrics\n- API response latency (p50, p95, p99) and error rates\n- Service uptime and availability percentage\n- Deployment frequency and lead time for changes\n- ...\n\n## Career Progression\n- Junior (0-2): Implements well-scoped features under guidance\n- Mid (2-5): Independently delivers feature-sized changes\n- Senior (5-8): Leads complex feature initiatives, mentors others\n- ...\n\n## Day-to-Day Workflow\n- Daily standup to share progress, blockers, and plans\n- Sprint-based development with 1-2 week iterations\n- Weekly 1:1 with engineering manager\n- On-call rotation (1 week every 4-6 weeks)\n- ...\n\n## Cross-Functional Relationships\n- Partners with eng-frontend on API contract design\n- Works with prd-manager on feature requirements\n- Coordinates with eng-sre on production readiness\n- ...\n\n## Regional Nuances\n- NA: Largest market, highest comp, remote-first common\n- EMEA: Strong labor protections, 35-40 hour weeks, GDPR\n- APAC: More hierarchical, broader skillset expected\n- LATAM: Growing remote workforce, Node.js/Python strong\n- ...\n\n## Industry Variations\n- SaaS: Multi-tenant architecture, API-first, uptime\n- Fintech: Transactional integrity, audit logging, PCI-DSS\n- Healthcare: HIPAA, PHI, strict access controls\n- ...\n```\n\nEach preset is a JSON file with metadata, applicability rules, and a full org structure:\n\n```\n{\n  \"preset\": \"series-a-saas\",\n  \"version\": \"1.0\",\n  \"name\": \"Series A SaaS\",\n  \"description\": \"For SaaS companies at Series A stage with 10-30 people...\",\n  \"applicability\": {\n    \"regions\": [\"na\", \"emea\", \"apac\", \"latam\"],\n    \"industries\": [\"saas\"],\n    \"stages\": [\"startup\", \"scaleup\"]\n  },\n  \"headcount_range\": \"10-30\",\n  \"org_structure\": {\n    \"overview\": \"At Series A the startup formalizes into functional areas...\",\n    \"departments\": [\n      {\n        \"name\": \"Engineering\",\n        \"description\": \"Builds and ships the product...\",\n        \"headcount\": \"4-8\",\n        \"reports_to\": \"CEO\",\n        \"roles\": [\n          {\n            \"title\": \"VP of Engineering\",\n            \"count\": 1,\n            \"level\": \"Head\",\n            \"reports_to\": \"CEO\",\n            \"description\": \"Leads engineering strategy, hiring, and delivery...\"\n          }\n        ]\n      }\n    ],\n    \"key_relationships\": [\n      \"Product and Engineering are co-located...\",\n      \"Marketing and Sales meet weekly on funnel metrics...\"\n    ],\n    \"org_chart_text\": \"CEO\\n├── VP of Engineering\\n│   └── ...\"\n  }\n}\n```\n\nThe system automatically detects these from your natural language input:\n\n| Dimension | How it's detected | What it shapes |\n|---|---|---|\nRegion |\nCountry/city names, legal references, currency | Employment laws, culture, currency, entity types, benefits, reporting standards |\nIndustry |\nDomain keywords (fintech, healthcare, etc.) | Which departments exist, regulatory embedding, key metrics, operational patterns |\nStage |\nFunding language (Series A, pre-seed), headcount, revenue context | Org depth, process formality, decision speed, role specialization, comp approach |\nTask type |\nAction verbs (hire, launch, reorg, comply) | Which perspectives need to be involved, output format |\n\nUse `@`\n\nshortcodes to override auto-detection:\n\n```\n/orgframework @emea @fintech @scaleup what's our Q3 hiring plan\n```\n\n**Input:**\n\n```\n/orgframework we're a 50-person fintech in Berlin expanding to Brazil\n```\n\n**What happens:**\n\n- Context detected: EMEA region, fintech industry, scaleup stage, expansion task\n- Fintech preset loaded — adapted for EMEA headquarters + Brazil expansion\n- Role files read for depth on key functions (compliance, legal, HR, payments)\n- Region profiles applied — CLT contracts, 13th salary, BCB licensing for Brazil\n- Custom org structure built for this specific scenario\n\n**Output:**\n\n```\nContext: EMEA → LATAM expansion | Fintech | Scale-up | Task: International expansion\n\n## Expansion Org Structure: Berlin HQ → Brazil\n\n### New roles (Brazil)\nBrazil Country Manager — reports to COO Berlin\n  Entity setup, local hiring, regulatory relationships\nBrazil Compliance Lead — reports to CCO Berlin, dotted to Brazil GM\n  BCB licensing, LGPD compliance, local AML\nBrazil Engineering Manager — reports to CTO Berlin\n  Local team, Pix integration, Portuguese localization\n\n### Existing Berlin roles supporting expansion\n- lgl-privacy: GDPR ↔ LGPD data transfer framework\n- fin-tax: Brazilian tax complexity\n- hr-recruiting: CLT contracts, 13th salary, Portuguese hiring\n\n### Key timeline\nMonth 1-2: Legal entity setup + BCB licensing\nMonth 3-4: Country Manager + Compliance Lead hired\nMonth 5-6: First 5 engineers onboarded\nnpm test\n```\n\nValidates:\n\n- All 537 role files exist and match the index\n- All role files have the correct expanded template structure\n- All 31 presets have valid JSON, required fields, and valid departments/roles\n- All region, industry, and stage profiles are present and configured correctly\n\n- Create a new\n`.md`\n\nfile in`.claude/orgframework/styles/`\n\n- Follow the existing format (summary, responsibilities, competencies, KPIs, career path, cross-functional relationships, regional nuances, industry variations)\n- Add the role ID to\n`reference_roles`\n\narray in`index.json`\n\n- Run\n`npm test`\n\nto verify\n\n- Create a new\n`.json`\n\nfile in`.claude/orgframework/presets/`\n\n- Follow the preset format (metadata, applicability, departments with roles, key relationships, org chart text)\n- Run\n`npm test`\n\nto verify\n\nThe repo includes a GitHub Actions workflow (`.github/workflows/ci.yml`\n\n) that runs `npm test`\n\non every push.\n\n- 537 hand-written reference roles across 30+ domains\n- 31 org presets for common structures\n- 6 crisis command templates\n- Compensation bands for 50+ roles across 4 regions\n- Region/industry/stage adaptation profiles\n- Cross-region expansion playbooks\n- Org chart visualization (Mermaid.js)\n- RACI matrix generator\n- Hiring plan generator from org structure\n- Role vacancy simulation\n- Maturity assessment against stage benchmarks\n- Budget calculator from structure + comp data\n- More presets (hospitality, manufacturing, logistics)\n- More roles in underrepresented domains\n\nMIT — build whatever org structure you need.", "url": "https://wpnews.pro/news/orgframework-537-hand-written-role-files-for-claude-code", "canonical_source": "https://github.com/korishnn/orgframework", "published_at": "2026-07-18 13:04:57+00:00", "updated_at": "2026-07-18 13:21:14.263892+00:00", "lang": "en", "topics": ["ai-tools", "developer-tools"], "entities": ["OrgFramework", "Claude Code", "Anthropic"], "alternates": {"html": "https://wpnews.pro/news/orgframework-537-hand-written-role-files-for-claude-code", "markdown": "https://wpnews.pro/news/orgframework-537-hand-written-role-files-for-claude-code.md", "text": "https://wpnews.pro/news/orgframework-537-hand-written-role-files-for-claude-code.txt", "jsonld": "https://wpnews.pro/news/orgframework-537-hand-written-role-files-for-claude-code.jsonld"}}