creating-commands

Generate Claude Code slash command files with structured frontmatter and validation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/BrendanShields/spec-flow --skill creating-commands-brendanshields
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-commands
Source: https://github.com/BrendanShields/spec-flow/tree/main/plugins/spec/skills/creating-commands
Command: npx skills add https://github.com/BrendanShields/spec-flow --skill creating-commands-brendanshields

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides the creation of Claude Code slash commands with well-structured frontmatter, clear prompts, and consistent naming.

Core Features & Use Cases

  • Choose templates (Basic, With Args, Workflow) and generate command files.
  • Document arguments and prompts, and enforce naming and help text standards.
  • Validate commands against a standardized checklist before publishing.

Quick Start

Gather requirements, select a template, generate the command file in .claude/commands/, and validate the frontmatter and structure.

Frequently Asked Questions about creating-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create Claude Code slash commands with proper structure?

Create commands by selecting a template (Basic, With Args, or Workflow), generating the command file in `.claude/commands/`, and structuring it with well-formed frontmatter, clear prompts, and consistent naming conventions that follow Claude Code standards.

What should I include in command frontmatter and validation?

Frontmatter must document arguments, define help text, and enforce naming standards. Validate your command against a standardized checklist covering structure, metadata completeness, and naming consistency before publishing.

Can I use templates to automate command generation?

Yes. Templates for Basic, With Args, and Workflow patterns automate file generation and enforce best practices, reducing manual setup and ensuring consistent structure across your command library.

What's the best way to document command arguments?

Document each argument in frontmatter with clear descriptions and type information. Use consistent naming and provide help text that explains purpose and expected values, making arguments discoverable and self-documenting.

When should I use the Workflow template instead of Basic?

Use the Workflow template when your command orchestrates multiple steps or requires sequential processing. Basic templates suit single-action commands; Workflow templates handle complex multi-step automation.