Using GitHub Spec Kit with GitHub Copilot CLI

I demonstrate how to use GitHub Spec Kit workflows from the newly announced GitHub Copilot CLI. The walkthrough shows how prompt files can stand in for custom slash commands that the CLI does not yet support natively.

■ Setup and workflow
- Install and launch the CLI, then use Spec Kit prompts for constitution, specification, clarification, planning, tasks, analysis, and implementation.
- Follow a podcast landing-page example, including reviewing generated files and running the site locally.

■ Compatibility and limitations
- See how the CLI reads instruction files and how to guide it to use prompts in the project’s prompts folder; native custom slash-command support and command suggestions are not demonstrated as available.
- The example uses PowerShell and notes that preview users can report issues with `/feedback`.

For developers exploring terminal-based coding agents or Spec Kit, this provides a practical workflow to try in their own projects. Install the CLI, adapt the prompt-folder guidance to your repository, and use `/feedback` to report issues.