Added comprehensive guidelines and responsibilities for the Data Engineer & ETL Architect role, including pipeline design, AI remediation, and compliance rules.
Three new specialist agents filling clear gaps in the current roster:
- engineering/engineering-data-engineer.md: ETL/ELT pipelines, Delta Lake,
Apache Spark, dbt, Medallion Architecture (Bronze/Silver/Gold), streaming
with Kafka, data quality with Great Expectations, cloud lakehouse platforms
(Fabric, Databricks, Synapse, Snowflake, BigQuery)
- engineering/engineering-technical-writer.md: Developer documentation,
API reference (OpenAPI), README templates, tutorials, docs-as-code
(Docusaurus/MkDocs), content quality standards, DX metrics
- specialized/specialized-developer-advocate.md: Developer relations,
DX auditing and improvement, technical content creation, community
building, GitHub engagement, conference talks, product feedback loops
Each agent follows the standard template with YAML frontmatter, identity,
core mission, critical rules, technical deliverables with working code,
workflow process, communication style, and success metrics.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Adds a specialized Security Engineer agent covering threat modeling,
vulnerability assessment, secure code review, and security architecture.
This fills a gap in the Engineering Division where no dedicated security
specialist existed.
Update 19 agent name: fields from slug-style (e.g. "engineering-ai-engineer")
or code-style (e.g. "ArchitectUX") to clean human-readable names (e.g.
"AI Engineer", "UX Architect"). Add missing YAML frontmatter to 2 spatial-
computing agents. All 51 agents now use consistent naming that aligns with
the NEXUS strategy docs.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Fix malformed YAML frontmatter with literal \n characters in agent files
- Fix insecure HTTP link in README (http:// -> https://)
- Update outdated year references (2024 -> 2025)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
