Quick Start¶

Get up and running with Dezycro in a few steps.

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 workspace switcher in the header, click + Create workspace to add another (e.g. one per team).

2. Create a Project (optional)¶

When you first sign up, Dezycro seeds a default My First Project for you — so you can skip this and use that. To organize work differently, create another with New project on Home or the workspace overview: a project represents a product or feature area and contains all related features, PRDs, and tests.

3. Connect your Knowledge Base (optional, recommended)¶

Before authoring your first PRD, give the workspace real product knowledge to ground on. In Workspace settings → Knowledge Base, connect Confluence and/or Linear, then click Import to run the import wizard — pick your spaces (or teams/projects), review the AI's document classifications, and start the import. Imported documents become workspace-level grounding that PRD/TRD authoring and chat retrieve from, so drafts start from your product's actual context instead of a blank slate. See the Knowledge Base connectors guide for details, or Document Ingestion to upload files directly.

4. Create a Feature¶

Click New Feature anywhere in the app. A feature is the smallest planned unit of behavior; it auto-creates two documents: PRD and TRD. The chooser offers three ways in:

Describe it — a sentence or two; Dezycro suggests a name + folder and seeds the PRD with your intent.
Upload / Import — drop existing markdown/text docs; each file becomes one proposed feature.
Connectors — import Confluence pages, one feature per page, copied into Dezycro or linked with Confluence as the source of truth. See the Confluence connector guide.

You can then author or refine each document via AI chat, the editor, or /<prefix>:dz-author in your coding agent (guided discovery → drafting → quality gate).

5. Generate Test Cases¶

Open your feature's Tests tab (right-hand panel). 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.

6. Run the Verifier¶

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

From the web UI's feature page, or
Via /<prefix>:dz-verify in your coding agent, 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 reports its results back to the workbook on its own. Once all enforced journeys pass — and the workbook's issue, task, and coverage gates are clear — the feature auto-transitions to VERIFIED.

7. Bring your coding agent in¶

Install the Dezycro CLI, run dezycro login and dezycro setup, then in your repo run /dezycro:init to bind it to your workspace. Your workspace's commands sync to the agent automatically (or run dezycro skills sync), and from then on the flow above runs from the terminal:

/acme:dz-work checkout          # start a session on a feature (acme = your workspace prefix)
/acme:dz-verify                 # run the verifier; results self-report to the workbook
/acme:dz-sync                   # record tasks, decisions and commits in the workbook

8. Make the agent remember¶

The first time you correct your agent — "we never use gRPC for new APIs", "always link the workbook task in the PR" — say so, and it records the rule in your workspace's Agent Playbook via /acme:dz-kb-learn. Every later session, in every agent on the team, consults the playbook before substantive work — and agents launched through dezycro run carry it as team rules on every request.

What next?¶

The full slash command reference 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.