Run any Skill in Manus with one click

map-it

Stars1

Forks0

UpdatedJuly 17, 2026 at 07:12

Resolve a foggy, multi-session goal into a frozen execution map that ship-it can consume — decisions, not deliverables. Chart a fog-of-war map of decision-tickets (only ticket what you can phrase sharply now), clear the research/decision frontier in parallel with HITL at each decision, and produce a frozen plan + a prepared DAG. Use when the goal is too big/foggy for one session, "chart this", "plan this epic", "I don't know the shape yet", or you can't yet authorize implementation. Its outcome is a decided plan; building is ship-it. Not for a foggy BUG (root-cause) or ready-to-build intent (ship-it).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ravidsrk

ravidsrk/orca-fleet

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

File Explorer

2 files

SKILL.md

readonly

name	map-it
description	Resolve a foggy, multi-session goal into a frozen execution map that ship-it can consume — decisions, not deliverables. Chart a fog-of-war map of decision-tickets (only ticket what you can phrase sharply now), clear the research/decision frontier in parallel with HITL at each decision, and produce a frozen plan + a prepared DAG. Use when the goal is too big/foggy for one session, "chart this", "plan this epic", "I don't know the shape yet", or you can't yet authorize implementation. Its outcome is a decided plan; building is ship-it. Not for a foggy BUG (root-cause) or ready-to-build intent (ship-it).
license	MIT
proof	doctrine-only
compatibility	HARD dependency: Orca runtime + orchestration skill (Orca CLI). A wayfinder/research worker playbook (mattpocock wayfinder + research) — one router per worker.

map-it — foggy goal → a frozen, decided execution map

You are the COORDINATOR. The terminal ARTIFACT is distinct from building: resolved decision tickets plus a frozen execution map. Valuable precisely when the user does not want, or cannot yet authorize, implementation. Inside ship-it, ordinary planning is a phase; map-it is invoked only when the goal fails the freeze bar: a testable acceptance criterion cannot yet be written for ≥1 in-scope capability, or ≥1 one-way decision's inputs are unknown. Below that bar, ship-it's own grill/freeze phase handles planning. Composes decide-and-freeze, decompose-dag (prepare only); rides gate-classification, liveness-resume, evidence-manifest. Worker TASK pack: matt — never co-mount.

Two terminal outcomes

MAPPED — destination named; every open question is a sharp ticket (resolved) or explicit "not yet specified"; human-resolved decisions; frozen plan/spec + prepared, verified, frozen-for- handoff DAG that ship-it can consume without re-grilling.
MAPPED-WITH-BLOCKED (degraded) — map is frozen for what is known, but ≥1 decision ticket is blocked on a human who has not answered; handoff lists blockers. Never reported as MAPPED.

