sdd-design

To generate a technical design document for software changes, you can use an automated skill that drafts a design.md file. It outlines the implementation strategy, detailing architecture decisions, data flow, and file impacts to ensure stakeholder clarity before coding begins.

An automated technical design document includes the implementation strategy, architecture decision records with rationale and alternatives, data flow descriptions, and a comprehensive list of affected files with their specific modification types for full traceability.

To track file modifications when planning software architecture, the generated design document lists all affected files alongside their modification types. This file change tracking ensures every component impacted by the proposed software change is documented.

Yes, you can persist technical design documents using Engram or the filesystem. The design generation process supports artifact persistence through specified modes including 'engram', 'openspec', or 'hybrid' to ensure documentation is stored and retrieved effectively.

You need to create an architecture decision record for a new feature when a change is proposed and requires documented rationale. The technical design generation process automatically records choices and alternatives to align stakeholders on the implementation plan.

The best way to document data flow and implementation plans before coding is to generate a comprehensive technical design document. This approach automates the articulation of architecture decisions and file impacts, ensuring the 'how' of a change is clearly defined.