[FEATURE] Configurable follow-up prompt suggestions for commands and skills

Resolved 💬 3 comments Opened Jan 21, 2026 by MarcusJellinghaus Closed Jan 25, 2026

Problem Statement

Claude Code sometimes suggests a "next prompt" after completing a command, but there's no way for users to influence or configure these suggestions. This makes it difficult to create guided workflows where one command naturally leads to another.

Use Case

When building custom workflows with commands/skills, users often have a logical sequence:

  • /plan_review/plan_approve/implement
  • /issue_analyse/issue_approve/plan_create
  • /implement/test/commit

Currently, users must remember or document these sequences manually. The suggested prompts feature could guide users through workflows automatically.

Proposed Solution

Add a suggested-next (or similar) frontmatter field for commands and skills:

---
description: Review the implementation plan
suggested-next:
  - label: "Approve plan"
    command: "/plan_approve"
  - label: "Request changes"
    command: "/plan_update"
  - label: "Discuss concerns"
    command: "/discuss"
---

# Review Implementation Plan
...

Expected Behavior

After a command completes, if suggested-next is defined:

  1. Display the configured suggestions as clickable prompts
  2. Fall back to AI-generated suggestions if not configured
  3. Allow multiple options for branching workflows

Benefits

  • Guided workflows: Users can create self-documenting command sequences
  • Reduced cognitive load: No need to remember what comes next
  • Team consistency: Enforce standard processes across team members
  • Discoverability: New users learn workflows by following suggestions

Alternatives Considered

  1. Documentation only: Document workflows in README - doesn't integrate with UI
  2. Hooks: Can trigger actions but can't influence UI suggestions
  3. Wrapper scripts: External tooling to chain commands - loses Claude Code integration

Additional Context

This would complement the existing commands/skills system by adding workflow orchestration capabilities, similar to how CI/CD pipelines define job dependencies.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