Oci product development
Compose secure OCI platform bundles for five product-development golden paths: API Gateway with Functions, Container Instances applications, OKE applications, Queue or Streaming event workers, and ADB-backed services. Use when a user asks to design, scaffold, or deploy an OCI application platform, select a runtime/ingress/data/delivery stack, or create platform-bundle.yaml. Produces infrastructure, delivery, IAM, OpenAPI, verification, and runbook artifacts—not business application logic.From its SKILL.md
npx -y skills add adibirzu/oci-skills --skill oci-product-developmentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
4.5 KB, as published. Nobody here has run it
OCI product development
Turn product requirements into an owner-explicit platform bundle. Artifact generation is offline; deployment requires a named context, preflight, plan review, and risk-specific approval.
Intake
Resolve runtime constraints, ingress audience, data durability, traffic/SLOs, compliance, recovery objectives, budget, region/availability, delivery source, and operator model. Default to private ingress, Vault references, least privilege, encryption, logs, alarms, budgets, and Terraform ownership.
Golden paths
| Path | Bundle selection | Primary handoffs |
|---|---|---|
| Secure API | Functions + API Gateway | developer-services, events-functions |
| Container application | Container Instances + load balancer | developer-services, networking-compute |
| OKE application | OKE + load balancer | oke-admin, developer-services |
| Event worker | Queue or Streaming + consumer | events-functions; developer-services for delivery only |
| Data-backed service | Functions + private ADB + API Gateway | autonomous-db, developer-services |
All paths compose IAM, networking, security, observability, cost, Terraform, and DevOps. See product-development.md for the ownership matrix and acceptance checks.
Bundle workflow
- Scaffold offline:
python3 ../../scripts/platform_bundle.py scaffold <golden-path> <output> --name <name> --context <context>; forevent-worker, select--event-transport queue|streaming. - Validate
platform-bundle.yamland inspect the generated ownership metadata. - Have each owning domain materialize its component in
terraform/; keep application code outside the bundle. - Validate Terraform and the CLI alternative; review IAM, quota, network, logging, public exposure, and secrets.
- Preflight (
./scripts/oci_preflight.sh -c "$COMPARTMENT_OCID"; stop if the resolved tenancy/compartment does not match the intended target), plan, get explicit user approval of the reviewed plan (honorsOCI_SKILLS_DRY_RUN=truefor a no-op preview), apply, and verify. Record named checks in the runbook. - Roll back through DevOps or the reviewed Terraform plan. Reconcile any break-glass CLI mutation.
If a context, provider, or approval is not available, still complete steps 1–2 and the offline ownership, OpenAPI-boundary, delivery-specification, and runbook work. Report the one later live gate instead of treating it as a block on design or scaffolding.
Common multi-step flows
| Request | Sequence |
|---|---|
| Generate a bundle | intake → choose golden path → scaffold → schema validation → owner review; no credentials required |
| Deploy a bundle | context select → preflight → domain materialization → validate → plan → approval → apply → named checks |
| Inspect health | oci-project status → bundle verification list → owning domain diagnostics |
| Tear down | refreshed Terraform destroy plan → dependency review → destructive approval → verify → compartment last via oci-project |
Boundary
Do not generate business handlers, domain models, UI, or application tests. Generate only platform/IaC, OpenAPI boundary, build/deploy specifications, IAM requirements, verification, and operations material.
Official documentation
Architecture Center · Cloud Adoption Framework · OCI DevOps. Full list in the product-development reference.
Open Knowledge Format grounding - every doc link here is registered and liveness-checked in the oracle-docs.md index (the pack's single source of truth). When extending this skill, cite the most specific official page through that index; the non-official MCP gateway is never a source of truth.