internal-ops-repo

Direct product and engineering decisions to private operational documentation.

7|23|Updated Aug 9, 2015
One-click install
npx skills add https://github.com/gamedevpl/www.gamedev.pl --skill internal-ops-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: internal-ops-repo
Source: https://github.com/gamedevpl/www.gamedev.pl/tree/main/.claude/skills/internal-ops-repo
Command: npx skills add https://github.com/gamedevpl/www.gamedev.pl --skill internal-ops-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents product and engineering work from relying on missing, outdated, or sensitive operational context by directing decisions to the private ops repository while protecting confidential information from the public codebase.

Core Features & Use Cases

  • Operational Context: Locate guidance for go-to-market stages, launch gates, monitoring, backups, and operational readiness.
  • Planning and Compliance: Support decisions involving product risks, legal compliance, mobile apps, PWA and store submissions, pricing, growth, and creator experience.
  • Repository Boundaries: Keep private strategy, risk, legal, and operations content out of public issues, pull requests, commits, and code comments.
  • Use Case: Before changing a launch gate or store-submission workflow, consult the corresponding private ops documentation and preserve the repository's confidentiality rules.

Quick Start

Use the internal-ops-repo skill to identify the relevant private operations document and apply its guidance to the current planning, launch, compliance, or risk decision.

Frequently Asked Questions about internal-ops-repo

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

FAQPage Schema
How do I keep confidential operations data out of public repository commits?

To keep confidential operations data out of public repository commits, route product and engineering decisions to the private ops repository. This enforces leak-hygiene rules to prevent sensitive legal, risk, and strategy content from entering public issues, pull requests, and code comments.

Where can I find launch planning and app store submission guidelines for my product?

Find launch planning and app store submission guidelines within the private ops documentation repository. It directs your go-to-market stages, store-submission workflows, and launch gates to the correct operational files while maintaining repository privacy.

Does this internal ops guidance cover legal compliance and mobile app release workflows?

Yes, this internal ops guidance covers legal compliance and mobile app release workflows. It supports decisions involving PWA submissions, app-store releases, pricing, growth, and creator experience by referencing the appropriate private operational documentation.

How do I manage unresolved product risks without exposing sensitive strategy details?

Manage unresolved product risks by consulting the private ops repository for operational readiness and monitoring guidance. It applies leak-hygiene rules to ensure sensitive risk management and strategy details remain strictly out of public codebases and pull requests.

What prerequisites are needed to access the go-to-market and operations documentation?

Accessing the go-to-market and operations documentation requires entry to the private www.gamedev.pl-ops repository. Users must also adhere to the guidelines established in its AGENTS.md file to properly navigate operational and compliance decisions.