Build a PARA Project Command Center

Turn Startup Simulator plans into an actionable PARA workspace in Obsidian.

Introduction

30 Second Summary

Your product plan can feel clear when you write it. A week later, the next useful action can be buried across tabs and files.

In this project, you will turn your approved Startup Simulator plans into a focused project workspace in Obsidian. The PARA method keeps every decision connected to the next action.

What You'll Build

Picture opening one Startup Simulator dashboard and immediately knowing what to build next without searching through separate planning files.

By the end of this project, you'll have:

A working Obsidian vault that opens with the full PARA structure plus repository templates ready for daily use.
A project command center that puts the next build decision one click from its supporting evidence.
A repeatable Inbox-to-Project workflow that keeps each new question tied to the active outcome.
Secret Mission: Extract reusable planning lessons into Startup Product Planning Playbook.md for future startup ideas.

What do I need before starting?

Install Obsidian for your operating system from the official download page.
Install Git for your operating system from the official installation page.
Complete Startup Project Part 1.
Complete Startup Project Part 2.

Before We Start

Before the hands-on work begins, this is your moment to define what the Startup Simulator project folder must help you deliver. That outcome keeps every later PARA choice tied to current use.

Set Up the Second Brain Vault

Your planning system needs one local place where active work stays easy to find. An Obsidian vault provides that workspace.

The 00-Foundation branch already contains the PARA folders and templates used in this project. You will clone it with Git instead of rebuilding the structure by hand.

In this step, get ready to:

Clone the Foundation branch into a local vault folder.
Open the cloned folder as an Obsidian vault.
Install and configure Templater for the repository templates.

Clone the Foundation branch

The Foundation branch gives you the complete vault structure in one download.

macOS

Press Cmd+Space to open Spotlight.
Type Terminal.
Press Enter to open Terminal.
Clone the Foundation branch into ~/second-brain by running the command below:

Windows

Press the Windows key to open system search.
Type Git Bash.
Press Enter to open Git Bash.
Clone the Foundation branch into ~/second-brain by running the command below:

Linux

Open your desktop's app launcher.
Search for Terminal.
Select Terminal to open it.
Clone the Foundation branch into ~/second-brain by running the command below:

git clone --branch=00-Foundation --single-branch https://github.com/donald-stolz/second-brain.git ~/second-brain

You should see Git download the repository into ~/second-brain.

Check the cloned folders by running this command:

ls ~/second-brain

You should see 00 Inbox, 01 Projects, 02 Areas, 03 Resources, 04 Archive, and Templates.

Need help with the clone?

Help me troubleshoot the clone.

Open the folder as an Obsidian vault

An Obsidian vault is a local folder that Obsidian treats as one connected workspace.

macOS

Press Cmd+Space to open Spotlight.
Type Obsidian.
Press Enter to open Obsidian.
Select Open folder as vault.
Select Open to open Finder.
Choose the second-brain folder inside your home folder.
Select Open to load the vault.

Windows

Press the Windows key to open system search.
Type Obsidian.
Press Enter to open Obsidian.
Select Open folder as vault.
Select Open to open File Explorer.
Choose the second-brain folder inside your user folder.
Select Open to load the vault.

Linux

Open your desktop's app launcher.
Search for Obsidian.
Select Obsidian to open it.
Select Open folder as vault.
Select Open to open your file manager.
Choose the second-brain folder inside your home folder.
Select Open to load the vault.

The Obsidian file explorer should show all five PARA folders and Templates. That visible structure confirms the correct folder is open.

Install and configure Templater

Templater reads the dynamic fields inside the repository's note templates.

Open Settings from the lower-left corner of Obsidian.
Select Community plugins.
Turn on community plugins if Obsidian prompts you.
Select Browse.
Search for Templater.
Select Install on the Templater listing.
Select Enable.

Templater is now active. Connect it to the templates stored in this vault.

Return to Settings.
Select Templater in the Community plugins section.
Set Template folder location to Templates.
Open the Command palette from Obsidian's left ribbon.
Search for Create new note from template.

You should see a Templater command named Create new note from template. The file explorer should still show the five PARA folders and Templates.

Need help with Templater?

Help me set up Templater.

Your setup is ready: the Foundation vault is open with its PARA folders and Templater connected to its templates.

