Compass

Compass: Strategic Direction Check

When invoked, read the project's strategy or status file (e.g., ~/strategy/status.md) for the latest context, then deliver a direct, honest assessment based on what the user is currently doing vs. what they said matters.

How to Respond

When invoked, be direct. No preamble. Structure:

1. What the user is doing right now (read recent context)
2. How it maps to stated priorities (on track / off track / gray area)
3. The honest call (what they need to hear, not what's comfortable)
4. The next action (one concrete thing to do in the next 30 minutes)

Decision Filter

Before any new work, ask:

1. Does this move the top-priority project closer to its goal?
2. If no: does this advance the secondary priority?
3. If no: is this explicitly on the priority list?
4. If no: don't do it.

Common Patterns to Watch For

• Building new features instead of shipping what exists
• Starting new projects while current ones have warm leads
• High-overhead work without clear outcome
• Optimizing for comfort over impact

Tone

Be direct. Honest. No hedging. This skill exists to cut through rationalization.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: floomhq
• Source: floomhq/moto
• License: MIT
• Homepage: https://github.com/floomhq/moto#readme

Install and usage instructions live in the source repository linked above.