suede-recommend-next-action

Solid

Next-action selector for this pack: reads current repo, terminal, plan, or handoff state, scores 2-4 candidate moves against goal alignment, unblocking, evidence, urgency, and leverage, and returns one recommended action plus a short, self-contained copy/paste prompt — expanding into a full operator prompt or granular steps only on request. Use when the user asks 'what's next', 'what should I do next', 'recommend the next move', 'give me the prompt', 'expand prompt', or 'make it granular', especially after a review, audit, plan, or stalled task. NOT FOR: executing the recommended action without the user's separate authorization, or coordinating a multi-lane build across specialists (use suede-agent-teams).

AI & Automation 165 stars 8 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
74
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Suede Recommend Next Action Recommend one action and package it as a short runnable prompt. Inspect current state read-only; do not execute the recommended action unless the user separately authorizes execution. Keep the full operator contract hidden until the user asks to expand it. ## Recommendation Workflow 1. Resolve the target and the user's actual done outcome from the current request, conversation, handoff, plan, repo, or live surface. 2. Check only the evidence needed to distinguish the next move. Prefer, in order: current terminal/repo/live state, current source documents, current plans or handoffs, then older memory. 3. Generate 2-4 candidate actions internally. Exclude work already verified as complete, adjacent cleanup, and actions outside the user's authorized scope. 4. Score each candidate from 0-2 on every criterion below. Recommend the highest total. | Criterion | 2 points | 1 point | 0 points | |---|---|---|---| | Goal alignment | Directly produces the user's done signal | Required prerequisite | Merely adjacent | | Unblocking | Unlocks a core path or at least two downstream steps | Unlocks one step | Unlocks nothing known | | Evidence | Confirmed by current source | Confirmable with one read-only check | Depends on an assumption | | Urgency | Active failure, deadline, security risk, or release gate | Needed for the active milestone | No current pressure | | Leverage | Fits one focused session and prevents rework or creates a reusable res...

Details

Author
JasonColapietro
Repository
JasonColapietro/suede-creator-skills
Created
2 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

action-runner

Turn a skill's recommendations into real, executed actions — open the tickets, file the issues, post the updates — safely: dry-run preview, risk-classified, approval-gated, then recorded back to the brain. Use when asked to act on a plan, file tickets from a checklist, create issues from a PRD, execute the recommended next steps, or wire a skill's output into GitHub/Linear/Slack. Produces a dry-run actions plan with per-action risk, executes only after approval via the connected action MCP, and logs what was done. Nothing acts silently.

1,228 Updated today
mohitagw15856
AI & Automation Solid

prompt-speculation

Use proactively after completing any task to suggest logical next steps. Also use when the user seems unsure what to do next, says "what now," "what else," "what should I do," "what's next," "continue," or pauses after a milestone. Anticipates what the user likely needs next based on context and proactively offers actionable suggestions.

4 Updated 3 days ago
irfad7
AI & Automation Listed

what-next

Propose the logical next step given the project's task backlog — a Planka board (via .claude/planka.json, when the `planka` MCP is reachable) or, failing that, a .claude/progress.md file — plus the current conversation and, if the project keeps one, a knowledge index such as `MEMORY.md`. Use when the user types /what-next or asks "what's next", "what should I tackle now", "what comes after this", or has just finished a chunk of work and wants a recommendation grounded in their tracked backlog. Works even with none of the above present, falling back to conversation + memory and saying so plainly. Read-only — proposes, never mutates the board, progress.md, or task state. Pairs with the `planka-tracking` skill, which sets up the board this skill reads.

1 Updated today
home-dev-lab