herreraspaintingba-hubherreraspaintingba-hub/second-brain-starter-kit/skills/project-door/SKILL.md

project-door

Skill0 starsChanged 42 days agoMITView on GitHub

Keeps one "Door" note per project: the project's current state in one screen (what is true today, the numbers that matter, the next steps), read FIRST whenever work on that project starts, and rewritten at every session close. Use it when the user starts or resumes work on a project ("let's work on X", "where are we with X?", "status of X", "open the door of X", "vamos con X", "¿en qué quedamos con X?", "abre la Puerta de X"), when they start a new project ("new project", "proyecto nuevo"), and when close-session updates the project. Bilingual EN+ES.

In this repository8 other files it gives its agents.
- brain-healthSkill
- brain-searchSkill
- close-sessionSkill
- obsidian-power-userSkill
- project-advisorSkill
- save-to-obsidianSkill
- second-brain-initSkill
- session-checkpointSkill

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Read the front page:
line 62
Distinctive:
If it says the Door is old, say so and check the numbers before deciding anything.
line 69
Distinctive:
Read the checkpoint only if the Door points to it or the session was interrupted.
line 70
Distinctive:
When the user starts something that will take more than one session:
line 83
Very specific:
Add the project slug to the project list in .brain/vocabulary.json (tell the user).
line 92
Distinctive:
Never put a number in section 2 you did not verify this session.
line 113

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Project Door: the front door of every project

Why it exists

Without a Door, resuming a project means crawling through old session logs and guessing which one is current. That is slow, it fills the AI's memory with history, and it still misses things. The Door fixes this: one note, one screen, always current, and the first thing read when work on that project begins.

Note	Answers	Changes
Door (`09 MOCs/Door, <Project>.md`)	Where does this project stand today?	Rewritten at every close
Checkpoint (`session-checkpoint`)	What were we doing an hour ago?	During a long session
Session log (`save-to-obsidian`)	What happened in that session?	Never, once written
MOC	Where is everything about this theme?	When notes are added

The shape of a Door

Six numbered sections. The numbers matter: the tools read sections by number, so the headings can be in any language.

#	English	Español	What goes there
1	Current state	Estado vigente	3 to 6 lines: what is true today
2	Numbers that matter	Números que mandan	The few figures that drive decisions, each with its source and date
3	Next steps	Pendientes	Checkboxes: the next concrete steps and who owns each
4	How it runs	Cómo se opera	How to use, operate or ship it. Read only when needed
5	Where everything else lives	Dónde vive lo demás	Links to the MOC, checkpoint, decisions, files
6	History	Historial	One line per change, newest first

Frontmatter: type: door, project: <slug>, status: active, and verified: YYYY-MM-DD, the day someone last checked that sections 1 to 3 are true. A Door older than 7 days is treated as possibly stale.

Sections 1, 2 and 3 are the front page. That is all that gets read when a session starts. Sections 4 to 6 are read only when the task needs them. The note is never split; in Obsidian it stays one screen.

Opening a project (start of a session)

Identify the project from what the user said. If it is unclear, ask; do not guess a name (a guessed name creates a second Door that looks real).
Read the front page:
```
python3 "{{VAULT_PATH}}/.brain/tools/door.py" "<Project>"
```
Without Python, open 09 MOCs/Door, <Project>.md and read sections 1 to 3.
If it says the Door is old, say so and check the numbers before deciding anything.
Read the checkpoint only if the Door points to it or the session was interrupted.
Tell the user in one line where things stand and what the next step is.

python3 "$T/door.py"                    # list all Doors with their verified date
python3 "$T/door.py" "Garden" 4         # one section
python3 "$T/door.py" "Garden" --all     # the whole note

Creating a Door (new project)

When the user starts something that will take more than one session:

python3 "{{VAULT_PATH}}/.brain/tools/door.py" --new "Garden" --project garden          # English headings
python3 "{{VAULT_PATH}}/.brain/tools/door.py" --new "Huerto" --project huerto --lang es # Spanish headings

Then:

Add the project slug to the project list in .brain/vocabulary.json (tell the user).
Fill sections 1 to 3 with what you know now; leave honest placeholders, not invented numbers.
Link the Door from the theme's MOC in 09 MOCs/ (create a MOC if the project is big enough to need one), so it is not an orphan.
Validate: python3 "$T/check_frontmatter.py" "09 MOCs/Door, Garden.md".

Without Python, create the note by hand with the six sections and the same frontmatter.

Updating a Door (end of a session)

This is step 2 of close-session. Rewrite, do not append, for sections 1 to 3:

Section 1: what is true now, replacing what is no longer true.
Section 2: the numbers as they are now, each with where it came from.
Section 3: check off what got done; add what is new; remove what was dropped.
Section 6: add one line at the top: - YYYY-MM-DD HH:MM: what changed.
Set verified: to today, only for what you actually checked.

Never put a number in section 2 you did not verify this session. If you could not verify it, keep the old one and say "not verified since <date>".

Changelog

2.0.0 (2026-10-02): New skill. Six-section Door, front page, door.py.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free