Skip to content

dongshuyan/compass-skills / skills/clear-communication

clear-communication

Verified

Use on every turn for all user-visible output, including one-line replies and progress updates. Make the main point easy to find, connect ideas clearly, and preserve the source's meaning. Use alongside task-specific skills.

references/logic-patterns.md

View on GitHub
# Logic Patterns

This reference gives compact models for choosing an information shape. The examples are illustrative; they are not fixed templates.

## A pipeline

Use a pipeline when later actions require earlier results:

```text
goal → prerequisites → action → check → outcome or recovery
```

Keep the check beside the action it validates. If a failure changes the next step, branch at the failure instead of hiding it in a final warning.

## A decision tree

Start with the observable condition, then name the branch and its consequence:

```text
What is the current state?
├─ state A → do A → verify A
└─ state B → do B → if B fails, recover or stop
```

Do not list branches before telling the reader how to identify them.

## A network

For a system with many relationships, give the reader a map before enumerating nodes:

```text
entry point → central nodes → dependent nodes
                         ↘ feedback or cross-link
```

Explain why the chosen traversal is useful. A network description may have a reading order without claiming that the system itself is linear.

## A narrative reveal

An opening result, flashback, or delayed explanation works when it creates a question and later answers it. Give the reader enough orientation to know whose result it is, when it matters, or what question is being answered. Each reveal should reduce a stated uncertainty rather than introduce an unrelated fact.

## A review pass

Mark each major unit with the relation it has to the previous one: `because`, `therefore`, `however`, `for example`, `if`, `after`, `while`, or `this changes`. Missing or contradictory relations are candidates for a bridge sentence, reorder, split, or explicit uncertainty label.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall