Projects, features & documents

Projects, features, and the two document types (PRD + TRD) are the unit of work in Dezycro.

Projects

A project is the top-level grouping inside a workspace. Each project contains:

• Features — the unit of behavior (each with its own PRD/TRD + workbook)
• Ingested Documents — uploaded files used for RAG enrichment of PRDs and tests
• Settings — project-scoped defaults

The project page surfaces a stat row across the top (features, new, in-progress, complete, tests), the project's folders for grouping related features, and the feature list itself underneath. The Project ID copy chip next to the title is the same one CI Setup reads from.

Project status

Status	Meaning
Active	Currently being worked on
Archived	No longer active, preserved for reference

Archive / rename / delete projects from the project page or the sidebar context menu.

Features

A feature is the smallest planned unit of behavior — typically one user story or one related cluster. Features live inside a project and can be nested under directories for organization.

When you create a feature, Dezycro auto-creates three documents and an empty workbook for it.

Feature lifecycle

DRAFT → IN_PROGRESS → VERIFIED → RELEASED

Transitions are mostly automatic — see The Workbook → Lifecycle stages.

Folder-Aware Feature Creation

When creating a feature, Dezycro suggests a directory placement based on the feature name + existing project structure (RAG-backed). You can accept the suggestion, override with a different directory, or place the feature at project root.

The two documents

Every feature has two associated markdown documents:

PRD (Product Requirement Document)

Describes what should happen — user stories, acceptance criteria, the behavior the user can expect. There's no required schema; structure it the way that fits the feature.

The feature stepper at the top of the page (Product Requirements → Technical Requirements → Agent Context → Validation) shows the lifecycle and lets you jump between the four artifacts; the right panel runs continuous conflict detection against other PRDs in the same project.

TRD (Technical Requirement Document)

Describes how it'll be built. There's no required format — see the dedicated TRDs guide for what tends to work well, plus authoring and revision flow.

Document status

Each document moves through:

Status	Meaning
DRAFT	Work in progress
COMPLETE	Author considers it done
APPROVED	Reviewed + locked-in

You can edit any document at any time before APPROVED. After APPROVED, edits create a new revision (history is preserved).

Authoring methods

Three ways to write each document:

1. Web UI editor — direct markdown editing
2. AI chat in app.dezycro.ai — describe what you want, the AI drafts the document
3. /dezycro:author in the Claude Code plugin — guided state machine: discovery → clarifying Q&A → drafting → quality gate

For TRDs specifically, /dezycro:author --doc trd is the recommended path — it bakes the quality gate into the loop and won't let you finalize a TRD that doesn't address every PRD pillar.

Conflict detection

When multiple PRDs or PRD sections contain contradictory or overlapping requirements, Dezycro highlights the conflicts. You can:

• Review each conflict with the conflicting sections side by side
• Dismiss false positives
• Resolve by editing the underlying section