Your Second Brain foundation is ready. Next, you'll create a dedicated Startup Simulator folder and build its main project note from the repository template.

Create the Active Startup Simulator Project

Set Up the Startup Simulator Project Folder

Your Obsidian vault is ready with its PARA structure and templates. The next step is to give the Startup Simulator one clear home.

A dedicated folder keeps the main project note beside every document that supports its current outcome. You will create that folder first, then build the main note from the Project Note template.

In this step, get ready to:

Create a dedicated Startup Simulator project folder.
Create the main project note from the Project Note template.
Use frontmatter to classify the project and track its active state.

Create the project folder

The folder becomes the boundary for the active Startup Simulator work. Anything that directly supports this outcome belongs inside it.

Select 01 Projects in Obsidian's left file explorer.
Select the new-folder control at the top of the file explorer.
Name the folder Startup Simulator.

You should see Startup Simulator nested beneath 01 Projects.

Create the main note from the template

Templater turns the repository's Project Note template into a consistent starting point. The template supplies project fields, an Outcome section, and a Next Actions section.

Right-click the Startup Simulator folder in Obsidian's file explorer.
Select Create new note from template.
Select Project Note from the template list.
Type Startup Simulator into the selected filename.
Press Enter to save the note as Startup Simulator.md.

You should see type: project and status: inbox near the top of the note. The date fields should contain generated dates instead of Templater commands.

Why use the Project Note template?

The template gives every PARA Project the same basic shape. That consistency makes active work easier to scan and review.

Activate the project with frontmatter

Frontmatter is structured information stored at the top of a Markdown note. Obsidian uses these fields to display properties that help you classify, filter, and find the note.

Change status from inbox to active.
Replace the summary placeholder with Turn the approved Startup Simulator plan into the next working product increment..
Add startup-simulator to tags.
Add product-development to tags.
Keep the generated created date.
Keep the generated modified date.

What does the frontmatter record?

The type field identifies the note as a project.
The status field shows that the project is current work.
The summary field states the active purpose in one sentence.
The tags field keeps the note discoverable by topic.

Help me write a focused project summary.

Replace the template body beneath the frontmatter by pasting this content:

## Outcome

Ship the next planned Startup Simulator increment with its approved requirements easy to retrieve.

## Next Actions

- [ ] Review `project-requirements.md` before choosing the next build task.

How does this create movement?

The Outcome defines the finish line for the next product increment.
The first action keeps the approved requirements in view.

Before you review the note, which section do you expect to show the finish line?

Save 01 Projects/Startup Simulator/Startup Simulator.md.
Review the rendered properties at the top of the note.
Review the Outcome section.
Review the unchecked Next Action.

You should see an active project with generated dates, two topic tags, one Outcome, and one unchecked Next Action. Your main project note now has both a classification and a clear direction.

Your Startup Simulator now has a dedicated folder and an active main note. Next, you'll bring its existing requirements document into the same project workspace.

Build the Startup Simulator Project Folder

Import the Startup Project Requirements

Your active project now has a home inside Obsidian. Its main note defines the outcome and the next actions.

The approved requirements already exist in the Startup Simulator project. This step copies that document into the active PARA Project so its decisions stay beside the work they support.

In this step, get ready to:

Locate the existing Startup Simulator requirements document.
Copy the document into the active project folder.
Confirm that the project workspace contains both notes.

Locate the existing requirements document

The existing file contains decisions that the next product increment depends on. Importing it preserves that work instead of rewriting it from memory.

macOS

Press Cmd+Space to open Spotlight.
Type Finder.
Press Enter to open Finder.
Open your existing Startup Simulator project folder.
Locate project-requirements.md.

Windows

Press the Windows key to open system search.
Type File Explorer.
Press Enter to open File Explorer.
Open your existing Startup Simulator project folder.
Locate project-requirements.md.

Linux

Open your desktop's app launcher.
Open your file manager.
Open your existing Startup Simulator project folder.
Locate project-requirements.md.

You should see project-requirements.md inside the existing Startup Simulator project. This is the source document you will copy into the vault.

Help me check why this document belongs with the active project.

Copy the document into the PARA project

Copying keeps the original project file in place. The vault receives a working copy that you can connect to the project dashboard.

macOS

