Menu

Individual skill

next-steps

0upvotes

Turn an ongoing task or conversation into evidence-informed opportunities and an actionable decision workspace. Use when the user asks what next, invokes $next-steps, or wants to explore, compare, combine, and prioritize possible directions. Adapt from a short conversational recommendation to a richer interactive exploration when the decision warrants it.

next-steps/SKILL.md

Read pinned source

Source commit 1acf58f08cca24b764a4352a6c30fed1f7fb9fb6

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
198
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Next Steps

Do the useful thinking before presenting the menu. Help the user discover and choose opportunities, not merely maintain a task queue. Lead with a point of view about the outcome and what could move it forward.

## Orient without reciting the conversation

Use the available context to recover the user's outcome, corrections, accepted choices, constraints, and unresolved questions. Newer decisions supersede older proposals. Do not reactivate abandoned work or ask the user to reconfirm settled preferences.

Keep completed work, user-reported changes, verified live state, proposals, and blockers distinct. Put routine operational status in a short line or expandable detail; let it dominate only when it genuinely blocks progress or presents material risk. Avoid ritual intent/confidence statements and repeated recaps.

## Discover before recommending

Do a bounded read-only evidence pass when it could change the options or their ranking. Inspect readily available project data; browse relevant current primary sources, credible practitioner examples, or competing approaches where useful. Bring back an actual finding, example, or comparison instead of turning every answer into a proposal to research later.
Back to top