documentator

Extract decisions, roles, and timelines from the OWFINANCE Drive folder.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oteroweb/OWFINANCE2026 --skill documentator-oteroweb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentator
Source: https://github.com/oteroweb/OWFINANCE2026/tree/main/.agents/skills/documentator
Command: npx skills add https://github.com/oteroweb/OWFINANCE2026 --skill documentator-oteroweb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams discover, read, summarize, create, and update OWFINANCE2026 documentation. It preserves role ownership and keeps local summaries lean, reducing time spent searching through Drive.

Core Features & Use Cases

  • Discover the latest strategy, roles, planning, and operating context docs in the canonical OWFINANCE Drive folder.
  • Extract decisions, responsibilities, timelines, and dependencies into concise working notes.
  • Create or update canonical planning documents in the appropriate Drive hub and cross-link outputs with Notion backlog or local repo docs when needed.

Quick Start

Locate the latest strategy or planning document in the OWFINANCE Drive and generate a concise working note.

Frequently Asked Questions about documentator

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

FAQPage Schema
Can I cross-link Notion docs with planning files stored in Google Drive?

Cross-link Notion backlog or local repo docs with canonical planning documents in the appropriate Drive hub. This ensures outputs reference Drive sources only while keeping local summaries lean and preserving governance.

What is the best way to summarize strategy documents without exposing secrets?

The best way to summarize strategy documents is to extract decisions, responsibilities, and timelines into concise working notes. The process explicitly avoids exposing secrets and references Drive sources only to preserve governance.

Does this documentation summarization approach work for team role ownership tracking?

Documentation summarization supports role ownership tracking by extracting responsibilities and planning context from the canonical OWFINANCE Drive folder. It preserves role ownership and governance while returning concise working notes.

How do I create or update canonical planning documents in Drive hubs?

Create or update canonical planning documents by extracting decisions and timelines into the appropriate OWFINANCE Drive hub. Cross-link outputs with Notion or local docs while ensuring all references point to Drive sources only.

Why does my documentation summarization need to reference Drive sources only?

Documentation summarization references Drive sources only to maintain the canonical OWFINANCE folder as the single source of truth. This approach prevents conflicting local summaries and preserves role ownership and governance.