project-context

name	project-context
description	Compile a compact context brief for a project — read its _overview.md, scan recent daily notes for mentions, gather all tagged notes, and surface current status, open decisions, recent progress, and blockers. Use when [OWNER] says "project context [name]", "contexto del proyecto [nombre]", or at the start of any coding session on [YOUR_PROJECT] / Brisas / [ARCHIVED_PROJECT] / University.

Project Context

Before Eduardo starts a coding session on a project, he needs the project paged into his head: where things stood last time, what's open, what's blocked. This skill produces that brief from the vault so the coding session starts with full situational awareness — not a cold start.

Workflow

1. Identify the project. Match [OWNER]'s input against 03-projects/ folders. Common shortcuts:
   • "[your-project]" → 03-projects/[your-project]/
   • "[your-project-tag]" / "[client-site]" → 03-projects/[client-site]/
   • "[archived-project]" → 03-projects/[archived-project]/
   • "uni" / "university" / "ugb" → 03-projects/university/
   • "personal brand" / "marca" → 03-projects/personal-brand/
   • If no match, list available projects and ask.
2. Read the overview: 03-projects/<project>/_overview.md. This is the source of truth on status, strategy, and links.
3. Read project sub-files as relevant: services.md, pipeline.md, files in clients/, etc. Use Glob 03-projects/<project>/**/*.md.
4. Scan recent daily notes for project mentions:
   • Glob 02-daily/*.md, sort by mtime desc, take the 14 most recent
   • Grep them for the project name and any associated tags (e.g., #[your-project], #your-project-tag)
   • Read the matching sections
5. Scan session logs in 02-daily/logs/ (last 14 by mtime) for project mentions.
6. Dev Brain integration (optional — runs if ~/Documents/Dev Brain/ exists).
   • Check whether ~/Documents/Dev Brain/sessions/index.md exists. If it does not, skip this step silently.
   • If it exists, resolve the Dev Brain slug for the project:
     • [your-project] → [your-project]
     • brisas / [client-site] → [client-site]
     • recmp3-cli → recmp3-cli
     • Otherwise, use the project folder slug as-is.
   • Run: grep '| <slug> |' ~/Documents/Dev\ Brain/sessions/index.md | tail -5 and capture the result for the brief's "Recent coding sessions" section.
   • If ~/Documents/Dev Brain/wiki/<slug>.md exists, include a one-line pointer in the brief suggesting cat ~/Documents/Dev\ Brain/wiki/<slug>.md for the full wiki digest and graphify query "<topic>" (run from the repo dir) for ad-hoc code-structure questions.
   • This step is read-only and must never write to Dev Brain.
7. Search the wider vault for tagged notes: Grep for #<project> across 05-knowledge/, 00-inbox/.
8. Check 00-inbox/_ACTIVE-PROJECTS.md for the project's current status line.
9. Compile the context brief using the format below.
10. Optionally log the session start to 02-daily/logs/{{YYYY-MM-DD-HHMM}}-{{project}}-session-start.md if [OWNER] confirms (or if invoked at the start of an actual coding session — ask).
11. Output the brief inline. Make it scannable in under 60 seconds.

Context brief format

# 🎯 Project Context: {{Project Name}}

**Status:** {{from _overview.md or _ACTIVE-PROJECTS.md}}
**Last touched:** {{date of most recent mention in daily notes / logs}}

## Where it stands
{{2-4 sentences synthesizing current state from _overview.md and recent activity}}

## 📌 Open decisions
- {{decision waiting on Eduardo, with context}}
- ...

## ✅ Recent progress (last 14 days)
- {{YYYY-MM-DD}} — {{what happened}} ([[daily note]])
- ...

## 🚧 Blockers
- {{what's stopping forward progress}}
- ...

## 🔗 Key files
- [[_overview]] · [[services]] · [[pipeline]] · ...

## 🧠 Relevant knowledge from vault
- [[permanent note]] — why it's relevant
- ...

## 🧠 Recent coding sessions (Dev Brain)
- {{UTC timestamp | slug | summary_line}} (from sessions/index.md)
- ... (last 5 lines)
→ For code structure: graphify query "<topic>" in <repo-dir>
→ For full wiki: cat ~/Documents/Dev\ Brain/wiki/<slug>.md

## ▶ Suggested next action
{{one concrete next step Eduardo could take in this session}}

Rules

• Brief must be scannable in under 60 seconds. Hard cap: ~300 words. If the project has too much state to fit, point to the longest doc and stop.
• Bilingual: [YOUR_PROJECT]/Brisas notes are mostly Spanish → write the brief in Spanish. University/personal-brand may be English. Match the source.
• Never modify project files. The skill is read-only on 03-projects/.
• "Suggested next action" must be concrete (not "continue working on [YOUR_PROJECT]"). One thing, doable today.
• If _overview.md doesn't exist, say so and offer to create one from the template.
• The session-start log is opt-in — don't write it unless invoked in a session-start context or [OWNER] says so.

Example invocation

[OWNER]: project context [your-project]
→ Read 03-projects/[client-site]/_overview.md and all sub-files
→ Glob 02-daily/, take last 14, Grep for "[your-project-tag]" and "#your-project-tag"
→ Grep 05-knowledge/ for #your-project-tag tag
→ Compile brief → output inline
→ Ask: "Want me to log this as a session start?"