Platform skills

Every workspace ships with a set of platform skills — the dz-* commands Dezycro maintains and delivers into every workspace. They sync to developers exactly like workspace skills, under your workspace's prefix, so the same command is /acme:dz-work in one workspace and /mobile:dz-work in another — and it's always clear which workspace you're acting on.

Skill	What it does
dz-work	Start or resume a coding session on a feature; gates on approval and binds the session to the workbook
dz-author	Guided PRD / TRD authoring with a quality gate (--doc prd \| trd, --revise-existing)
dz-status	Compact workbook snapshot for the active feature
dz-sync	Sync tasks, decisions, commits, and issues from the current session into the workbook
dz-publish-spec	Detect and upload the feature's OpenAPI spec; kicks off the verifier build
dz-verify	Pull the verifier binary and run it; the binary self-reports results (--env <name>)
dz-import-features	Reverse-engineer an existing codebase into features with PRDs and TRDs
dz-kb-learn	Record a durable team rule in the Agent Playbook
dz-kb-recall	Consult the Agent Playbook before substantive work

Per-command usage — arguments, prerequisites, what each one does step by step — is in the Slash commands reference. The one command that is not a platform skill is /dezycro:init, which is built into the CLI because it runs before a repo is bound to any workspace.

Where they show up

Platform skills appear on the Skills page with a Platform badge. They're hidden by default so your team's own skills stay front and centre — use the Show N Dezycro skills toggle to list them. dezycro skills list --all does the same on the command line.

dz-kb-learn and dz-kb-recall

These two turn the workspace's Agent Playbook into your team's long-term memory.

/<prefix>:dz-kb-learn — capture durable knowledge. Records one durable, reusable team decision. The agent invokes it when someone states a lasting rule ("from now on…", "we always…", "don't do X again"), when PR-review feedback generalizes beyond the current task, or explicitly: /acme:dz-kb-learn use REST, not gRPC, for new APIs. It keeps the playbook trustworthy rather than noisy:

• Distills a timeless rule, not session narrative — "Use REST, not gRPC, for new service APIs", with the why and who decided.
• Dedupes before writing — if a relevant entry exists it's updated, never near-duplicated. Replaced rules stay visible as superseded so agents meeting legacy code know the change was deliberate.
• Refuses junk — no secrets, no task-scoped context (that belongs in the feature's workbook), no speculation, nothing already enforced by linters or CI.
• Never blocks work — if the playbook is unavailable or full, the agent says so in one line and moves on.

/<prefix>:dz-kb-recall — consult before building. Pulls relevant team decisions before substantive work — starting a new endpoint, a refactor, a design decision — or on demand: /acme:dz-kb-recall error response format. The agent runs a couple of targeted searches, reads the few most relevant pages, and applies what it finds silently, citing an entry only when it actually shaped the work. When things conflict, it surfaces the conflict instead of guessing — task vs. playbook, entry vs. entry, playbook vs. code.

Together they close the loop: corrections you give an agent today become rules every agent follows tomorrow. How the playbook also reaches agents as team rules on every request is covered in Agent Playbook → Team rules delivery.

Platform skill lifecycle

Platform skills stay updatable by Dezycro until your workspace takes them over:

You do	What happens
Nothing	Dezycro ships improvements automatically; developers get them on next sync
Edit the skill	Your version wins — the skill stops receiving platform updates. An "update available" hint appears when the bundled version moves ahead
Delete the skill	Opt-out for the workspace. The card stays on the Skills page so you can re-add it later
Reset to platform version	Discards workspace edits (or revives an opt-out) and restores the current bundled content

Platform skills can't be renamed — the name is how Dezycro identifies them across updates. Workspace skills can reference them like any other skill with @{skill:dz-verify}.