Select project-requirements.md in the existing Startup Simulator project folder.
Press Cmd+C to copy the file.
Open your home folder in Finder.
Open second-brain/01 Projects/Startup Simulator.
Press Cmd+V to paste the file.

Windows

Select project-requirements.md in the existing Startup Simulator project folder.
Press Ctrl+C to copy the file.
Open your user folder in File Explorer.
Open second-brain/01 Projects/Startup Simulator.
Press Ctrl+V to paste the file.

Linux

Select project-requirements.md in the existing Startup Simulator project folder.
Press Ctrl+C to copy the file.
Open your home folder in your file manager.
Open second-brain/01 Projects/Startup Simulator.
Press Ctrl+V to paste the file.

You should see project-requirements.md beside Startup Simulator.md.

Why copy the document?

The source project remains unchanged because you copied the document. The vault copy now serves the active outcome and can participate in Obsidian links.

Confirm the imported project context

A project folder is useful when every file inside it supports the same finish line. The final check confirms that the dashboard and requirements now form one working set.

Before you check the folder, which two files do you expect to see together?

Return to Obsidian.
Expand 01 Projects/Startup Simulator in the left file explorer.
Open project-requirements.md.
Confirm that the existing requirements content is visible.

You should see Startup Simulator.md and project-requirements.md inside the folder. The imported requirements should retain their original content.

Your active Project now contains its dashboard and the requirements that guide the next increment. Next, you'll connect that material through a project control center.

Create a Project Control Center

Your main project note now sits beside project-requirements.md in Obsidian.

Co-location keeps the project material together. A control center goes further by surfacing the current decisions and linking each action to its evidence.

You will turn Startup Simulator.md into that control center with a decision snapshot, project-material links, and a traceable next action.

In this step, get ready to:

Summarize the decisions that shape the next increment.
Connect the dashboard to the imported requirements.
Make the first Next Action traceable to its supporting evidence.

Add a decision snapshot

A decision snapshot keeps the assumptions that affect the next task visible. Each line answers one question that would otherwise require reopening the imported requirements.

Open project-requirements.md from the Startup Simulator folder.
Identify the target user.
Identify the smallest promised outcome.
Identify the current build stage supported by the approved requirements.
Return to Startup Simulator.md.
Place your cursor after the Outcome sentence.
Insert the Decision Snapshot before ## Next Actions by pasting:

## Decision Snapshot

- Target user: Replace with the target user from `project-requirements.md`.
- Smallest promised outcome: Replace with the minimum user-visible result.
- Current build stage: Replace with the next product stage supported by `project-requirements.md`.
- Most important constraint: Replace with the constraint that most affects the next task.

What does the snapshot show?

The Target user line keeps the next increment focused on the person named in the requirements.
The Smallest promised outcome line defines the minimum result that person can observe.
The Current build stage line shows where implementation work stands.
The Most important constraint line keeps the strongest limit visible.

Replace the Target user prompt with one concise statement from project-requirements.md.
Replace the Smallest promised outcome prompt with one observable result from project-requirements.md.
Replace the Current build stage prompt with the next product stage supported by project-requirements.md.
Replace the Most important constraint prompt with the strongest limit on the next task.
Save Startup Simulator.md.
Review the Decision Snapshot.

You should see four populated bullets between Outcome and Next Actions. Together, they provide the context needed to judge the next task.

Help me distill the imported requirements into a decision snapshot.

Connect the imported requirements

Wikilinks connect notes by filename. The dashboard can open the imported requirements without sending you back through the file tree.

Place your cursor after the final checklist item under ## Next Actions.
Add the Project Materials section by pasting:

## Project Materials

- [[project-requirements]]

How do these links work?

Each wikilink matches the filename without the .md extension. Obsidian resolves the link to the corresponding note inside the vault.

Before you activate the link, which imported note do you expect it to open?

Save Startup Simulator.md.
Activate [[project-requirements]] from the Project Materials section.

The link should open project-requirements.md. This confirms that the dashboard can reach the approved requirements directly.

Make the next action traceable

A traceable action names the work to start and the evidence that defines success. The links keep both parts available from the action itself.

Return to Startup Simulator.md.
Find the checklist under ## Next Actions.
Replace that section with this traceable version:

## Next Actions

- [ ] Start the next build task named in the Decision Snapshot and validate it against [[project-requirements]].
- [ ] Resolve the blocking item in [[Open Questions]].

