Skip to content

Conversation

@DevenDucommun
Copy link

Summary

This PR adds support for Warp as an AI agent in spec-kit.

Changes

  • Added Warp to AGENT_CONFIG as IDE-based agent
  • Updated CLI help text to include warp option
  • Added Warp to README supported agents table and examples
  • Updated release package and GitHub release scripts
  • Added Warp support to bash and PowerShell agent context scripts

Configuration

  • Agent Type: IDE-based (no CLI check required)
  • Directory: .warp/commands/
  • Format: Markdown
  • Arguments: $ARGUMENTS

Testing

The code changes have been verified locally. Template package generation will work correctly in GitHub Actions' Linux environment (which has GNU coreutils).

After this PR is merged and a new release is created, users will be able to run:

specify init my-project --ai warp

- Added Warp to AGENT_CONFIG as IDE-based agent
- Updated CLI help text to include warp option
- Added Warp to README supported agents table and examples
- Updated release package and GitHub release scripts
- Added Warp support to bash and PowerShell agent context scripts
- Warp uses .warp/commands/ directory with Markdown format
Based on testing, Warp does not support reading custom slash commands from
.warp/commands/ directory. Instead, Warp reads WARP.md for project-specific
rules and context.

Changes:
- Created agent_templates/warp/WARP.md with spec-kit workflow documentation
- Updated release script to copy WARP.md instead of generating commands
- WARP.md includes all spec-kit commands with script paths
- Paths are rewritten to .specify/ structure via rewrite_paths()

Testing confirmed:
- Warp reads and applies context from WARP.md
- Custom slash commands only work via Warp Drive (cloud-based)
- This approach provides Warp's AI with spec-kit workflow knowledge
@DevenDucommun
Copy link
Author

Update: Fixed Integration Based on Testing

After testing with Warp, I discovered that Warp does not support reading custom slash commands from local files like .warp/commands/. Instead, Warp uses:

  • WARP.md for project-specific rules and context
  • Warp Drive (cloud-based) for custom prompts

Changes Made

✅ Created agent_templates/warp/WARP.md template with spec-kit workflow documentation
✅ Updated release script to copy WARP.md instead of generating .warp/commands/
✅ Tested integration - Warp successfully reads and uses the WARP.md file

How It Works

Users run specify init --ai warp which creates a WARP.md file. When users work in that project:

  1. User asks: "What spec-kit commands are available?"
  2. Warp reads WARP.md and lists all workflows
  3. User asks: "How do I run specify?"
  4. Warp guides them to run .specify/scripts/bash/setup-plan.sh specify

Testing Confirmed

User: what are the project setup instructions
Warp: [Reads WARP.md] TEST SUCCESSFUL

User: what spec-kit commands are available
Warp: Lists all spec-kit commands from WARP.md

User: how do I run the specify command
Warp: Run `.specify/scripts/bash/setup-plan.sh specify`

Comparison with Claude Integration

Claude: /speckit.specify → Direct slash command execution
Warp: Ask Warp → Guides to .specify/scripts/bash/setup-plan.sh specify

Future Enhancement

Submitted feature request to Warp for local project-based slash commands (similar to Claude's .claude/commands/). Until then, the WARP.md approach provides working integration.

The integration is now tested and functional! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant