engineering-design

Engineering Design

Purpose

This skill transforms an approved project architecture into concrete engineering decisions.

It defines how the approved architecture will be implemented.

The primary output is ENGINEERING.md, which becomes the engineering specification for repository initialization and future implementation.

Engineering Design bridges architecture and implementation.

---

Lifecycle Stage

Architecture Design
        ↓
Engineering Design
        ↓
Repository Initialization

Architecture defines how the system is organized.

Engineering Design defines how that architecture will be implemented.

---

Role

Primary role:

Engineering Agent

This skill may also be executed by another reasoning-capable agent acting in the Engineering Agent role.

---

When to Use

Use this skill when:

• PROJECT.md has been approved;
• ROADMAP.md has been approved;
• ARCHITECTURE.md has been approved;
• engineering conventions must be defined;
• repository initialization is the next lifecycle stage.

Do not use this skill for:

• project discovery;
• roadmap creation;
• architecture design;
• repository initialization;
• implementation planning;
• production code.

---

Inputs

Required:

• PROJECT.md
• ROADMAP.md
• ARCHITECTURE.md

Optional:

• ADRs;
• project constraints;
• engineering assumptions discovered earlier.

Architecture should already be sufficiently stable.

---

Outputs

Produce:

• ENGINEERING.md

The document should define:

• programming language;
• runtime versions;
• dependency management;
• quality tooling;
• runtime technologies;
• repository structure;
• testing strategy;
• configuration strategy;
• development workflow;
• coding conventions;
• operational assumptions;
• deferred engineering decisions.

The result should provide sufficient information for Repository Initialization.

---

Procedure

Step 1 — Understand the Project

Review:

• project goals;
• roadmap;
• architecture;
• ADRs;
• engineering assumptions.