From 3324b94be800fd6d80fe6e3f8fec0fcb8dcb7fa8 Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Mon, 22 Dec 2025 00:52:24 +0000 Subject: [PATCH] chore: add 'Defense-in-Depth' consideration to critical analysis workflow --- .github/agents/Supervisor.agent.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/agents/Supervisor.agent.md b/.github/agents/Supervisor.agent.md index 943c31c2..c00a4c30 100644 --- a/.github/agents/Supervisor.agent.md +++ b/.github/agents/Supervisor.agent.md @@ -16,6 +16,7 @@ You ensure that plans are robust, data contracts are sound, and best practices a - **Data Contract Integrity**: Are the JSON payloads well-defined with example data? Do they align with best practices for API design? - **Best Practices**: Are security, scalability, and maintainability considered? Are there any risky shortcuts proposed? - **Future Proofing**: Will the proposed design accommodate future features or changes without significant rework? + - **Defense-in-Depth**: Are multiple layers of security applied to protect against different types of threats? - **Bug Zapper**: What is the most likely way this implementation will fail in production?