wdd-init-project

name	wdd-init-project
description	Initialize a repository for text-only Wave-Driven Development by creating .wdd artifacts, templates, epic storage, and constitution scaffolding without relying on a CLI or scripts.

WDD Init Project

Use this when a project does not yet have .wdd/ artifacts or when the user asks to adopt WDD.

User Input

Use any user-provided project name, boundaries, preferred agents, storage mode, model preferences, or branch policy. If no guidance is provided, infer only safe defaults from repository docs and code.

Preconditions

• Work from the repository root.
• Read repo instructions first.
• If .wdd/constitution.md already exists, do not overwrite it.
• If .wdd/ exists, inspect it and update only missing scaffolding.
• Keep schema-v1 initialization portable: it must not require a WDD CLI, script, package manager, or validator. When initializing a schema-v2 managed workflow, wddctl is the optional controller integration and its installer must still be an explicit user choice.
• Use this skill's local templates/ directory as the source for starter artifacts. Do not rely on a repository-root templates/ directory.

Workflow

1. Inspect project context:

   • Read AGENTS.md if present.
   • Read README.md if present.
   • Identify project type, package manager, verification commands, target branch, and ownership boundaries from repo evidence.

2. Create directories if missing:

       .wdd/
         work/
         epics/
         templates/
   

3. Create .wdd/constitution.md if missing:

   • Use templates/constitution.md from this skill folder.
   • Fill only values that can be inferred safely.
   • Leave the initial constitution as draft; record explicit questions and require user ratification before any schema-v2 execution.

4. Copy or create local templates under .wdd/templates/:

   • constitution.md
   • epic.md
     • ticket.md
     • task.md
     • task-compact.md
     • wave-plan.md
   • controller-state.md
   • validation-checklist.md
   • shared-context-index.md
     • shared-context-resource.md
     • orchestration.json
     • work-brief.md
     • work-task.md
     • work-state.json
     • epic-validation.md
     • final-pr.md
   • Prefer exact copies from this skill folder's templates/ directory, then let later phase skills specialize generated artifacts for the project.

5. Create .wdd/README.md:

   • Explain that .wdd/ is the durable source of truth.
   • List phase order: constitution, micro-wave or epic, planning, execution, reconciliation, validation when applicable, and final handoff.
   • State that external trackers are adapters.
   • State that schema-v1 is text-only and does not require scripts, while a schema-v2 scope may use the optional wddctl controller.

6. Report:

   • Files created.
   • Files preserved.
   • Constitution questions that still need user input.
   • Recommended next phase.

Done When

• .wdd/ exists.
• .wdd/work/ exists.
• .wdd/epics/ exists.
• .wdd/constitution.md exists and was not overwritten.
• .wdd/templates/ contains the text templates.
• The next phase is wdd-constitution if setup choices remain, otherwise wdd-start-epic.