onboard-project

Stand up a custom project workspace. Lighter than onboard-brand — projects are ad-hoc and don't need full briefs.

Pre-flight checks

1. project_slug is kebab-case.
2. Departments/Projects/{project_slug}/ does not exist.
3. For each brand_slug in brands: Brands/{brand_slug}/ exists (or fail and ask Adam to onboard the brand first).

Procedure

1. Scaffold from template

Copy Departments/Projects/_Template/ to Departments/Projects/{project_slug}/:

• _Project.md
• Agents/, Skills/, Notes/ subfolders

2. Fill _Project.md frontmatter

• name: {project_slug}
• status: active
• brands: {brands}
• owner: adam
• created: {today}
• target_completion: {target_completion} (or null)
• display_name, charter from inputs.

3. Create the wiki node

Write Wiki/Concepts/project-{project_slug}.md using the wiki-node template:

• node_kind: concept
• tags: [project]
• Body: 2–3 sentences from charter, link back to <a class="wikilink wikilink-broken" href="#">Departments/Projects/{project_slug}/_Project</a>.

4. Cross-link affected brands

For each brand_slug in brands:

• Append a line under "Active campaigns / programs" in Brands/{brand_slug}/BrandContext.md: - <a class="wikilink wikilink-broken" href="#">Departments/Projects/{project_slug}/_Project</a> — {display_name}

5. Append Log entry

Via log-operation:

• agent: ea-orchestrator
• skill: onboard-project
• input: {project_slug}, brands={brands}
• output: Departments/Projects/{project_slug}/
• artifacts: <a class="wikilink wikilink-broken" href="#">Wiki/Concepts/project-{project_slug}</a>

Failure modes

• Project slug collision: abort.
• Referenced brand missing: list missing brands, suggest running onboard-brand first.

Hard rules

• Don't create project-specific agents or skills automatically — let those emerge as the project clarifies. The empty Agents/ and Skills/ folders are intentional placeholders.
• Wiki node is mandatory — projects need to be discoverable via graph view.