Skip to content

JasonColapietro/suede-creator-skills / skills/suede-workflow-skills

suede-workflow-skills

Verified

Route requests across the full public Suede pack to the narrowest specialist and preserve the request verbatim. Use when asked "which Suede skill should I use?", when work crosses lanes, or when only the umbrella is installed. For next-action help: what’s next, recommend the next move, give me the prompt, expand prompt, or make it granular. NOT FOR: one clear lane (use its specialist), one multi-file implementation graph (use suede-graph-flo-xr), or parallel file ownership (use suede-agent-teams).

references/next-action-prompts.md

View on GitHub
# Next-Move Prompt Levels

The three prompt depths the router's Next move mode can hand back (short copy/paste, full operator prompt, granular steps) and what each must contain.

### Quick Prompt (Default)

Write 2-4 sentences that another capable agent can paste and run:

1. Name the selected skill or lane, exact target, and one concrete outcome.
2. Include the single current fact, scope boundary, or preservation rule most
   likely to change execution.
3. Name the observable done signal and its verification.
4. Add a stop condition only when a material blocker is plausible.

Do not dump field labels, the score breakdown, a long evidence list, or numbered
implementation steps by default. After the prompt, add exactly:

```text
Say "expand prompt" for the full operator version or "make it granular" for exact steps and commands.
```

### Expanded Prompt (On Request)

When the user says `expand prompt`, render the full self-contained prompt below.
Include only applicable fields and never leave placeholders such as `TBD` or
`<path>`.

```text
Use $<skill> to complete this task.

Target: <exact repo, worktree, route, URL, document, account, or surface>
Objective: <one concrete outcome>
Current verified state:
- <fresh fact and its source>
Authorized scope: <read-only, local edits, live mutation, or other exact boundary>
Preserve: <dirty work, copy, data, identities, or other invariants>
Source-truth order: <current sources in precedence order>

Required work:
1. <smallest complete sequence>

Done signal: <observable proof>
Verification:
- <command, readback, screenshot, URL, test, or response>
Stop and report if: <material ambiguity, unsafe mutation, failed gate, or missing authority>

Return: outcome, changed surfaces, verification evidence, caveats, and status.
```

### Granular Prompt (On Request)

When the user says `make it granular`, render the expanded prompt and decompose
`Required work` into atomic numbered steps. Include exact commands, absolute
paths, mutation checkpoints, expected readbacks, and stop conditions wherever
current evidence supports them. Do not invent missing commands or values; make
resolving a missing decisive fact the first step.

For multi-lane work spanning more than one specialist, start expanded and
granular prompts with `$suede-agent-teams` so the coordination lane owns the
handoff. For a single-lane task, start with the specialist the recommendation
names directly. Use exact absolute paths, URLs, handles, branch names, and
verification commands when current evidence provides them.
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated 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: 323kUpdated Claude CodeCodexVerifiedInstall