Quick Start Guide

Current Release

Current Release

Current version: v4.2.0

Step 1: Bootstrap DevSpark

Open a chat with your AI agent inside the target repository and paste the command for your agent:

GitHub Copilot

@workspace Follow the instructions at https://raw.githubusercontent.com/markhazleton/devspark/main/quickstart/devspark_quickstart_copilot.md

Claude Code

Follow the instructions at https://raw.githubusercontent.com/markhazleton/devspark/main/quickstart/devspark_quickstart_claudecode.md

Cursor

Follow the instructions at https://raw.githubusercontent.com/markhazleton/devspark/main/quickstart/devspark_quickstart_cursor.md

Codex

Follow the instructions at https://raw.githubusercontent.com/markhazleton/devspark/main/quickstart/devspark_quickstart_codex.md

For Codex-specific workflow guidance, see DevSpark and Codex.

Antigravity

Follow the instructions at https://raw.githubusercontent.com/markhazleton/devspark/main/quickstart/devspark_quickstart_antigravity.md

For Antigravity-specific workflow guidance, see DevSpark and Antigravity.

Any Other Agent

Follow the instructions at https://raw.githubusercontent.com/markhazleton/devspark/main/quickstart/devspark_quickstart_generic.md

The agent first asks only the install-critical questions, checks for existing DevSpark or legacy layouts, and only asks for project name, tech stack, and core principles when a constitution still needs to be created.

Run the same quickstart prompt again for upgrades or repairs. Every run checks .knowledge/entities/ and .knowledge/ontology/, initializes missing scaffold files, and classifies .documentation/ intake when that folder exists.

Step 2: Build Your First Feature

Once bootstrapped, run these slash commands in your AI agent's chat.

2a. Define Your Constitution

/devspark.constitution Security-first. TDD required. All public APIs must have documentation.

2b. Create the Spec

Describe what you want to build and why -- no tech stack yet. Keep it product-focused.

/devspark.specify Build a photo album organizer. Albums grouped by date, drag-and-drop reordering, tile-based photo previews.

/devspark.specify is route-aware. It recommends a one-off fix, quick spec, or full spec path, explains why, and asks you to confirm before it creates artifacts.

Anti-pattern: /devspark.specify Build a React app with Redux and PostgreSQL for photo management -- this locks you into a solution before the problem is fully understood.

2c. Refine the Spec (Optional)

Ask about user needs and constraints, not implementation details.

/devspark.clarify Focus on security and performance requirements.

Anti-pattern: /devspark.clarify Should we use WebSockets or SSE? -- save technology choices for the plan phase.

2d. Create the Implementation Plan

Now provide your tech stack. The plan translates product requirements into architecture.

/devspark.plan Use Vite with vanilla HTML/CSS/JS. Images stored locally, metadata in SQLite.

2e. Generate Tasks and Implement

/devspark.tasks

Run every gate named in the spec frontmatter. A full spec normally requires:

/devspark.checklist
/devspark.analyze
/devspark.critic

Then implement:

/devspark.implement

Use /devspark.verify after implementation when the change needs a focused behavioral or evidence check. Release performs the final mandatory revalidation.

Step 3: Review and Release

After implementation completes (spec status becomes Complete), draft the PR and review it:

/devspark.create-pr
/devspark.pr-review

When review finds issues, run /devspark.address-pr-review, synchronize the branch as needed, refresh the description with /devspark.update-pr, and run /devspark.pr-review UPDATE against the current commit.

The review checks that the spec is Complete and all tasks are done before recommending approval. Merge the PR after approval.

At release time, validate code, tests, knowledge, governance, and task linkage; archive completed work; update the version; and generate release notes:

/devspark.release

See the Release Guide for release validation and archival, and Implementation Lifecycle for the complete delivery flow.

What's Next

Edit this page