| name | start |
| description | First-time onboarding — asks where you are, then guides you to the right workflow. No assumptions. |
| argument-hint | [no arguments] |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, AskUserQuestion |
Guided Onboarding
Workflow
1. Detect Project State (Silent)
Before asking anything, silently gather context:
- Project configured? Read
.claude/docs/technical-preferences.md. If Building Type is [TO BE CONFIGURED], not set.
- Project brief exists? Check for
design/architectural/project-brief.md.
- Design docs exist? Count markdown files in
design/.
- Specifications exist? Check for files in
specs/.
- Production artifacts? Check for files in
production/phases/ or production/milestones/.
2. Ask Where the User Is
Welcome to Claude Code Construction Team!
Before I suggest anything, I'd like to understand where you're starting from.
A) No idea yet — I don't have a building concept. I want to explore options.
B) Vague idea — I have a rough building type or site in mind but nothing concrete.
C) Clear requirements — I know the building type, site, and basic program but haven't formalized documents.
D) Existing project — I already have design docs, drawings, or significant planning done.
Wait for response.
3. Route Based on Answer
If A: No idea → /brainstorm
If B: Vague idea → /brainstorm [hint]
If C: Clear requirements → /setup-project-type then /map-systems
If D: Existing project → /project-stage-detect
4. Confirm Before Proceeding
Present recommended path and ask which step to take first. Never auto-run.