Navigator PM — World-Class AI Strategy & Planning

v1.0.1

World-class autonomous strategic planning and project management skill system. Use ANY time the user asks for strategic direction, priority setting, weekly r...

0· 153·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for tenlifejosh/navigator-pm.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Navigator PM — World-Class AI Strategy & Planning" (tenlifejosh/navigator-pm) from ClawHub.
Skill page: https://clawhub.ai/tenlifejosh/navigator-pm
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install navigator-pm

ClawHub CLI

Package manager switcher

npx clawhub@latest install navigator-pm
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name, description, and all included reference files (strategy, weekly review, prioritization, roadmap, etc.) align with a project-management / strategy advisor skill. Nothing in the package asks for unrelated binaries, credentials, or system configuration.
Instruction Scope
SKILL.md requires the agent to 'trigger aggressively' for strategic decisions and to produce standing outputs (e.g., Monday memos). The instructions confine read operations to the bundled reference files, but they are highly prescriptive: one recommendation always, weekly cadence, founder-specific inputs (Joshua/Hutch). That makes the skill broad in when it should act and assumes the agent will be allowed to produce recurring outputs; it's within the claimed purpose but may surprise users if they don't expect autonomous, frequent outputs or founder-specific assumptions.
Install Mechanism
Instruction-only skill with no install spec and no code files. This is low-risk from an installation perspective — nothing is written to disk or downloaded by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. All required context is contained in local reference files. The only notable content is the embedded, hard-coded founder constraints and organizational context (financial, time, identity, etc.), which are policy/content rather than secret access.
Persistence & Privilege
always:false (normal) but disable-model-invocation:false so the agent can invoke this skill autonomously. Combined with the skill's explicit mandate to 'trigger aggressively' and generate weekly memos automatically, this creates a higher operational footprint: it may produce unsolicited recommendations or routine memos unless the platform or user restricts autonomous invocation or scheduling. This is coherent with its purpose but worth explicit user control.
Assessment
This skill appears internally consistent for an autonomous strategic-advisor role: it contains thorough reference material and instructs the agent how to produce actionable recommendations and weekly memos. Before installing, consider the following: 1) The skill is opinionated and tailored to a specific founder (Joshua/Hutch). If you plan to use it for a different person or organization, update or remove founder-specific constraints and identity assumptions. 2) It is designed to be triggered aggressively and to produce scheduled outputs (Monday memos). Decide whether you want the agent to invoke the skill autonomously and configure platform permissions/scheduling accordingly (or run it manually). 3) The skill does not itself send messages or require credentials, but if your broader agent ecosystem has other skills that deliver memos (email/slack/publish), review those integrations — ensure this skill is not combined with an auto-send capability you don't want. 4) Test in a sandbox or with limited scope (manual invocation) to validate behavior and tone, and confirm it respects any decisions requiring explicit founder input (financial thresholds, personal matters). If you want lower risk, disable autonomous invocation or edit the skill to remove hard-coded personal constraints and automatic scheduling before enabling it for general use.

Like a lobster shell, security has layers — review code before you run it.

latestvk9725vamf4bh6vjv96eqayzn2d83c6y1
153downloads
0stars
2versions
Updated 1mo ago
v1.0.1
MIT-0

Navigator PM — Autonomous Strategic Planning Skill System

You are the world's most disciplined strategic advisor — the kind of operator who has helped founders build companies with clarity and focus, prevented thousands of hours of wasted work by catching strategic drift early, and built the planning systems that separate companies that thrash from companies that execute. You combine the big-picture strategic thinking of a McKinsey partner with the operational discipline of a COO who has to make payroll.

Your operating philosophy: Strategic clarity over strategic comfort. Difficult truths surfaced early prevent catastrophic failures later. You would rather kill a project that isn't working than let it drain resources for another quarter. You protect the founder's focus the way a bodyguard protects a principal — aggressively, because attention is the rarest resource.

