Step 5: Your First Workflow

Time to see the system in action. You’ll run a simple workflow end-to-end so you can see how everything connects.

What you’ll need: Steps 1-4 complete (Claude Code installed, vault set up, profile created, at least basic connections).

Time: About 20 minutes.

What We’ll Do

You’ll create and run a simple “daily planning” workflow. This teaches you the pattern that all workflows follow:

  You trigger it ──▶ System gathers info ──▶ System thinks ──▶ You get a result

5.1 Start a Claude Session

Open your terminal:

claude

What you should see: Claude starts up and shows a prompt where you can type.

5.2 Load Your Context

If you created a context-loading command in Step 3, use it. Otherwise, tell Claude where to find your information:

Read my personal profile from ~/Vault/0_InnerContext/Self_Context/ and my vault index from ~/Vault/0_InnerContext/AGENT_GUIDE.md. Then confirm what you know about me.

What you should see: Claude reads your files and summarizes what it knows about you — your name, preferences, goals, and constraints.

This is the “magic moment.” When Claude summarizes your profile back to you, you’ll see the difference between a generic AI and YOUR AI. If something is wrong or missing, tell Claude to update the relevant file.

5.3 Run Your First Workflow

Now ask Claude to help you plan your day:

Help me plan my day. Check my calendar if you can, look at my goals, and give me a prioritized plan that respects my energy patterns and constraints.

What you should see: Claude creates a personalized daily plan that:

• Reflects your actual schedule (if calendar is connected)
• Respects your constraints (from your profile)
• Aligns with your goals (from your profile)
• Matches your communication style (from your profile)

5.4 Save It as a Reusable Command

If you liked the result, you can save this as a command you can run anytime. Ask Claude:

Save this daily planning workflow as a reusable command called /today that I can run every morning. Put it in ~/.claude/commands/today.md

What you should see: Claude creates a command file. Next time, you can just type /today instead of explaining what you want.

5.5 Try Another Workflow

Here are a few more things to try:

Review your week:

Review what I accomplished this week and suggest priorities for next week.

Challenge your thinking:

I'm thinking about [a decision you're facing]. Play devil's advocate and challenge my reasoning.

Draft a message:

Draft an email to [person] about [topic]. Match my communication style.

Each of these can be saved as a reusable command once you find a version you like.

What You Just Learned

  ┌─────────────────────┐
  │   Load context      │
  │   (who you are)     │
  └─────────────────────┘
             │
             ▼
  ┌─────────────────────┐
  │   Give a task       │
  │   (what you need)   │
  └─────────────────────┘
             │
             ▼
  ┌─────────────────────┐
  │   System executes   │
  │   (profile + tools) │
  └─────────────────────┘
             │
             ▼
  ┌─────────────────────┐
  │   Review the result │
  │   (approve/adjust)  │
  └─────────────────────┘
             │
             ▼
  ┌─────────────────────┐
  │   Save as command   │
  │   (optional, reuse) │
  └─────────────────────┘

This is the pattern behind every workflow:

1. Context — The system knows who you are and what you have
2. Task — You tell it what you need (or a schedule triggers it automatically)
3. Execution — The system uses your profile, connections, and tools to do the work
4. Review — You approve, adjust, or reject the result
5. Reuse — Save good workflows as commands for one-click access

Checkpoint

You’ve successfully:

• Started Claude Code and loaded your context
• Run a personalized daily planning workflow
• Seen the system use your profile to tailor its output
• (Optional) Saved a workflow as a reusable command

All good? Move on to Verify It Works for a final system check.