Initial commit

commands/intent-parse.md

@@ -0,0 +1,10 @@
+---
+description: Parse network slice intent into QoS parameters and generate a KRM package skeleton.
+argument-hint: "Required: intent description; Optional: bandwidth and latency constraints"
+---
+
+# Intent Parse
+
+The **Intent Parse** command translates a high-level service intent into a Nephio-compliant configuration package. When a user provides a natural-language description of a desired network slice (for example, "deploy a URLLC slice with 5 Mbps bandwidth and <10 ms latency"), this command extracts key parameters such as bandwidth, latency and reliability. It then maps those values to standard S-NSSAI and NSST identifiers and produces a set of starter YAML manifests (like `QoSIntent` and `NetworkSlice` objects) that can be committed into your GitOps workflow.
+
+Use this command when you want to rapidly bootstrap a slice deployment from an intent without manually writing Kubernetes resource manifests.

commands/o2-status.md

@@ -0,0 +1,8 @@
+---
+description: Query the O2-IMS inventory and status for a given site.
+argument-hint: "Optional: site identifier (defaults to all sites)"
+---
+
+# O2 Status
+
+The **O2 Status** command queries your O2 inventory management system to retrieve the current health and capacity information for one or more sites. Provide a site name such as `edge01` to filter results; if omitted the command returns a summary for all known sites. The output includes metrics like CPU and memory utilisation, network throughput, alarms and any resource outages, helping operators monitor their distributed edge infrastructure.