DimonSmart

Check whether implementation behavior matches durable product intent in `.idd/intent/`.

Implement behavior from current `.idd/intent/` product intent and verify the code against the relevant specification.

Update `.idd/intent/` product intent from confirmed implementation behavior.

Diagnose `.idd/intent/` product intent structure and recommend reorganizations without editing files.

Clarify real product intent before changing `.idd/intent/`, using focused customer-development questions and simplification options without editing product intent, planning implementation, or writing code.

Update current `.idd/intent/` product intent from a user-requested behavior change, preferring existing specs over new specs.

Import raw source material into structurally normalized IDD intent under `.idd/intent/`.

Run mechanical `.idd/intent/` consistency checks without editing files.

Update `.idd/intent/` product intent from confirmed implementation behavior.

Diagnose `.idd/intent/` product intent structure and recommend reorganizations without editing files.

Clarify real product intent before changing `.idd/intent/`, using focused customer-development questions and simplification options without editing product intent, planning implementation, or writing code.

Update current `.idd/intent/` product intent from a user-requested behavior change, preferring existing specs over new specs.

Import raw source material into structurally normalized IDD intent under `.idd/intent/`.

Run mechanical `.idd/intent/` consistency checks without editing files.

Create a new owning IDD spec, ADR, or spike only when no existing current document owns the area or decision.

Import existing specs/docs/planning documents or migrate an old `.worklog` tree into `.specs`. Use only when invoked manually by the user as /spec-import SOURCE_FOLDER.

Rebuild or update `.specs/INDEX.md` from current Spec Guided Dev documents, archived history, and temporary deviations.

Compare implementation with Spec Guided Dev documents and decide whether no update, cleanup, replacement, or temporary deviation is needed.

Review whether current changes follow Spec Guided Dev rules. Use before commits or when checking spec structure.

Create the next numbered Spec Guided Dev document before significant implementation work. Use when starting durable product intent, an ADR, a spike, or a temporary deviation.

Build and review ASP.NET Core endpoints, minimal APIs, controllers, middleware, and services following thin-handler and boundary-validation patterns.

Build and review Blazor components with correct render mode selection, component design, state management, and MudBlazor integration.

Apply C# nullable analysis attributes from System.Diagnostics.CodeAnalysis when `?`, non-nullable declarations, and ordinary flow analysis are not enough. Use for Try-patterns, guard helpers, late initialization, member null-state guarantees, generic nullability, and compiler flow hints around nullable warnings.

Create, edit, review, or polish README.md and README-like Markdown fragments in a calm, concrete, non-marketing engineering style close to the repository author's voice. Use for README.md, README*.md, README sections in Markdown files, and short documentation fragments intended to be copied into README.

Import existing specs/docs/planning documents from an explicitly provided SOURCE_FOLDER into .worklog. Use only when invoked manually by the user as /worklog-import SOURCE_FOLDER. SOURCE_FOLDER is required; if it is missing, ask for it and do not inspect or move source files.

Rebuild or update `.worklog/INDEX.md` from current worklog documents. Use after creating, archiving, replacing, importing, or reconciling worklog documents.

Compare an existing work document with the actual implementation, git diff, and recent commits. Use after significant implementation or investigation to decide whether an Outcome section, a follow-up work document, or no worklog update is needed.

Review whether current changes follow the worklog-driven development rules. Use before commits or when checking worklog structure.

Create the next numbered work document before significant implementation work. Use when starting a feature, user-visible behavior change, architecture decision, or spike.