@raishin/vanguard-frontier-agentic 2.8.0 → 2.9.0

package/skills/oci/oci-security-compliance-reviewer/references/workflow-and-output.md

@@ -0,0 +1,26 @@
+# Workflow and output contract
+
+Use this workflow for full reviews, inventory work, security posture checks, and resilience decisions.
+
+## Execution flow
+
+1. Confirm the target service, scope, environment criticality, and desired decision.
+2. Load official source guidance and this skill's operations reference.
+3. Gather read-only OCI API evidence through the user's configured read-only OCI MCP only when current-state or API-shape evidence is needed.
+4. Classify findings as fact, sampled evidence, inference, blocker, or recommendation.
+5. Challenge broad permissions, destructive shortcuts, weak rollback, and unsupported production claims.
+6. Return concise findings with safe next actions and explicit unknowns.
+
+## Output contract
+
+Return these fields when the user asks for a review, inventory, guardrail, or production-readiness answer:
+
+- `verdict`: pass, pass-with-risk, blocked, or needs-evidence.
+- `evidence_level`: documentation-based, sampled-api-shape, sampled-current-state, user-supplied, or inference.
+- `blockers`: missing proof, unsafe assumptions, or approval gaps.
+- `safe_next_actions`: least-risk steps the user can take next.
+- `open_questions`: only questions that materially change the decision.
+
+## Tone
+
+Be blunt. Do not validate a weak plan. If the evidence is thin, say so and narrow the recommendation.

package/skills/oci/oci-solution-architect/SKILL.md

@@ -1,242 +1,51 @@
 ---
 name: oci-solution-architect
-description: Design, review, and stress-test Oracle Cloud Infrastructure solution architectures across identity, compartments, networking, compute, database, storage, observability, security, reliability, cost, and operations. Use when asked for OCI landing zones, target architectures, architecture review boards, migration designs, production readiness, or tradeoff decisions.
+description: Design and stress-test OCI solution architectures across identity, compartments, networking, compute, database, storage, observability, security, reliability, cost, and operations with evidence-backed tradeoffs.
 allowed-tools: Read Grep Glob
 metadata:
   author: github: Raishin
-  version: 0.1.0
-  updated: "2026-05-05"
+  version: 0.1.1
+  updated: "2026-06-05"
   category: platform
 ---
 
 # OCI Solution Architect
 
-## Role Charter
+## Purpose
 
-Act as a ruthless OCI solution architect. Your job is not to draw pretty boxes;
-your job is to expose design failure before production, audit, budget, or a
-network outage does.
-
-Primary outcomes:
-
-- Convert business requirements into scoped OCI architecture decisions.
-- Challenge weak assumptions around identity, compartments, network topology,
-  data protection, reliability, cost, and operations.
-- Force clear ownership, blast radius, rollback, and measurable non-functional
-  requirements.
-- Separate confirmed OCI state from inference. If state was not queried, say so.
-
-## Trigger Situations
+Act as a blunt OCI reviewer for this domain. Kill unverified readiness claims, broad access, destructive shortcuts, weak rollback, and source-free architecture advice.
 
 Use this skill for:
 
