Skip to content

[Feature]: Argument hints for /speckit.* Claude Code commands #1951

@Heremeus

Description

@Heremeus

Problem Statement

When using slash commands like /speckit.constitution or /speckit.specify in
Claude Code, no hint is shown indicating that user input is expected. This leads
users to run the commands without arguments, resulting in degraded output. For example:

  • /speckit.constitution silently falls back to defaults assumed by Claude
  • /speckit.specify responds with "The feature description was empty. Please
    provide a description of the feature you'd like to specify."

There is no in-UI signal that arguments are required or even supported, which
creates a confusing first-time experience.

Proposed Solution

Claude Code command files support an argument-hint front matter field that
displays an inline prompt to the user when they invoke a command. Adding this
field to all relevant Spec Kit command files would surface the expected input
before the command runs.

Example for /speckit.specify:

argument-hint: Brief description of the feature you want to specify

This surfaces directly in the Claude Code UI as the user types the command,
making it immediately clear what input is expected.

Alternatives Considered

No response

Component

Agent integrations (command files, workflows)

AI Agent (if applicable)

Claude Code

Use Cases

No response

Acceptance Criteria

  • All Claude Code commands that accept user input have an argument-hint
    that accurately describes the expected argument

Additional Context

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions