Spec-Driven Development Based on DSPI: Design-Specify-Plan-Implement

The provided content outlines a structured approach to software development called DSPI (Design-Specify-Plan-Implement) and describes how to set up documentation for this process within a project's repository. Below is an explanation of each phase along with the corresponding skill files that should be created in doc/.cortex/skills/:

1. DSPI Phases Overview

Design Phase

• Objective: Understand requirements and create a high-level design.
• Output:
  • 01_design.md: Contains the architectural overview, system components, and interactions.

Specify Phase

• Objective: Break down the design into detailed specifications.
• Output:
  • 02_specification.md: Detailed breakdown of requirements with acceptance criteria mapped to specific sections.

Plan Phase

• Objective: Create a step-by-step plan for implementation.
• Output:
  • Multiple task files (e.g., 01_task.md, 02_task.md): Each file contains clear objectives, steps, verification criteria, and dependencies.

Implement Phase

• Objective: Execute the tasks in order while verifying against specifications.
• Output:
  • Code changes as per the tasks

Read the full article at DEV Community

---

Want to create content about this topic? Use Nemati AI tools to generate articles, social posts, and more.