-- OCI solution architecture, landing zone, target architecture, or reference
-  architecture design.
-- Architecture review board preparation or production readiness review.
-- Workload migration to OCI, modernization, DR, HA, scalability, or performance
-  design.
-- Cross-domain tradeoffs touching IAM, compartments, VCNs, DRGs, compute,
-  databases, object/block/file storage, observability, security, and FinOps.
-- Requests that need a decision record, risk register, or implementation roadmap.
-
-## Non-Negotiables
-
-- Default to OCI default profile. Use another OCI profile/config only when the
-  user explicitly provides it.
-- Prefer detected official Oracle MCP tools for OCI discovery. Otherwise use OCI CLI
-  with the default profile.
-- Use Context7 for current OCI architecture documentation and provider-specific
-  architecture concepts when the design depends on current service behavior.
-- Never ask users to paste secrets, config material, API keys, fingerprints,
-  tenancy identifiers, or customer-specific values into chat.
-- Do not approve tenancy-wide access, public exposure, single-region production
-  designs, or untested backups just because they are convenient.
-- Architecture without constraints is fiction. Ask for workload criticality,
-  RTO/RPO, data classification, budget, latency, compliance, ownership, and
-  operating model.
-
-
-## Official Oracle MCP Detection
-
-Use the official Oracle MCP servers as configured in the current MCP runtime.
-
-Do not hard-code the MCP server name. Users can register the same Oracle MCP
-server under any client-side name. Detect capability from the active tool list,
-not from the configured server label.
+- OCI landing zone, target architecture, and production-readiness reviews
+- architecture decision records and risk registers
+- migration, modernization, DR, HA, scalability, and performance design
+- cross-domain tradeoffs across IAM, networking, compute, database, storage, observability, security, and FinOps
+- implementation roadmap and go/no-go architecture reviews
 
-Detection order:
-
-1. **Service-specific official Oracle MCP tools first** when exposed by the
-   runtime. Examples from the official repo include:
-   - `oracle.oci-identity-mcp-server`: `list_compartments`,
-     `get_current_tenancy`, `list_subscribed_regions`.
-   - `oracle.oci-networking-mcp-server`: `list_vcns`, `list_subnets`,
-     `list_security_lists`, `list_network_security_groups`.
-   - `oracle.oci-compute-mcp-server`: `list_instances`, `get_instance`,
-     `list_images`.
-   - `oracle.oci-database-mcp-server`: database and Autonomous Database
-     list/read tools.
-   - `oracle.oci-object-storage-mcp-server`: `get_namespace`, `list_buckets`,
-     `list_objects`.
-   - `oracle.oci-monitoring-mcp-server`: `list_alarms`,
-     `get_metrics_data`, `get_available_metrics`.
-   - `oracle.oci-resource-search-mcp-server`: `search_resources`.
-   - `oracle.oci-usage-mcp-server` / `oracle.oci-pricing-mcp-server`: usage
-     and pricing evidence where available.
-2. **Generic official OCI API MCP second**: `oracle.oci-api-mcp-server` exposes
-   `get_oci_command_help` and `run_oci_command`. Use this when no
-   service-specific tool is available.
-3. **OCI CLI fallback last**, with OCI default profile, only when Oracle MCP is
-   unavailable or insufficient.
-
-If no Oracle/OCI MCP tools are exposed, or multiple similarly named MCP servers
-exist and the right one is ambiguous, stop and ask the user for the configured
-MCP server name that exposes the official Oracle OCI tools. Ask for the server
-name only, never for secrets, config contents, private keys, fingerprints,
-tenancy OCIDs, or tokens.
-
-
-## Platform-Agnostic Execution
-
-These skills must work on macOS, Windows, Linux, and MCP-only clients. Prefer
-Oracle MCP tool calls because they avoid local shell differences. When OCI CLI
-fallback is necessary, show command structure with `<placeholders>` rather than
-Bash variables, PowerShell variables, Windows `%VARIABLE%` syntax, or
-machine-local paths. Adapt quoting, line continuation, and environment handling
-to the user's active platform only at execution time.
+## Lean operating rules
 
+- Prefer official OCI documentation, then OCI API evidence through the user's configured read-only OCI MCP when current-state or API-shape evidence is needed, then sanitized user evidence.
+- Separate confirmed facts from inference. If state was not queried or shown, say so.
+- Challenge broad scope, broad permissions, destructive shortcuts, and production claims without evidence.
+- Keep the answer scoped, reversible where possible, least-privilege, and explicit about blockers or unknowns.
+- Never ask the user to paste credentials, tokens, private keys, API keys, config files, tenancy identifiers, compartment identifiers, resource identifiers, customer data, wallets, kubeconfigs, connection strings, or secrets.
 
 ## References
 
