Skip to main content
Version: v2.0.2

Your First Feature

Run the core Spec Kit command sequence for one feature, sync an Epic → Feature → User Story → Task hierarchy in Azure Boards, and verify the wiki artifacts.

Time: about 20–30 minutes the first time.

Prerequisites​

  • Completed Quick Start (authorized, seated, initialized, AI connected)
  • Chat panel visible on the right

This tutorial uses /speckit.* commands. If Settings → Commands Mapping is set to Default, the dropdown shows friendly names (for example, "Create Specification" instead of /speckit.specify). Those are the same commands.

The Workflows tab offers guided alternatives that use the same engine — try that after you understand this path.

Step 1: Set the constitution (once per project)​

/speckit.constitution Create principles focused on code quality, testing standards, user experience consistency, and performance requirements

Review the preview, then click Keep (or Regenerate for another draft). The constitution is saved at Speckit/specify/memory/constitution in the wiki.

Step 2: Specify the feature​

Describe what to build (not the tech stack yet):

/speckit.specify Build an app to organize photos into date-grouped albums, with drag-and-drop reordering and a tile preview inside each album.

A new feature folder is created under Speckit/specs/NNN-feature-name/ with a spec page.

Step 3: Clarify ambiguities​

/speckit.clarify

Answer the questions the AI asks in chat so gaps are folded back into the spec.

Step 4: Plan and break down tasks​

/speckit.plan Use Vite with minimal libraries. Prefer vanilla HTML, CSS, and JavaScript. Store metadata in a local SQLite database.
/speckit.tasks

This creates plan and tasks under the same feature folder.

Step 5: Create and sync work items (Visual)​

Open the Visual tab and sync one level at a time:

  1. On the Constitution card, open the magic-wand menu and sync Epics.
  2. On an Epic card, sync Features.
  3. On a Feature card, sync User Stories.
  4. On a User Story card, sync Tasks.

If Sync is disabled, generate the required wiki files first (constitution for Epics; feature spec for Features; tasks for Tasks). Details: Visual.

Confirm an Epic → Feature → User Story → Task tree appears on the canvas. Re-running Sync updates existing items instead of duplicating them.

Step 6: Verify the Wiki​

  1. Open your Azure DevOps Wiki.
  2. Browse Speckit/specs/NNN-feature-name/ and confirm spec, plan, and tasks.

Optional next commands​

  • /speckit.analyze — consistency and coverage gaps
  • /speckit.checklist — requirements-quality checklist
  • /speckit.converge — after code is pushed, append remaining tasks

You can also try a Workflows capability (for example Governance → Create project foundation). Catalog: Workflows.

Next steps​