In this article
Network ISA-95 Planner
| Field | Value |
|---|---|
| Kind | agent |
| Source | .github/agents/project-planning/network-isa95-planner.agent.md |
| Invocation | Selected from the chat agent picker as Network ISA-95 Planner |
| Interactive | Yes |
What it does
ISA-95-aligned network planning for secure edge Kubernetes to Azure connectivity and remediation roadmaps
When to use it
Use Network ISA-95 Planner to assess segmentation and plan secure edge Kubernetes connectivity to Azure for brownfield or greenfield sites. It organizes recommendations around zones, conduits, allowed flows, and operational constraints. Use a broader architecture reviewer when the decision is not primarily about site networking.
How to use it
- Select
Network ISA-95 Plannerand provide the site type, levels present, Kubernetes model, connectivity, segmentation, identity, logging, and change-window constraints. - For brownfield sites, describe reusable infrastructure and who can change it. For greenfield sites, describe target trust boundaries and connectivity expectations.
- Resolve missing intake facts before asking for a final alignment classification or remediation roadmap.
- Review the plain-language assessment and YAML companion together, including effort, confidence, and highest-risk exposures. Planning does not deploy network changes.
Example usage
Ask: "Assess our brownfield edge site from design/site-network.md. Reuse existing firewall and gateway controls where evidence supports them, ask for missing ownership details, and produce a staged remediation plan without deployment."
Expect an intake-gated assessment with explicit flows, constraints, and prioritized recommendations. Success means unknown site facts remain visible rather than becoming confident alignment scores.