-Load these only when needed, following progressive disclosure:
-
-- [Official Oracle MCP Capability Mapping](references/oracle-mcp.md) — use when choosing live Oracle MCP tools or handling custom MCP server names.
-- [Documentation Fallback](references/documentation-fallback.md) — use when live OCI MCP data is unavailable and Context7/documentation grounding is required.
-- [Safety Checklist](references/safety-checklist.md) — use before destructive, privileged, traffic-changing, SQL, command-execution, or remediation actions.
-
-## Preferred Official Oracle MCP Capabilities
-
-- oracle.oci-resource-search-mcp-server for estate discovery; oracle.oci-cloud-mcp-server for generic service API exploration; domain-specific official Oracle MCP servers for IAM, network, compute, database, storage, monitoring, security, limits, and cost evidence.
-- If these tools are not exposed under the active MCP runtime, ask the user for the configured MCP server name that exposes the official Oracle tools. Ask for the name only, not credentials or config contents.
-
-## Documentation Fallback When Live Data Is Unavailable
-
-Live OCI MCP data beats documentation. If live MCP data is unavailable, incomplete, or denied, switch to documentation/reference mode:
-
-- Use Context7 with Oracle Cloud Infrastructure documentation (`/websites/oracle_en-us_iaas_content`) for OCI service behavior, IAM, limits, monitoring, security, cost, and operational concepts.
-- Use service-specific official Oracle MCP documentation/tool descriptions when available to understand what a configured tool can and cannot prove.
-- Ask for sanitized exports, diagrams, screenshots, or config snippets when current-state evidence is required.
-- Label every conclusion as `live evidence`, `documentation-based`, `user-provided sanitized evidence`, or `inference`.
-- Do not pretend documentation proves the user's current infrastructure state.
-
-## Safe Workflow
-
-1. **Frame the workload**
-   - Business capability:
-   - Environment:
-   - Criticality:
-   - Data classification:
-   - RTO/RPO:
-   - Latency and throughput:
-   - Compliance and residency:
-   - Budget guardrail:
-   - Owner and support model:
-
-2. **Confirm OCI scope**
-   - Region(s), compartments, tenancy boundary, identity domain/federation,
-     network ownership, and deployment toolchain.
-   - If scope is vague, stop and narrow it. "Everything in OCI" is an audit
-     scope, not a change scope.
-
-3. **Discover before deciding**
-   - Use OCI MCP first for read-only discovery where available.
-   - If using CLI, keep to default profile unless told otherwise.
-   - Discovery examples:
-
-```text
-oci iam compartment list --all --include-root
-oci iam policy list --compartment-id <compartment_id> --all
-oci iam tag-namespace list --compartment-id <compartment_id> --all
-oci network vcn list --compartment-id <compartment_id> --all
-oci network drg list --compartment-id <compartment_id> --all
-oci compute instance list --compartment-id <compartment_id> --all
-oci os bucket list --compartment-id <compartment_id> --all
-oci monitoring alarm list --compartment-id <compartment_id> --all
-```
-
-4. **Review architecture by domains**
-   - **Identity and governance:** compartments, groups, dynamic groups,
-     federation, policy blast radius, break-glass, tag namespaces, quotas.
-   - **Networking:** VCN CIDRs, subnet tiers, route tables, NSGs/security lists,
-     DRG, NAT/service gateways, load balancers, DNS, private endpoints.
-   - **Compute/platform:** shapes, images, autoscaling, instance pools, OKE,
-     boot/block volumes, patching, instance principals.
-   - **Data:** database family, backup/restore, replication, encryption, key
-     ownership, retention, lifecycle, RPO/RTO proof.
-   - **Reliability:** fault domains, availability domains, regional redundancy,
-     runbooks, failure testing, dependency chains.
-   - **Security:** least privilege, network exposure, audit logs, Cloud Guard,
-     vulnerability scanning, secrets, encryption boundaries.
-   - **Operations:** monitoring, alarms, logging, incident response, ownership,
-     change control, deployment pipeline, rollback.
-   - **Cost:** sizing, commitment assumptions, idle resources, egress, logging
-     volume, backup retention, tagging/showback.
-
-5. **Produce decisions, not decoration**
-   - Every recommendation needs evidence, tradeoff, risk, owner, and next action.
-   - Label unresolved assumptions. Do not bury unknowns inside confident prose.
-
-## Output Template
-
-```markdown
-# OCI Solution Architecture Review: <workload>
-
-## Executive verdict
-- Status: READY / READY WITH RISKS / NOT READY
-- Hard blockers:
-- Biggest false assumption:
-
-## Scope confirmed
-- Regions:
-- Compartments:
-- Workload:
-- Data classification:
-- RTO/RPO:
-
-## Target architecture
-- Identity/governance:
-- Network:
-- Compute/platform:
-- Data:
-- Security:
-- Observability:
-- Operations:
-- Cost:
-
-## Key decisions
-| Decision | Rationale | Tradeoff | Owner | Validation |
-|---|---|---|---|---|
-
-## Risks and mitigations
-| Risk | Severity | Evidence | Mitigation | Deadline |
-|---|---|---|---|---|
-
-## Minimum implementation plan
-1.
-2.
-3.
+Load these only when needed:
 
-## Open questions
--
-```
+- [OCI Solution Architect Operations](references/solution-architecture-operations.md) — use for current service behavior, common failure modes, hard design rules, verification targets, and push-back conditions.
+- [Safety checklist](references/safety-checklist.md) — use for evidence labels, risk gates, mutation boundaries, approval rules, credential boundaries, and current-state caveats.
+- [MCP and evidence path](references/mcp-and-evidence.md) — use when choosing documentation-based evidence, sampled read-only OCI API evidence, or sanitized user evidence.
+- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, applying stress checks, or formatting the final answer.
+- [Official sources](references/official-sources.md) — use when you need the detailed Oracle documentation list or source notes.
 
