Quick Start Guide

Current Release: v2.3.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.

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. No CLI required.

Need terminal-driven setup or execution? See Other Ways to Get Started for CLI installation options, then use the runtime guidance in Harness Engineering.

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

Optionally validate first with /devspark.analyze or /devspark.critic, then:

/devspark.implement

Step 3: Review and Release

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

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

If you push more commits after review feedback or a rebase, refresh the description with /devspark.update-pr before re-reviewing.

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

At the end of the sprint, archive completed specs and generate release notes:

/devspark.release

See Implementation Lifecycle for the full spec status lifecycle and sprint cadence.

What's Next

Strict Harness Path

For delivery-integrity focused execution, use the strict harness template and run with an explicit write-capable adapter:

devspark harness run sample.harness.yaml --hands-off --adapter claude_code

If the latest run is not create-pr ready, inspect decision-packet.json and no-change-explainer.md before continuing.

Edit this page