SpecSquad Flow
Spec-driven team workflow for VS Code — Copilot slash commands, Cursor skills, Jira dispatch, and git branch orchestration.
Install
VS Code Marketplace (after publish):
ext install maazizit.specsquad-flow
Or: Open in VS Code
Manual VSIX — download from GitHub Releases → Extensions: Install from VSIX…
Features
- One-click init —
.specsquad/ config, specs/, Copilot /sq.* prompts, Cursor skills
- Jira + Git — dispatch Epic + Stories + child branches from
tasks.md
- Multi-IDE — same workflow in Copilot Chat (Agent) and Cursor
- Doctor — quick setup validation before your first dispatch
Quick start
- Install the extension (Marketplace or VSIX)
- Open your app repo in VS Code
Cmd+Shift+P → SpecSquad: Initialize Workflow in Workspace- Edit
.specsquad/config.yml (Jira project key, GitHub owner/repo)
- Enable Atlassian + github MCP in Copilot Agent chat
- Try
/sq.scope in Copilot Chat
Commands
| Command |
Description |
| SpecSquad: Initialize Workflow in Workspace |
First-time setup |
| SpecSquad: Sync Prompts (Copilot + Cursor) |
Regenerate /sq.* after extension update |
| SpecSquad: Doctor — Check Setup |
Validate files + MCP hints |
| SpecSquad: Open Installation Guide |
Full install & demo guide |
Slash commands (Copilot Agent)
/sq.scope
/sq.specify
/sq.dispatch --spec my-feature --dry-run
/sq.implement-guide
/sq.review --spec my-feature
/sq.publish-pr --spec my-feature
/sq.sync-status --spec my-feature
Requirements
- VS Code ≥ 1.96
- GitHub Copilot Chat (Agent mode) for slash commands
- Node.js 18+ for Atlassian MCP
- Jira Cloud project with Epic/Story types
- bash (macOS/Linux; Windows: Git Bash or WSL)
Configuration
After Init, edit .specsquad/config.yml:
project:
key: "YOUR-JIRA-KEY"
github:
owner: "your-org"
repo: "your-repo"
git:
integration_base: "develop"
pr_target: "develop"
MCP setup
Init creates .vscode/mcp.json if missing. Reload window, then authenticate Atlassian via OAuth in Copilot Chat.
Links
License
MIT