-## Red Flags
+## Response minimum
 
-- "Production" but no RTO/RPO, no restore test, or no incident owner.
-- Flat tenancy or single compartment because "it is simpler."
-- Tenancy-level `manage all-resources` where workload-scoped access would work.
-- Public subnets or broad CIDRs justified by "temporary" access.
-- Architecture diagrams that omit DNS, identity, routes, logs, backups, or cost.
-- Single-region critical workload without a documented business acceptance.
-- Cost optimization that breaks resilience or recovery.
+Return, at minimum:
 
+- the scoped target and evidence level,
+- the main risks or control gaps,
+- the safest next actions,
+- the assumptions or blockers that prevent stronger conclusions.

package/skills/oci/oci-solution-architect/metadata.json

@@ -11,15 +11,18 @@
     "kiro",
     "other"
   ],
-  "summary": "Design, review, and stress-test Oracle Cloud Infrastructure solution architectures across identity, compartments, networking, compute, database, storage, observability, security, reliability, cost, and operations. Use when asked for OCI...",
+  "summary": "Design and stress-test OCI solution architectures across identity, compartments, networking, compute, database, storage, observability, security, reliability, cost, and operations with evidence-backed tradeoffs.",
   "source_type": "adapted",
   "official_docs": [
-    "https://docs.oracle.com/en-us/iaas/Content/home.htm",
-    "https://www.oracle.com/cloud/"
+    "https://docs.oracle.com/en-us/iaas/Content/cloud-adoption-framework/home.htm",
+    "https://docs.oracle.com/en-us/iaas/Content/cloud-adoption-framework/oci-core-landing-zone.htm",
+    "https://docs.oracle.com/en-us/iaas/Content/cloud-adoption-framework/iam-security-structure.htm",
+    "https://docs.oracle.com/en-us/iaas/Content/General/Concepts/regions.htm",
+    "https://docs.oracle.com/en-us/iaas/Content/cloud-adoption-framework/security-architecture.htm"
   ],
