skills.rest
remiboivin021
remiboivin021COMMUNITY
Explore all skills by this author →
GitHub

architect-security

Identify and govern architectural and security-sensitive repository changes with dual-trigger activation.

Updated Feb 19, 2026
Search Tags:#architecture#adr#governance#risk-management#security-review#change-control#architect-security
One-click install
npx skills add https://github.com/remiboivin021/synexis --skill architect-security
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect-security
Source: https://github.com/remiboivin021/synexis/tree/main/.agents/skills/architect-security
Command: npx skills add https://github.com/remiboivin021/synexis --skill architect-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps governance teams ensure that changes that are both architectural and security-sensitive are identified, evaluated, and controlled before they are merged into the system, preventing invariant violations and accidental exposure.

Core Features & Use Cases

  • Dual-trigger governance: enforces combined architectural and security review for relevant changes.
  • Risk framing and mitigation: produces a structured risk and control plan for downstream teams.
  • ADR-driven traceability: ensures decisions are documented and traceable with migration/rollback pathways.

Quick Start

Outline a dual-trigger governance plan for architect-security changes including migration, rollback, and validation steps.

Frequently Asked Questions about architect-security

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

FAQPage Schema
How do I govern architectural changes that impact security-sensitive boundaries?▼

Architectural security governance requires a dual-trigger review process to identify and control changes affecting modular boundaries, storage schemas, pipelines, config contracts, or trust boundaries. This ensures changes are evaluated before merging, preventing invariant violations and accidental exposure.

What is a dual-trigger governance plan for security reviews?▼

Dual-trigger governance enforces combined architectural and security review for relevant repository changes. It maps trust boundaries, ranks risks, produces a structured control plan, and ensures decisions are traceable with mandatory migration and rollback pathways for downstream teams.

How do I ensure traceability for architectural security decisions?▼

Ensure traceability for architectural security decisions using ADR-driven documentation. This approach records decisions traceably, requiring explicit migration and rollback pathways alongside verifiable downstream gates to validate system invariants after changes.

When do I need to map trust boundaries in repository changes?▼

Map trust boundaries in repository changes when modifications affect modular boundaries, storage schemas, pipelines, or config contracts. This explicit mapping is essential to rank security risks and establish verifiable downstream gates that prevent accidental exposure.

Can I outline a governance plan including migration and rollback steps?▼

You can outline a dual-trigger governance plan that includes mandatory migration, rollback, and validation steps. This plan ensures architectural and security-sensitive changes are evaluated with structured risk framing and ADR-driven traceability before integration.

Related Skills

Explore More Software Engineering Skills→
KimYx0207KimYx0207
160

meta-skill-creator

Create and refactor reusable agent skills with trigger boundaries and validation contracts.

Community
Advanced
lionbenjaminlionbenjamin
15

review_plan

Review implementation plans against specifications to identify gaps and risks.

Community
Advanced
EngineerWithAIEngineerWithAI
4

architecture-decision-records

Create and manage Architecture Decision Records in multiple formats.

Official
Intermediate
khapn-2933khapn-2933

tkm:predict-risks

Analyze proposed changes for architectural, security, performance, and UX risks.

Community
Advanced