What makes the action traceable?

The first action links the selected build task to the requirement it must satisfy. The second action keeps a blocking question visible as part of the active project.

Before you test the first action, which document do you expect its link to open?

Save Startup Simulator.md.
Activate [[project-requirements]] in the first Next Action.

You should open project-requirements.md. The first Next Action now carries both the work and the evidence that defines success.

You've connected the project dashboard to its imported evidence. Next, you'll process a new capture into this active Project and keep the control center current.

Process Inbox Items Into the Project

Your Obsidian dashboard now connects each next action to the planning material behind it. The active project still needs a reliable way to absorb new questions as they appear.

This step completes the recurring PARA loop for work in progress. You will capture a blocking question before classifying it by current use.

In this step, get ready to:

Capture a blocking build question in 00 Inbox.
Classify the question as support for the active Startup Simulator project.
Add milestone checks plus a repeatable review routine to the dashboard.

Capture a blocking question

The Inbox gives new information a temporary landing place before you decide where it belongs. Capturing first keeps classification from interrupting the thought itself.

Return to the open ~/second-brain vault in Obsidian.
Right-click 00 Inbox in the file explorer.
Select Create new note from template.
Select Inbox Note from the template list.
Rename the generated note to Startup Simulator - First Build Question.md.
Replace the template prompt with one question that blocks the first implementation task.
Save Startup Simulator - First Build Question.md.

You will see normal frontmatter instead of raw Templater syntax. Your first Inbox capture now holds a concrete question from the active build.

Template syntax still visible?

Confirm that you right-clicked 00 Inbox and selected Create new note from template. Choose Inbox Note from the template list instead of opening the template file itself.

Check that Template folder location still points to Templates in the Templater settings.

Help me render the Inbox Note template.

Triage the capture by current use

This question directly blocks the active Startup Simulator outcome. It belongs beside the project dashboard as support material that can change the next action.

Why does this stay with the Project?

A Project contains information that supports a defined outcome with a finish line. This question shapes the next Startup Simulator increment.

A Resource supports future use across multiple efforts. The question remains specific to the current build.

Drag Startup Simulator - First Build Question.md from 00 Inbox into 01 Projects/Startup Simulator/.
Rename the moved note to Open Questions.md.

You will see Open Questions.md beside the dashboard and imported requirements. The original capture no longer appears in 00 Inbox.

Replace the frontmatter in Open Questions.md with this project-support frontmatter:

---
type: project-support
status: active
project: "[[Startup Simulator]]"
created: "your-creation-date-here"
modified: "your-modified-date-here"
summary: Questions that currently block or shape the next Startup Simulator action.
tags:
  - startup-simulator
  - open-questions
---

What does this frontmatter do?

The project-support type identifies the note as material serving the active project.
The active status keeps the question connected to ongoing work.
The [[Startup Simulator]] value creates a route back to the dashboard.

Save Open Questions.md.
Check the rendered properties at the top of the note.

You will see the note classified as project-support with a status of active.

Frontmatter not rendering?

Check that both --- lines remain in place. Missing delimiters cause Obsidian to display the properties as ordinary text.

Help me fix the Open Questions frontmatter.

Replace the note body below the frontmatter with this structure:

## Current Questions

- [ ] Replace with the question that must be answered before the first implementation task begins.

## Resolution Notes

- Record the answer, evidence, and resulting project decision here.

## Project Link

- [[Startup Simulator]]

How does this note stay actionable?

Current Questions turns each blocker into a checkable item.
Resolution Notes preserves the evidence behind the eventual decision.
Project Link returns you to the dashboard without browsing the file tree.

Replace the Current Questions prompt with the blocking question you captured.
Save Open Questions.md.
Activate [[Startup Simulator]] under Project Link.

You will return directly to the active dashboard. The question now has a permanent place beside the decisions it can affect.

Project link opens the wrong note?

Confirm that the destination note is named exactly Startup Simulator.md. Obsidian resolves the wikilink from that note title.

Help me repair the Startup Simulator wikilink.

The full-code reference keeps learner-specific text as scaffold prompts. Your captured question takes the place of the Current Questions prompt.

✔️ Awesome, I've got everything!

Great. Double check that Open Questions.md is saved inside 01 Projects/Startup Simulator/.