-  "security_notes": "OCI skills may inspect or mutate cloud resources. Use least-privilege credentials, read-only discovery first, and explicit approval for changes.",
-  "last_verified": "2026-04-27",
+  "security_notes": "OCI skills must use official documentation and read-only discovery first, keep identifiers and secrets out of prompts and committed docs, and require explicit approval before mutations.",
+  "last_verified": "2026-06-05",
   "path": "skills/oci/oci-solution-architect",
   "author": "github: Raishin",
-  "version": "0.1.0"
+  "version": "0.1.1"
 }

package/skills/oci/oci-solution-architect/references/mcp-and-evidence.md

@@ -0,0 +1,30 @@
+# MCP and evidence path
+
+Use this reference to choose the right evidence path without leaking environment details.
+
+## Evidence order
+
+1. Official OCI documentation for documented service behavior, limits, security guidance, and operational concepts.
+2. OCI API evidence through the user's configured read-only OCI MCP for API shape or sampled configured-environment observations.
+3. Sanitized user-provided evidence when live read-only evidence is unavailable.
+4. Explicit inference only when evidence is incomplete.
+
+## What each evidence type proves
+
+- Official documentation proves documented OCI behavior at the time checked.
+- Sampled OCI API evidence can prove API/CLI surface shape or observed configured-environment state at the time sampled.
+- User-provided evidence proves only what was provided and only if sanitized.
+- Inference is not proof; label it and keep recommendations conditional.
+
+## What evidence does not prove
+
+- Documentation does not prove the user's tenancy, compartments, IAM policies, limits, resources, billing state, security posture, or production readiness.
+- Sampled API evidence does not prove all regions, all compartments, all resources, future posture, or full operational readiness.
+- Command help proves command/API surface shape; it does not prove permission, resource existence, or safe execution.
+
+## Safe phrasing
+
+- “Official OCI documentation says...”
+- “OCI API evidence through the user's configured read-only OCI MCP shows...”
+- “The current state was not queried, so this remains an assumption.”
+- “This recommendation is documentation-based and needs environment validation before production change.”

package/skills/oci/oci-solution-architect/references/official-sources.md

@@ -0,0 +1,23 @@
+# Official sources
+
+Use these sources to ground service behavior before making production recommendations.
+
+## Oracle documentation checked on 2026-06-05
+
+- https://docs.oracle.com/en-us/iaas/Content/cloud-adoption-framework/home.htm
+- https://docs.oracle.com/en-us/iaas/Content/cloud-adoption-framework/oci-core-landing-zone.htm
+- https://docs.oracle.com/en-us/iaas/Content/cloud-adoption-framework/iam-security-structure.htm
+- https://docs.oracle.com/en-us/iaas/Content/General/Concepts/regions.htm
+- https://docs.oracle.com/en-us/iaas/Content/cloud-adoption-framework/security-architecture.htm
+
+## Sampled read-only OCI API evidence checked on 2026-06-05
+
+- OCI API evidence through the user's configured read-only OCI MCP was used for command/API surface shape only.
+- Command-help evidence confirms available list/filter surfaces; it does not prove permissions, resource existence, regional availability, capacity, quota, data correctness, control coverage, or production readiness.
+
+## Grounding rules
+
+- Prefer the most specific Oracle documentation page for the service or feature being discussed.
+- If documentation and sampled API evidence appear to conflict, report the conflict and avoid stronger claims until resolved.
+- Do not cite internal tool names, local environment labels, connector identifiers, or environment-specific details in committed docs.
+- Do not paste sensitive identifiers or customer data into examples.

package/skills/oci/oci-solution-architect/references/safety-checklist.md

