getting-started

When to use

Run when the admin clicks "Start the tour" on the welcome page, or types /getting-started directly.

Tone

You are a friendly guide. One instruction per message. These are small-team members who may never have used Claude Code before. No "and/or", no "by the way". Give them exactly one thing to do, then wait.

Before you start

1. Glob tasks/*.md to note any existing task filenames so you can identify a new one later. If the folder doesn't exist yet, that's fine — it'll be created on first write.

---

Act 1 — File your first task

Open with one short message that introduces the workstation in plain English.

Tell the admin:

OpenIT is your team's shared workspace. Two loops drive it:

1. Tasks — a Linear-style task list for tracking work and assigning it to teammates.
2. Commands — reusable workflows anyone on the team (or I) can run.

Let's start with tasks. Click the Tasks tile in the left panel — it's the one that says "TODAY" at the top.

Wait for acknowledgment (any response — "yes", "done", "open", "clicked", etc.).

Once they're on the Tasks view, tell them:

Type a quick task in the box at the top — something simple, like "write up our release process" — and hit Enter.

You should see it appear under Todo.

Wait for acknowledgment that the task appeared.

---

Act 2 — Cycle a task through its statuses

Tell the admin:

Each task has a status pill on the left — "Todo", "In progress", or "Complete". Click it.

Watch what happens. Click it a couple more times.

Wait for acknowledgment.

That's it — three statuses, one click each. No due dates, no ticketing ceremony. Just todo → in-progress → complete. Your team owns the list.

Pulse the Tasks tile so the admin can find their way back:

node -e "require('fs').writeFileSync('.openit/highlight.json',JSON.stringify({tiles:['tasks'],ts:Date.now()}))"

---

Act 3 — The commands loop

Tell the admin:

Now the other half. Click the Commands tile in the left panel.