easysdd-onboarding

To onboard a repository into the EasySDD workflow, the system scans your project to determine if it is greenfield or requires migration, then generates the easysdd root structure including architecture, features, issues, and learnings directories.

Migrating scattered architecture docs involves scanning for existing files in directories like docs/ and producing a mapping plan, which requires your explicit confirmation before restructuring them into the easysdd skeleton.

Yes, you can bootstrap an easysdd skeleton for a greenfield repository, which creates the full directory structure including architecture/design.md, root directories, and necessary tool references to initiate your project.

The onboarding process does not strictly require an existing AGENTS.md file to run, but it ensures that the presence and configuration of an AGENTS.md file is explicitly considered during the repository integration.

Bootstrapping the easysdd skeleton generates a root structure containing dedicated directories for architecture, features, issues, learnings, decisions, tricks, explores, tools, and reference materials.

A migration audit is required to accurately inventory your existing scattered documentation before mapping, ensuring the generated easysdd structure correctly integrates your current architecture and design files without data loss.