sdc-init

name	sdc-init
description	Use when a project needs an SDC workspace, project cognition, or standards import.

Codex/Hermes workflow skill generated from commands/init.md. Treat the user's current request as $ARGUMENTS. In Codex/Hermes, route to the matching SDC skill/workflow instead of expecting /sdc:* slash-command support.

SDC Init

Initialize or repair the standard .sdc/ workspace in the current project. Treat "$ARGUMENTS" as additional project context.

Do not overwrite user-authored .sdc/ artifacts. If old SDC-generated managed templates are clearly stale, upgrade them to the current schema only with a .bak-* backup and report the repair.

Run the SDC init workflow:

• Create or repair .sdc/ idempotently.
• Preserve existing user/project memory.
• Create or repair constitution.md, project.md, project-cognition.md, common-ground.md, expert-routing.md, knowledge/, memory/, standards/, templates/, changes/, specs/, decisions/, reviews/, and reports/.
• Classify the project as Greenfield, Brownfield/Legacy, or Unknown using repository evidence.
• Seed common-ground.md with ESTABLISHED / WORKING / OPEN sections; do not mark generated starter content as ESTABLISHED.
• Seed expert-routing.md with candidate expert profiles; do not expose those profiles as additional public slash commands.
• Seed a product/technical knowledge index and a memory candidate area; do not treat generated starter content as confirmed facts.
• If the user provides an existing standards directory, import it as a private company/team standards pack under .sdc/standards/company/ and create a routing index. Do not publish those private rules with SDC.
• For Brownfield/Legacy, create or update reusable project-cognition.md; do not perform per-change impact analysis during init.