onboard-project

Onboard Project

Set up a new project in the PM workspace through a structured onboarding flow.

Usage

/onboard-project {project-name}

Workflow

Step 1: Scaffold

Create the project folder structure under projects/{project-name}/:

{project-name}/
  raw/
  docs/
    INDEX.md
  decisions/
  comms/

If raw/ already contains files, note them for processing in Step 2.

Step 2: Process raw inputs

For each file in raw/:

1. Read the file (PDF, text, export, etc.)
2. Generate a structured markdown summary following the process-document skill
3. Save to docs/ with a matching name
4. Update docs/INDEX.md

If raw/ is empty, skip to Step 3.

Step 3: Interview

Conduct a structured interview to populate the project brief. Use processed docs as starting context so you don't ask about things you already know.

Interview areas (adapt based on what you already learned from docs):

1. Project basics: What is this project? Why does it exist?
2. Goals and success: What does good look like? How will we know?
3. Stakeholders: Key people, roles, what they care about, political dynamics.
4. Constraints: Time, budget, tech, organizational limits.
5. Risks: What worries you most?
6. Your role: What are you responsible for? What authority do you have?
7. Ways of working: How will you operate day-to-day on this project? What's your rhythm? What tools? How do you want to capture and track things?
8. Agent persona: What kind of PM partner do you need on this project? Think about: archetypes (senior TPM, product strategist, program manager, builder-operator), document standards (Amazon 6-pager precision vs. lean one-pagers), decision rigor (log everything vs. only key calls), communication style (formal/precise vs. casual/fast). If the PM isn't sure, suggest an archetype based on what you've learned about the project so far.

Ask 2-3 questions at a time. Don't overwhelm. Let the conversation flow naturally. Use processed docs to pre-fill what you can and validate with the PM rather than asking from scratch.