ⓧ I'd like to double check the full code

---
type: project-support
status: active
project: "[[Startup Simulator]]"
created: "your-creation-date-here"
modified: "your-modified-date-here"
summary: Questions that currently block or shape the next Startup Simulator action.
tags:
  - startup-simulator
  - open-questions
---

## Current Questions

- [ ] Replace with the question that must be answered before the first implementation task begins.

## Resolution Notes

- Record the answer, evidence, and resulting project decision here.

## Project Link

- [[Startup Simulator]]

Compare the headings plus frontmatter with your note. Keep your own blocking question under Current Questions.

Switch back to Startup Simulator.md.
Add [[Open Questions]] below [[project-requirements]] in Project Materials.
Save Startup Simulator.md.
Activate [[Open Questions]] from the dashboard.

You will open the intended support note without using the file explorer. The dashboard now reaches every piece of current project evidence.

Keep active work current

A processed Inbox item can change the finish line or expose stale work. Milestone checks plus a short review routine keep the dashboard aligned with the next product increment.

Return to Startup Simulator.md.
Add this section directly below Project Materials:

## Current Milestone

- [ ] The selected product behavior works as described in [[project-requirements]].
- [ ] The next build task is named in the Decision Snapshot.
- [ ] New decisions and unresolved questions are recorded in this project folder.

What does this milestone measure?

Each check describes visible evidence for the next increment. Product behavior connects to the requirements.

The Decision Snapshot names the next build task. New decisions stay inside the active project folder.

Save Startup Simulator.md.
Check the dashboard below Project Materials.

You will see a Current Milestone heading with three checkboxes. Each checkbox points to evidence inside the active project.

Add this review routine directly below Current Milestone:

## Review Checklist

- [ ] Process every Startup Simulator item in `00 Inbox`.
- [ ] Review and update [[Open Questions]].
- [ ] Complete, remove, or rewrite stale Next Actions.
- [ ] Choose the next build task from the Decision Snapshot.

How does the review loop work?

Processing the Inbox prevents new captures from becoming a second backlog.
Reviewing open questions exposes blockers before implementation begins.
Rewriting stale actions keeps the dashboard focused on work that can move now.
Choosing the next implementation task ends each review with a concrete starting point.

Save Startup Simulator.md.
Check the bottom of the dashboard.

You will see a Review Checklist with four recurring actions. The project keeps its active status because the Startup Simulator remains in progress.

Review section in the wrong place?

Place Review Checklist after the final Current Milestone checkbox. Keep a blank line between the two sections so each heading renders separately.

Help me organize the dashboard sections.

✔️ Awesome, I've got everything!

Your dashboard now links both support notes. It also shows the current milestone plus the recurring review routine.

ⓧ I'd like to double check the full code

---
type: project
status: active
created: "your-creation-date-here"
modified: "your-modified-date-here"
summary: Turn the approved Startup Simulator plan into the next working product increment.
tags:
  - startup-simulator
  - product-development
---

## Outcome

Ship the next planned Startup Simulator increment with its requirements and open questions easy to retrieve.

## Decision Snapshot

- Target user: replace with the target user from the approved requirements.
- Smallest promised outcome: replace with the minimum user-visible result.
- Current build stage: replace with the next product stage supported by the approved requirements.
- Most important constraint: replace with the constraint that most affects the next task.

## Next Actions

- [ ] Start the next build task named in the Decision Snapshot and validate it against [[project-requirements]].
- [ ] Resolve the blocking item in [[Open Questions]].

## Project Materials

- [[project-requirements]]
- [[Open Questions]]

## Current Milestone

- [ ] The selected product behavior works as described in [[project-requirements]].
- [ ] The next build task is named in the Decision Snapshot.
- [ ] New decisions and unresolved questions are recorded in this project folder.

## Review Checklist

- [ ] Process every Startup Simulator item in `00 Inbox`.
- [ ] Review and update [[Open Questions]].
- [ ] Complete, remove, or rewrite stale Next Actions.
- [ ] Choose the next build task from the Decision Snapshot.

Compare every dashboard section with this reference. Keep your learner-specific dates plus decision details in place.

Before you check, which folder should now be clear? Which status should the dashboard and Open Questions note show?