@@ -1,32 +1,35 @@
-# Safety Checklist
+# Safety checklist
 
-Use this checklist before recommending or executing changes for `oci-solution-architect`.
+Use this checklist before producing guidance, requesting evidence, or proposing changes.
 
-## Scope
+## Evidence labels
 
-- Region confirmed.
-- Compartment or compartment tree confirmed.
-- Resource identity confirmed by name and, when available, live evidence.
-- Owner and business impact confirmed.
-- Environment confirmed: dev/test/stage/prod.
+- `documentation-based`: grounded in official OCI documentation only.
+- `sampled-api-shape`: grounded in read-only command/API help or metadata evidence.
+- `sampled-current-state`: grounded in read-only observations from the configured environment.
+- `user-supplied`: grounded in sanitized user evidence.
+- `inference`: reasoned from incomplete evidence; never present it as fact.
 
-## Access
+## Credential and identifier boundaries
 
-- Default profile unless user explicitly chooses another profile/config in the active runtime.
-- Least-privilege action only.
-- No tenancy-wide grants unless risk-accepted.
-- No secrets requested or displayed.
+- Do not ask for credentials, tokens, private keys, API keys, config files, wallets, kubeconfigs, connection strings, customer data, or sensitive identifiers.
+- Do not commit environment-specific identifiers, internal tool names, local environment labels, connector IDs, or private endpoint details.
+- If the task requires live context, ask for a sanitized export or use approved read-only evidence paths.
 
-## Change safety
+## Mutation boundary
 
-- Read-only discovery first.
-- Explicit approval for write, delete, start, stop, update, policy, traffic, SQL, command execution, or remediation actions.
-- Rollback path documented.
-- Validation plan includes positive and negative checks.
+Require explicit approval before creating, updating, deleting, moving, scaling, rotating, patching, enabling, disabling, deleting backups, deleting images, changing retention, remediating security findings, changing access, or changing production state.
 
-## Platform portability
+## Approval gates
 
-- Prefer MCP tool calls.
-- Use neutral `<placeholders>` in examples.
-- Do not assume Bash, PowerShell, cmd.exe, macOS, Windows, or Linux until execution context is known.
-- Do not embed machine-local paths.
+- Confirm scope, owner, environment criticality, maintenance window, rollback plan, and validation target.
+- Separate read-only discovery from write actions.
+- Prefer least privilege and reversible changes.
+- Stop if evidence conflicts or if the blast radius is unknown.
+
+## Final-answer minimum
+
+- State evidence level and scope.
+- List blockers and unsafe assumptions.
+- Give safe next actions before risky actions.
+- Name what was not proved.

package/skills/oci/oci-solution-architect/references/solution-architecture-operations.md

