Introduction
Raaghu Spec Kit helps you describe what to build before you write code. It uses AI to turn that description into structured specifications, plans, and task lists in your project Wiki, and can create matching Azure Boards work items.
It is built on the open-source GitHub Spec Kit and works with Azure Boards, Repos, and Wiki. Spec files live under Raaghu Spec Kit/ in the wiki (older projects may still use Speckit/) — no repository commits are required for those files.
What you can do
Once Spec Kit is set up, the workspace has five tabs:
| Tab | What it is for |
|---|---|
| Dashboard | Project health cards and how ready your specifications are |
| Workflows | Guided cards for common work (governance, backlog, sprint, QA, release) — good if you prefer not to use slash commands |
| Visuals | See and sync an Epic → Feature → User Story → Task hierarchy into Azure Boards; also find and link existing Boards items |
| Intake | Upload BRD/PRD documents and create work items from the AI analysis |
| Activity | Timeline of creates, updates, deletes, and intake documents |
You also get:
| Area | What it is for |
|---|---|
| Chat & commands | Talk to your AI provider and run /speckit.* commands (right-hand panel) |
| Context Menu | From Boards or Queries, open a work item’s Context Menu → Raaghu to review, refine, or generate children and test cases |
| AI options | Use your own provider keys (Azure OpenAI, OpenAI, or Claude), or Raaghu-hosted AI credits |
Getting started
flowchart LR
A["1. Install"] --> B["2. Authorize"]
B --> C["3. Get a seat"]
C --> D["4. Initialize"]
D --> E["5. Connect AI"]
E --> F["6. First feature"]
Choose the path that matches your situation:
- Organization admin setting up Spec Kit for the first time — follow Admin Setup (install, start trial or subscribe or activate a license key, approve users, assign seats, set AI).
- Team member with a seat — follow Quick Start (~10 minutes). Ask an admin to connect AI if you do not see Settings.
- Build your first feature — prefer guided cards in Workflows, or the step-by-step command path in Your First Feature.