Skip to content

Quick Start

Get up and running with Dezycro in a few steps.

0. Sign in

Visit app.dezycro.ai and click Continue with Google. On first sign-in, Dezycro creates your user record and provisions a tenant + a Default Workspace for you. See Authentication for tenant vs workspace, SSO, and PAT details.

1. Create a Workspace (optional)

If the Default Workspace works for you, skip this. Otherwise, from the sidebar workspace switcher, click Create Workspace to add another (e.g. one per team).

2. Create a Project

Inside your workspace, create a project. A project represents a product or feature area and contains all related features, PRDs, and tests.

3. Create a Feature

Inside a project, create a feature. A feature is the smallest planned unit of behavior; it auto-creates two documents: PRD and TRD.

You can author each document in three ways:

  • AI chat — Describe your requirements conversationally; the AI drafts a structured document.
  • Manual — Write from scratch using the editor.
  • /dezycro:author (Claude Code plugin) — Guided state machine that walks you through discovery → drafting → quality gate.

Tip

You can also upload existing documents to enrich the AI's understanding of your product. See Document Ingestion.

4. Generate Test Cases

Open LogicStudio for your feature. Select the documents to generate tests from; Dezycro's AI produces test cases covering happy paths, edge cases, and negative scenarios.

Review the generated tests, toggle individual cases on or off, and finalize when you're satisfied.

5. Run the Verifier

Once your service implements the feature, publish your OpenAPI spec (from the feature page or via /dezycro:publish-spec) and run the verifier:

  • From the web UI's feature page, or
  • Via /dezycro:verify in the Claude Code plugin, or
  • In CI — see the Verifier docs

The verifier executes your journeys against the running service, asserts the responses match the spec + workbook expectations, and uploads results. Once all enforced journeys pass and all journey-linked tasks are pushed, the feature auto-transitions to VERIFIED.

What next?

  • Wire the Claude Code plugin into your editor for the day-to-day flow.
  • Read about the Workbook — the structured record of what's been decided, built, and verified for each feature.
  • Set up auth fixtures so the verifier can authenticate as your test users.