AgentStack
SKILL verified MIT Self-run

Wayfinding

skill-lawzava-megapowers-wayfinding · by lawzava

Use when long-horizon work has unknown ownership, unresolved decisions, or unclear sequencing that prevents an honest specification or implementation plan.

No reviews yet
0 installs
7 views
0.0% view→install

Install

$ agentstack add skill-lawzava-megapowers-wayfinding

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Wayfinding? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Wayfinding

Reduce uncertainty until the work is ready for design or planning. Wayfinding is discovery and decision resolution, not delivery.

Invocation boundary

On Codex, agents/openai.yaml disables implicit invocation: invoke $wayfinding explicitly. Other harnesses consume the portable frontmatter and may still invoke this skill implicitly. The explicit-only policy is Codex-only.

Local contract

Use .megapowers/wayfinding// by default:

  • .megapowers/wayfinding//map.md: outcome, known regions, fog, source

trust, owners, named decisions, evidence, dependencies, and the current frontier.

  • decisions/.md: one question, its owner, evidence and source

trust, options, status, and consequences for the map.

The default .megapowers/ path is ignored personal workspace state. If the user wants a shared committed map, agree on a project-owned path first and use the same contract there. Never force ignored artifacts into git. Mirroring the map into an issue tracker is optional; the local artifacts remain complete without a tracker.

Loop

  1. Read the strongest available repository and external sources. Record what

each source establishes and how much it should be trusted.

  1. Create or refresh map.md. Separate known regions from fog, name owners and

unresolved decisions, record dependencies, and mark one current frontier.

  1. Resolve one decision at a time. Write or update its decision file with the

evidence, options, status, and map consequences.

  1. Update the map after each decision: propagate consequences, revise fog and

dependencies, then update the current frontier.

Never implement, execute a plan, start an autonomous run, or automatically commit while wayfinding.

Stop and hand off

  • Spec-ready: the outcome, constraints, behavior, and success criteria can

be designed without inventing missing facts. Hand off to megapowers:brainstorming.

  • Plan-ready: plan-ready is valid only when an approved design already

exists and the remaining uncertainty no longer prevents honest decomposition. Hand off to megapowers:writing-plans.

  • Blocked: name the missing external evidence, its owner, and what would

unblock the current frontier. Leave the map ready to resume.

These are terminal states. Do not hand directly to implementation or an autonomous run.

Source & license

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

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

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.