Sign in to create and edit playbooks. Sign In Register

Verify Architecture & Code Organization

DSP-3 Order: #3 Elaboration Has Dependencies

Updated 1 month, 2 weeks ago

Guidance

Verify Architecture & Code Organization

Objective

Verify that the project has a defined code organization, technology stack, and working project structure. This goes beyond SAO.md existence (DSP-02) to check that the architectural decisions have been realized in the actual codebase or are clearly documented for a greenfield project.


Process

1. Check Project Structure Exists

For an existing project, verify:

Check What to Look For Source
Project root manage.py, package.json, Cargo.toml, or equivalent entry point DTA-04
Source directories Application code directories matching SAO.md structure DTA-04
Test directories tests/ or equivalent with at least one test file DTA-06
Dependency file requirements.txt, package.json, Cargo.toml, etc. DTA-04
CI/CD config .github/workflows/, Jenkinsfile, etc. (optional for greenfield) DTA-10

For a greenfield project (no code yet), verify that SAO.md contains:
- Explicit directory layout plan (from DTA-04)
- Technology stack decisions (languages, frameworks, databases)
- These will be used by BSP (Bootstrap Project) workflow to create the structure

2. Check Workflow & Skill Coverage

Scan the Junior Edda playbook export (e.g. .cursor/playbooks/Edda/) for available workflows:

Available Workflows:
  ESM  | Envision the System     | 7 activities  | ✅
  DTA  | Define Architecture     | 18 activities | ✅
  DSP  | Deploy Software Process | 6 activities  | ✅ (this workflow)
  BSP  | Bootstrap Project       | 8 activities  | ✅
  BPE  | Build Feature           | N activities  | ✅
  EST  | Estimate the Project    | 8 activities  | ✅

Scan for available skills (if any exist in the playbook skills/ directory):

Available Skills:
  skills/  | N skills found
  (others) | ...

Scan for available artifact templates:

Available Artifact Templates:
  artifacts/  | User_Journey_Template.md, Feature_File_Template_Gherkin.md, IA_Guidelines_Template.md, ...

3. Evaluate Readiness

Ready to proceed if:
- SAO.md has technology stack and directory layout (from DSP-02)
- Either project structure exists OR SAO.md documents the planned structure
- At least BPE workflow is available (the AI needs to know how to build features)

Not ready if:
- No technology stack defined in SAO.md → redirect to DTA-02 (Define Application Blocks)
- No directory layout in SAO.md → redirect to DTA-04 (Define Code Organization)
- No BPE workflow available → this is a critical gap, inform user

4. Report Summary

Architecture & Code Organization Check:
  Technology stack defined   | ✅ Django 5 + SQLite + HTMX
  Directory layout defined   | ✅ In SAO.md Section "Project Structure"
  Project structure exists   | ✅ 4 Django apps, tests/, docs/
  BPE workflow available     | ✅ Build_Feature/ (Junior Edda playbook export)
  Skills available           | ✅ N skills in skills/
  Artifact templates         | ✅ templates in artifacts/

Deliverables

  • ✅ Project structure verified or planned
  • ✅ Workflow coverage inventoried
  • ✅ Skill coverage inventoried
  • ✅ Artifact template coverage inventoried
  • ✅ All prerequisites met — or user redirected to specific DTA/ESM activities
  • ✅ Ready to proceed to DSP-04
Details
Order:
#3
Phase:
Predecessor:
DSP-2 Verify DTA Artifacts
Created:
Apr 12, 2026
Last Updated:
Sep 22, 2026
Workflow
Deploy Software Process

Check prerequisite artifacts (ESM, DTA), choose target AI IDE, and generate configuration (CLAUDE.md / copilot-instructions.md / Windsurf/Cursor rules) so AI …

View Workflow
Assigned Agent

No agent assigned

Required Skills

No skills linked

Rules

No rules linked.

Input Artifacts 1
Output Artifacts

No output artifacts