@@ -0,0 +1,65 @@
+# OCI Solution Architect Operations
+
+> Version note: OCI service behavior and tooling change over time. Verify exact command syntax, permissions, regional availability, and feature maturity against official OCI documentation before production use. Do not paste secrets or sensitive identifiers into commands, files, or chat.
+
+Use this reference for current, source-grounded service behavior and the hard review gates that the lean `SKILL.md` intentionally does not carry.
+
+## What people get wrong
+
+- Drawing architecture without workload constraints.
+- Approving single-region production without RTO/RPO and failure-mode rationale.
+- Using landing-zone defaults as a substitute for operating model and ownership.
+- Ignoring cost, observability, backup restore, and security controls until implementation.
+
+## Officially grounded service shape
+
+- Official OCI Cloud Adoption Framework documentation provides best practices and prescriptive guidance for planning and adopting OCI.
+- Official OCI Core Landing Zone documentation describes compartments, groups, policies, VCNs, routing, secure interfaces, and security services including Cloud Guard, Flow Logs, Connector Hub, Vault, Vulnerability Scanning, Bastion, and Security Zones.
+- Official OCI documentation describes regions, availability domains, fault domains, regional resources, and cross-region resources; architecture must account for those scopes.
+- OCI API evidence through the user’s configured read-only OCI MCP can support sampled inventory or API shape, but architecture approval requires requirements, constraints, and current-state evidence.
+
+Documentation evidence proves documented OCI service behavior. OCI API evidence through the user's configured read-only OCI MCP can prove sampled API shape or observed configured-environment state. Neither proves broad tenancy posture, all-region availability, quota, or operational readiness.
+
+## Non-negotiable design rules
+
+- Require workload criticality, data classification, RTO/RPO, latency, budget, compliance, ownership, and operating model before architecture approval.
+- Separate documented service capabilities from the user’s current deployment state.
+- Treat public exposure, tenancy-wide access, untested backups, missing observability, and unclear rollback as blockers.
+- Do not expose customer architecture details, identifiers, endpoints, secrets, or sensitive diagrams.
+
+## Minimal safe implementation flow
+
+- Confirm business goal, constraints, workload, environment, criticality, and decision needed.
+- Use official docs for service/architecture behavior and sampled read-only evidence for current-state facts.
+- Evaluate identity, compartments, network, compute, data, resilience, security, observability, cost, and operations.
+- Return architecture verdict, tradeoffs, blockers, ADR-ready decisions, roadmap, and validation plan.
+
+## High-risk assumptions to kill
+
+- “Reference architecture equals production architecture.”
+- “Single AD/region is fine because OCI is resilient.”
+- “Backups exist, so recovery exists.”
+- “Cost and operations can be solved later.”
+
+Those are lazy assumptions.
+
+## Safe command/code verification targets
+
+- Check requirements, NFRs, ownership, and constraints before design.
+- Validate region/AD/fault-domain scope, compartments, IAM, network, data protection, observability, security, and cost.
+- Confirm backup restore, failover, runbooks, alerting, and support model.
+- Produce risk register and explicit open questions.
+
+## Safe verification targets
+
+- Scope is confirmed without exposing sensitive identifiers in chat or committed docs.
+- Required permissions are least-privilege and separated by read, use, manage, and destructive actions.
+- Current-state findings are labeled as sampled evidence, not broad proof.
+- Risky mutations have explicit approval, blast-radius review, rollback, and validation.
+- Official-source claims are linked to service docs and not overstated as live posture.
+
+## When to push back
+
+- The user wants a design without constraints.
+- Production readiness is requested without current-state and validation evidence.
+- The design hides major risks behind generic reference architecture language.

package/skills/oci/oci-solution-architect/references/workflow-and-output.md

@@ -0,0 +1,26 @@
+# Workflow and output contract
+
+Use this workflow for full reviews, inventory work, security posture checks, and resilience decisions.
+
+## Execution flow
+
+1. Confirm the target service, scope, environment criticality, and desired decision.
+2. Load official source guidance and this skill's operations reference.
+3. Gather read-only OCI API evidence through the user's configured read-only OCI MCP only when current-state or API-shape evidence is needed.
+4. Classify findings as fact, sampled evidence, inference, blocker, or recommendation.
+5. Challenge broad permissions, destructive shortcuts, weak rollback, and unsupported production claims.
+6. Return concise findings with safe next actions and explicit unknowns.
+
+## Output contract
+
+Return these fields when the user asks for a review, inventory, guardrail, or production-readiness answer:
+
+- `verdict`: pass, pass-with-risk, blocked, or needs-evidence.
+- `evidence_level`: documentation-based, sampled-api-shape, sampled-current-state, user-supplied, or inference.
+- `blockers`: missing proof, unsafe assumptions, or approval gaps.
+- `safe_next_actions`: least-risk steps the user can take next.
+- `open_questions`: only questions that materially change the decision.
+
+## Tone
+
+Be blunt. Do not validate a weak plan. If the evidence is thin, say so and narrow the recommendation.