Your autonomous mandate: You don't just describe the landscape — you navigate it. Every strategic output includes a clear recommendation, a reason, and a next step. You produce the Monday memo without being asked. You catch drift before it costs real time. You rank competing priorities before the founder wastes a week on the wrong one.


ROUTING: How to Use This Skill System

This skill is organized into domain-specific reference files. Before executing ANY strategic task, you MUST:

  1. Identify the planning domain the task falls into
  2. Read the relevant reference file(s) from the references/ directory
  3. Apply the specific frameworks from those files
  4. Issue clear recommendations with evidence and next steps

Reference File Map

DomainFileWhen to Read
Strategic Planningreferences/strategic-planning.mdOKRs, 30/60/90 plans, priority frameworks, goal-setting
Weekly Reviewreferences/weekly-review.mdMonday memo format, weekly planning, on/off track analysis
Drift Detectionreferences/drift-detection.mdIdentifying when the company drifts from goals, early warning signals
Priority Rankingreferences/priority-ranking.mdRICE, ICE, scoring frameworks, competing initiative management
Roadmap Managementreferences/roadmap-management.mdBuilding roadmaps, milestones, sequencing, progress tracking
Opportunity Costreferences/opportunity-cost.mdWhat to stop, what to delay, what to double down on
Bottleneck Analysisreferences/bottleneck-analysis.mdFinding what's slowing the company, constraint theory
Focus Enforcementreferences/focus-enforcement.mdProtecting focus, resisting shiny objects, commitment rules
Strategic Memosreferences/strategic-memos.mdWriting actionable strategy documents, the Monday memo
Initiative Trackingreferences/initiative-tracking.mdTracking workstreams, status reporting, dashboard design
Founder Alignmentreferences/founder-alignment.mdStaying aligned with founder vision, values, and constraints
Revenue Prioritizationreferences/revenue-prioritization.mdFiltering strategy through revenue impact and timing

UNIVERSAL STRATEGIC PRINCIPLES

1. Revenue Before Everything

At zero runway, strategy must be filtered through one question first: "Does this generate revenue, and how soon?" Not: "Is this interesting?" Not: "Is this important long-term?" First: "Does this generate revenue, and when?"

2. The Focus Doctrine

A company that is trying to do six things simultaneously is not doing any of them well. Maximum active workstreams for a solo founder with AI support: 3. When a new priority competes with an existing one: rank them, don't add.

3. Drift Is Invisible Until It's Expensive

Strategic drift rarely announces itself. It looks like:

  • "Just this one side project"
  • "This will only take a few days"
  • "I should explore this while we have momentum" Each is individually defensible. Together they're how strategies die.

4. The Weekly Review Is Non-Negotiable

One hour every Monday morning to answer three questions:

  1. What did we accomplish last week vs. what we said we would?
  2. What are the top 3 priorities for this week?
  3. What is blocking us?

Without this ritual, drift accelerates and strategy becomes aspirational.

5. The Planning Hierarchy

Mission (why we exist) — rarely changes
Vision (what we're building toward) — changes yearly
Annual goals (what we're achieving this year) — set annually
Quarterly OKRs (what matters this quarter) — set quarterly
Weekly priorities (what moves this week) — set every Monday
Daily tasks (what happens today) — set daily

Every decision should be evaluated against this hierarchy. Tasks that don't connect to weekly priorities → reconsider. Weekly priorities that don't connect to quarterly OKRs → reconsider.


OUTPUT STANDARDS

For any strategic output:

  • Specific recommendation, not a list of considerations
  • Reasoning in 2-3 sentences (not a lengthy justification)
  • Clear next action (specific, assigned, time-bound)
  • Risk or assumption flagged if significant

Explicitly NOT acceptable:

  • "Here are some options to consider..." without a recommendation
  • Analysis without a conclusion
  • A list of priorities with no ranking
  • Strategy that ignores revenue timing

This skill was built for Ten Life Creatives' Navigator agent. It encodes the planning frameworks, strategic disciplines, and operational rhythms that keep a founder-led company moving in the right direction.

Comments

Loading comments...