Pipeline (plan, don't do)

NAME the destination first (fixes scope — everything past it is out of scope; everything before but
  not-yet-sharp is FOG) → chart the MAP as decision-tickets
  → FOG-OF-WAR rule: only ticket what you can phrase SHARPLY now (the test is "can you state the
    question, not answer it"). Not-yet-sharp → "not yet specified".
  → clear the FRONTIER in parallel: Research tickets (AFK) gather evidence; Decision/Grill tickets are
    HITL classified mechanical/taste/one-way per `gate-classification.md` (the agent never stands in
    for the human's side); one decision per session; resolving a ticket clears fog and graduates
    newly-sharp questions into fresh tickets
  → when the route is clear: FREEZE the plan/spec (decide-and-freeze) + PREPARE the DAG (decompose-dag,
    materialize but do not dispatch)
  → HANDOFF ARTIFACT CHECKLIST (ship-it adopts these without re-decomposing):
    · freeze commit SHA + path to frozen plan/spec
    · prepared DAG artifact path + task-id ↔ slice table
    · open "not yet specified" / blocked ticket list
    · evidence manifest naming MAPPED or MAPPED-WITH-BLOCKED

Convergence proof

The destination is named; every open question is either a sharp ticket (resolved or blocked) or an explicit "not yet specified"; every decision ticket was resolved by the HUMAN (not the agent) or is explicitly blocked; a frozen plan/spec exists; a materialized, verified, FROZEN-for-handoff DAG exists (decompose-dag's prepare-only completion — committed by freeze, not dispatch) that ship-it can consume without re-grilling. The mission produces DECISIONS, not deliverables — no production code is written. Handoff checklist complete.

Ledger + supervision

Header per liveness-resume.md: RUN · COORDINATOR · BASE=- · FORK_POINT=- · T0 · SOURCE · WIP (SOURCE = destination + freeze SHA when frozen). Rows include Orca task id + decision ticket fields. Multi-session by design: stalls → WATCH; death → RESUME scoped to header coordinator + ledger task ids — never re-grill resolved tickets.

Anti-patterns

The agent answering its own decision/grill tickets (HITL leak). Charting fog you can't phrase now. Resolving more than one decision per session. Sliding into building (that's ship-it — hand off at freeze). Re-decomposing a prepared DAG in ship-it (orphans task ids).

ship-it (consumes the frozen map), root-cause (a foggy BUG, not a foggy plan).

More from this repository

same repository

oss-contribute

ravidsrk/orca-fleet

Turn a bounded set of issues on a repo you do NOT control into landed open-source contributions. Each actionable issue is skeptic-triaged (including a search of the upstream repo's OPEN PRs, not just its code), built on a fork with a failing-first test, reviewed build-blind, and opened as an etiquette-correct PR against the upstream default branch — or, where a maintainer PR already exists, shared as a quoted review-assist comment (an alternative PR only if maintainers invite one). The loop re-enumerates until the actionable set is dry. Merge is the maintainer's; the fleet never merges. Use when "contribute to this project", "open PRs for these upstream issues", "help out this OSS repo", "send fixes upstream", "we only have a fork". Not for a repo you own and can merge (that is clean-sweep — merged-SHA closure) and not for building a net-new project (ship-it).

2026-07-171

clean-sweep

ravidsrk/orca-fleet

Exhaust a finite backlog of findings to zero, PR-per-finding, on Orca. Sources: an audit/adversarial-review document, the issue tracker, or verified false documentation claims. Each finding is skeptic-triaged (reproduced or refuted with evidence), fixed on an integration branch with a failing-first test, build-blind reviewed, merge-verified, and closed with a linked SHA; the loop re-enumerates until dry. Use when "clean sweep", "close every issue", "drain the backlog", "fix everything in this audit", "the README lies — verify and fix it", or a broken test that fails deterministically (N/N, cause findable — deflake-it routes those here). Not for security/perf/deps/coverage-gaps/flakes (those are harden-it / speed-it / modernize-it / prove-it / deflake-it — different convergence proofs) and not for building new work (ship-it).

2026-07-171

ship-it

ravidsrk/orca-fleet

Turn intent or a frozen spec into a released, verified outcome on Orca. Entry is either a frozen spec (validate → decompose) or raw intent (grill → freeze → decompose); after freeze both enter one canonical pipeline: decompose → build (tested slices) → acceptance review → runtime-prove → land → release → observe, stopping at the highest release state you're authorized to reach (BUILT / PROMOTION_READY / RELEASED / DEPLOYED_AND_VERIFIED). Use when "build and ship this", "spec to shipped product", "ship this feature", or an autonomous build-to-release run. Not for closing an existing backlog (that's clean-sweep) or a foggy goal that needs charting first (that's map-it).

2026-07-171

prove-it

ravidsrk/orca-fleet

Give every critical path a test that dies under a semantics-preserving mutation. Map the untested critical surface (coverage × call-graph of the money/auth/data paths), write characterization tests that assert real behavior, prove each earns its keep by failing at its assertion under a mutation (harness still runnable — a compile break is not proof), and route surfaced bugs to a fix or backlog, looping until every confirmed critical path is mutation-audited. Use when "close the test gap", "cover the critical paths", "test debt", characterization/mutation testing — it owns missing coverage, not broken tests. Not for flake eradication (deflake-it), a deterministically failing test (clean-sweep), or building features with tests from the start (ship-it).

2026-07-171

harden-it

ravidsrk/orca-fleet

Establish a threat model and close it: audit → prove exploits → fix → RE-ATTACK the fix and audit the whole vulnerability class → re-audit, looping until a fresh full audit finds zero unrefuted P0/P1. STRIDE + OWASP Top 10 + OWASP LLM Top 10 + supply-chain. Use when "harden this", "security sweep", "red team", "close the security loop", or an unattended audit-fix-verify security run. The full adversarial loop — for a bounded per-diff security check use review-it's risk lens. Not for general backlog drain (clean-sweep) or a single PR verdict (review-it).

2026-07-171

deflake-it

ravidsrk/orca-fleet

Eliminate intermittent test failures to a declared confidence contract. Detect flakes by repeat-run + CI retry history, diagnose each with a loop that RAISES the failure rate (never a theory), fix the root cause and ratchet it red-by-revert, then re-run the whole suite for a consecutive green streak — local AND in CI — looping until the streak holds. Retry-wrappers as fixes are banned and grep-checked. Use when "kill the flaky tests", "deflake the CI", "flake zero", a flaky/intermittent suite. Not for a single hard bug with no suite-rate contract (root-cause) or deterministic failures (clean-sweep).

2026-07-171

name	map-it
description	Resolve a foggy, multi-session goal into a frozen execution map that ship-it can consume — decisions, not deliverables. Chart a fog-of-war map of decision-tickets (only ticket what you can phrase sharply now), clear the research/decision frontier in parallel with HITL at each decision, and produce a frozen plan + a prepared DAG. Use when the goal is too big/foggy for one session, "chart this", "plan this epic", "I don't know the shape yet", or you can't yet authorize implementation. Its outcome is a decided plan; building is ship-it. Not for a foggy BUG (root-cause) or ready-to-build intent (ship-it).
license	MIT
proof	doctrine-only
compatibility	HARD dependency: Orca runtime + orchestration skill (Orca CLI). A wayfinder/research worker playbook (mattpocock wayfinder + research) — one router per worker.

map-it — foggy goal → a frozen, decided execution map

Two terminal outcomes

MAPPED — destination named; every open question is a sharp ticket (resolved) or explicit "not yet specified"; human-resolved decisions; frozen plan/spec + prepared, verified, frozen-for- handoff DAG that ship-it can consume without re-grilling.
MAPPED-WITH-BLOCKED (degraded) — map is frozen for what is known, but ≥1 decision ticket is blocked on a human who has not answered; handoff lists blockers. Never reported as MAPPED.

Pipeline (plan, don't do)

NAME the destination first (fixes scope — everything past it is out of scope; everything before but
  not-yet-sharp is FOG) → chart the MAP as decision-tickets
  → FOG-OF-WAR rule: only ticket what you can phrase SHARPLY now (the test is "can you state the
    question, not answer it"). Not-yet-sharp → "not yet specified".
  → clear the FRONTIER in parallel: Research tickets (AFK) gather evidence; Decision/Grill tickets are
    HITL classified mechanical/taste/one-way per `gate-classification.md` (the agent never stands in
    for the human's side); one decision per session; resolving a ticket clears fog and graduates
    newly-sharp questions into fresh tickets
  → when the route is clear: FREEZE the plan/spec (decide-and-freeze) + PREPARE the DAG (decompose-dag,
    materialize but do not dispatch)
  → HANDOFF ARTIFACT CHECKLIST (ship-it adopts these without re-decomposing):
    · freeze commit SHA + path to frozen plan/spec
    · prepared DAG artifact path + task-id ↔ slice table
    · open "not yet specified" / blocked ticket list
    · evidence manifest naming MAPPED or MAPPED-WITH-BLOCKED

Convergence proof

Ledger + supervision

Anti-patterns

ship-it (consumes the frozen map), root-cause (a foggy BUG, not a foggy plan).