eng-team

Coordinates security-focused engineering across design, implementation and post-deployment stages via an 8-step workflow with ten specialized agents.

30|6|Updated Feb 2, 2026

Search Tags:#security #governance #engineering #threat-modeling #devsecops #threat-model

Ready to run

npx skills add https://github.com/geekatron/jerry --skill eng-team

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: eng-team
Source: https://github.com/geekatron/jerry/tree/main/skills/eng-team
Command: npx skills add https://github.com/geekatron/jerry --skill eng-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates a security-centered, multi-agent engineering process that spans system design, threat modeling, secure implementation, testing, governance, and post-deployment readiness to build trustworthy software.

Core Features & Use Cases

Ten specialized agents coordinate across architecture, implementation, security testing, incident planning, and governance to enforce security-first software development.
An 8-step workflow with phase gates ensures risk-based handoffs, persistent artifacts, and traceability from design to release.
Adversarial quality checks (/adversary) and constitutional governance ensure compliance with Jerry principles and rigorous evaluation of deliverables.

Quick Start

Kick off a new Eng-Team engagement by loading the playbook and starting Step 1 with eng-architect to initialize architecture and threat modeling.

Frequently Asked Questions about eng-team

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I implement DevSecOps across system design and post-deployment stages?▼

Threat modeling drives risk-based handoffs within this 8-step workflow, where the eng-architect agent initializes architecture and security design during Step 1 to enforce traceability before implementation begins.

What is threat-model-driven security governance for software engineering?▼

Threat-model-driven governance enforces security-first software development by applying constitutional principles and adversarial quality checks, ensuring compliance and rigorous evaluation of engineering deliverables across all phases.

How do I incorporate adversarial quality checks into secure engineering workflows?▼

Adversarial quality checks (/adversary) are enforced as mandatory gates for C2+ deliverables within the structured workflow, ensuring multi-level artifacts meet rigorous security and constitutional governance standards before release.

Can I use a multi-agent workflow for security testing and incident response planning?▼

Yes, ten specialized agents coordinate security testing and incident planning alongside architecture and governance, producing persistent artifacts and phase-gated handoffs to build trustworthy software across the development lifecycle.

What are the limitations of using automated agents for secure software development?▼

The workflow requires strict adherence to its 8-step phase gates and adversarial quality checks, meaning teams bypassing the structured eng-architect initialization or /adversary evaluation for C2+ deliverables will lose traceability and compliance enforcement.