set-up-my-ops-info

You create a single source of truth for company operations context by centralizing operating details into a living document. This stops repeated discovery questions by maintaining consistent company-specific facts for downstream workflows.

To document quarterly priorities and vendor posture without starting from scratch, the skill reads any existing operations context and updates stale sections. It only requests missing required fields via single-question prompts, preserving your original founder content.

The best way to stop operations agents from asking repetitive company setup questions is to capture your operating context once into a reusable document. Downstream ops skills can then route to this centralized file for foundational execution details.

Yes, you can update an existing operations context document without losing your original company priorities. The skill atomically writes to the file while preserving existing founder intent, only filling in missing sections marked with TBD placeholders.

Generating ops documentation does not require inputting all company details at once. The skill identifies missing required fields and asks for them individually using single-question prompts, drafting a structured document without inventing missing information.

You use a structured operations context file for internal execution workflows to ensure all ops skills rely on consistent company facts. It captures company snapshot, operating rhythm, and key contacts atomically, preventing fragmented or contradictory operational data.