Expand 00 Inbox in the file explorer.
Expand 01 Projects/Startup Simulator in the file explorer.
Open Startup Simulator.md.
Check its status property.
Open Open Questions.md.
Check its status property.
Return to Startup Simulator.md.
Activate [[Open Questions]] under Project Materials.

You will see a clear 00 Inbox plus three files inside the Startup Simulator project folder. Startup Simulator.md and Open Questions.md should show an active status, while the imported requirements retain their original content.

The dashboard displays Current Milestone plus Review Checklist. Activating [[Open Questions]] opens the intended support note.

Strong finish. Your vault can now turn a fresh capture into an actionable part of the active Startup Simulator project.

Secret mission

Extract a Reusable Startup Planning Playbook

Your Startup Simulator project contains planning lessons that could help with a completely different product. In this mission, you will extract those lessons into a reusable playbook without carrying over project-specific requirements or tasks.

Clean Up Your Resources

Your Obsidian vault runs entirely on your computer with no ongoing costs. Decide whether to keep the vault available, pause your work, or delete the local files entirely.

Resources you used:

A local Git clone at ~/second-brain that serves as your Obsidian vault.
Local vault configuration containing the enabled Templater plugin.
An active project folder at 01 Projects/Startup Simulator/ containing the dashboard plus two support notes.
A reusable planning Resource at 03 Resources/Startup Product Planning Playbook.md.

Keep everything running

No action needed. Choose this if you want to keep using the Startup Simulator project dashboard as your command center.

Keep using ~/second-brain as your active Obsidian vault.
Continue processing new captures through 00 Inbox.
Use the Review Checklist in Startup Simulator.md to keep the next actions current.
Store a deliberate backup outside the repository because personal notes are ignored by default.

Your Notes Need a Backup

The repository shares the vault structure without automatically tracking your personal notes. Cloning the repository does not create a backup of the notes you added.

Pause - I'll come back to this later

Pause the workspace when you want to stop working without removing your notes. No background service or billable resource remains active after Obsidian closes.

Close Obsidian.
Leave the ~/second-brain folder on your computer.
Open ~/second-brain as your existing Obsidian vault when you resume.

Delete - I don't want to use this again

Deleting the local vault is permanent, so copy any notes you want to keep first. Your GitHub fork remains unchanged because this cleanup only removes ~/second-brain from your computer.

macOS

Copy any notes worth keeping to a folder outside ~/second-brain.
Close Obsidian.
Press Cmd+Space to open Spotlight.
Type Terminal.
Press Enter to open Terminal.
Delete the local vault by running this command:

rm -rf ~/second-brain

Open your home folder in Finder.
Confirm that second-brain no longer appears.

Folder Still There?

Check that Obsidian is closed before you retry the deletion.

Help me remove the local vault safely.

Windows

Copy any notes worth keeping to a folder outside ~/second-brain.
Close Obsidian.
Press the Windows key to open system search.
Type Git Bash.
Press Enter to open Git Bash.
Delete the local vault by running this command:

rm -rf ~/second-brain

Open your user folder in File Explorer.
Confirm that second-brain no longer appears.

Folder Still There?

Make sure you ran the command in Git Bash. Check that Obsidian is closed before you retry the deletion.

Help me remove the local vault safely.

Linux

Copy any notes worth keeping to a folder outside ~/second-brain.
Close Obsidian.
Open your desktop's app launcher.
Search for Terminal.
Select Terminal to open it.
Delete the local vault by running this command:

rm -rf ~/second-brain

Open your home folder in your file manager.
Confirm that second-brain no longer appears.

Folder Still There?

Check that Obsidian is closed before you retry the deletion.

Help me remove the local vault safely.

Nice Work!

You did it! Your Obsidian vault is now a PARA command center for moving the Startup Simulator toward its next product increment.

What you learned:

Built a working vault from the 00-Foundation branch. Configured Templater to turn repository templates into usable notes.
Created a self-contained Startup Simulator project folder under 01 Projects. Kept approved requirements plus open questions beside the active dashboard.
Processed a capture from Inbox to Project according to its current use. Added observable milestone checks. Built a Review Checklist that keeps the next build task current.
Secret Mission: Extracted a reusable Startup Product Planning Playbook that can guide future startup projects without carrying over Startup Simulator-only material.

Ready to quiz yourself?