create-command

To create a Forge command, you generate a Markdown command file with YAML frontmatter containing a name and description, then store it in the .forge/commands directory to enable consistent discovery and execution within your dev workflow.

The required file structure for Forge commands involves a Markdown body outlining actionable steps and a SKILL.md frontmatter specifying the name and description, ensuring consistent filename-to-name mapping for project setup and discovery.

Yes, you can extend Forge command functionality by adding optional scripts, references, and assets directories alongside the main Markdown command file, allowing you to include supporting scripts and reference materials directly in the command structure.

Forge commands are discoverable by maintaining consistent filename-to-name mapping between the Markdown command file and the YAML frontmatter name property, ensuring the code-forge application can automatically locate and execute commands stored in .forge/commands.

Yes, YAML frontmatter is required to define a Forge command because it provides the essential name and description metadata that standardizes command files, enabling the Forge system to properly identify and execute project setup workflows.

When modifying commands in the .forge/commands directory, limitations include the strict requirement for YAML frontmatter and consistent filename-to-name mapping; deviating from this Markdown structure will prevent the Forge system from discovering and executing the command.