Help Center/ CodeArts Agent/ User Guide (CLI)/ TUI/ SDD
Updated on 2026-07-29 GMT+08:00
View PDF
Share

SDD

Specification-driven development (SDD) contains four phases: determination of required specifications, technical design, task planning, and code implementation. This structured process ensures that each step is controllable and that the history is traceable.

SDD Commands

Table 1 SDD commands

Command

Input

Output Path

Function

/sdd-new

/sdd-new + Requirement description (mandatory)

{Project root path}/.codeartsdoer/specs/Folder name of the generated file/spec.md

Generates the spec.md file based on the requirement description to define what to do, such as business behavior and requirement constraints.

/sdd-design

/sdd-design + Folder name of the generated file (optional). The system infers the folder name of the file generated in the previous phase from the dialog context.

CAUTION:

The directory ({Project root path}/.codeartsdoer/specs/Folder name of the generated file) and the generated spec.md file are mandatory.

{Project root path}/.codeartsdoer/specs/Folder name of the generated file/design.md

Generates the design.md file based on the spec.md file. The design.md file defines how to do it, such as the technical architecture and implementation solution.

/sdd-tasks

/sdd-tasks + Folder name of the generated file (optional). The system infers the folder name of the file generated in the previous phase from the dialog context.

CAUTION:

spec.md and design.md are mandatory.

{Project root path}/.codeartsdoer/specs/Folder name of the generated file/tasks.md

Generates the task list tasks.md based on spec.md and design.md.

/sdd-apply

/sdd-apply + Folder name of the generated file (optional). The system infers the folder name of the file generated in the previous phase based on the dialog context. This command is executed in the primary agent.

CAUTION:

spec.md, design.md, and tasks.md are mandatory.

Code and updated tasks

Executes coding tasks one by one based on tasks.md.

The Folder name of the generated file is automatically generated by a model. It may vary even if the same requirement description is input.

Generating Code Using SDD

  1. Enter the TUI development environment.

    1. Open the root directory of the target project.
    2. Right-click in the blank area and select Open Windows Terminal here.
    3. Enter /codearts in the terminal and press Enter to enter the TUI development environment.

  2. Create requirement specifications. In the TUI dialog box, enter /sdd-new Requirement description and press Enter to generate the spec.md file.

    Figure 1 Creating requirement specifications

    Open {Project root path}/.codeartsdoer/specs/Name of the generated file. You can find the generated spec.md file. If the generated spec.md file does not meet your expectations, you can manually modify it or use the agent to modify it.

  3. Create a technical design. In the TUI dialog box, enter /sdd-design and press Enter to generate the design.md file based on the spec.md file.

    Figure 2 Creating a technical design

    Open {Project root path}/.codeartsdoer/specs/Name of the generated file. You can find the generated design.md file. If the generated design.md file does not meet your expectations, you can manually modify it or use the agent to modify it.

  4. Create a coding task list. In the TUI dialog box, enter /sdd-tasks and press Enter to generate the tasks.md file based on the spec.md and design.md files.

    Figure 3 Generating a coding task list

    Open {Project root path}/.codeartsdoer/specs/Name of the generated file. You can find the generated tasks.md file. If the generated tasks.md file does not meet your expectations, you can manually modify it or use the agent to modify it.

  5. Perform coding tasks. In the TUI dialog box, enter /sdd-apply and press Enter. The agent will execute the coding tasks one by one based on the tasks.md file.

    Figure 4 Performing coding tasks

Parent Topic: TUI