Skip to content
Skills Library
Management & product · Planning

project-context

/project-context

Project state management using CONTEXT.md files with Past/Current/Future sections. Use when: "project context", "CONTEXT.md", "project status", "where are we", "project state", "new project", "project lifecycle".

Licence
MIT
Last repository change
27.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Project state management using CONTEXT.md files with Past/Current/Future sections. Use when: "project context", "CONTEXT.md", "project status", "where are we", "project state", "new project", "project lifecycle".

Triggers from the description

project contextCONTEXT.mdproject statuswhere are weproject statenew projectproject lifecycle
Original author description

Project state management using CONTEXT.md files with Past/Current/Future sections. Use when: "project context", "CONTEXT.md", "project status", "where are we", "project state", "new project", "project lifecycle".

How it works

  1. When to Use
  2. Location
  3. CONTEXT.md Structure
  4. Project Lifecycle
  5. When to Update CONTEXT.md
  6. Procedure
  7. Template
Original SKILL.md headings · 145 lines, 657 words
SKILL.md preview
---
name: project-context
description: |
  Project state management using CONTEXT.md files with Past/Current/Future sections.
  Use when: "project context", "CONTEXT.md", "project status", "where are we", "project state", "new project", "project lifecycle".
---

# Project Context

Every project has a `CONTEXT.md` that tracks its state across three time horizons. This is the project's memory — read it first, update it always.

## When to Use

- Starting a new project → Create CONTEXT.md
- Resuming work → Read CONTEXT.md to get current state
- After significant progress → Update Current section
- Making a decision → Add to Past → Key Decisions
- Planning next steps → Review and update Future section
- Pausing or completing a project → Update lifecycle stage

## Location

```
Second Brain/Projects/{project-name}/
├── README.md       ← What is this project? (stable overview)
├── CONTEXT.md      ← Past / Current / Future (living document)
└── {working files} ← Notes, docs, research
```

## CONTEXT.md Structure

### Past (How We Got Here)

This section grows over time. It's the project's history.

- **Origin**: Why this project exists. What problem triggered it.
- **Key Decisions**: Important choices and their reasoning (date + what + why)
- **Lessons**: What we learned that might be useful later

### Current (Where We Are)

This section changes frequently — it's the "state snapshot."

- **Status**: One-line summary (e.g., "Active — building MVP", "Paused — waiting on API access")
- **Tasks**: Active work items with status
- **Blockers**: What's preventing progress (with workarounds if known)

### Future (Where We're Going)

This section provides direction and surfaces uncertainty.

- **Next Milestone**: Concrete deliverable with rough timeline
- **End Goal**: What done looks like
- **Open Questions**: Unresolved decisions that affect direction

## Project Lifecycle

Projects move through stages. Track the stage in CONTEXT.md frontmatter (`status:` field) and update as transitions happen.

```
Idea → Active → [Paused] → Done → [Archived]
```

### Stage: Idea

A captured project that isn't actively being worked on.

```yaml
status: idea
```

**What to do**: Create minimal CONTEXT.md with Past (why) and Future (what done looks like). No Current section needed yet.

### Stage: Active

The project is being worked on. CONTEXT.md is updated regularly.

```yaml
status: active
```

**What to do**: Full CONTEXT.md with all three sections. Update after each session.

### Stage: Paused

Intentionally on hold. The key is documenting **why** and **when to resume**.

```yaml
status: paused
```

**What to do**: Update Current with:
- Why it's paused
- What state things are in (don't lose context)
- Conditions for resuming ("Resume when X happens")

### Stage: Done

Project goals are met.

```yaml
status: done
```

**What to do**: Final CONTEXT.md update:
- Move final status to Past
- Document final lessons learned
- Note what worked and what didn't

### Stage: Archived

No longer relevant. Move to `Second Brain/Projects/done/` if desired.

## When to Update CONTEXT.md

| Event | What to Update |
|-------|----------------|
| Task completed | Current → Tasks |
| New blocker found | Current → Blockers |
| Decision made | Past → Key Decisions (with date + reasoning) |
| Direction changed | Future → Next Milestone, and Past → Key Decisions |
| Milestone reached | Move to Past, set new Future milestone |
| Session ends with progress | Current → Status, Current → Tasks |
| Project paused | Status field, Current → explain why |

## Procedure

### At Session Start

1. Read the project's CONTEXT.md
2. Focus on Current section — what's the status, what's active, what's blocked?
3. Check if Future → Next Milestone is still accurate

### During Work

Update as state changes:
- Complete a task → mark it done in Current → Tasks
- Hit a blocker → add to Current → Blockers with what you tried
- Make a decision → add to Past → Key Decisions with reasoning

### At Session End

1. Update Current section to reflect session progress
2. Move completed milestones to Past if significant
3. Adjust Future if plans changed
4. Update `updated:` date in frontmatter

## Template

See [template.md](template.md) for the full Obsidian Templater template.
Files in this package (2)
  • SKILL.md 4 KB
  • template.md 1 KB

Versions

RepositoryScoreLicence
This page · joint-hubs/jointhubs-os100MIT
egorfedorov/claude-context-optimizer100MIT
trihuynh-agilityio/workez100MIT
ob-labs/powercontext-go100Apache-2.0
ob-labs/powercontext-go100Apache-2.0
ob-labs/powercontext-go100Apache-2.0
upex-galaxy/agentic-qa-boilerplate90MIT
ob-labs/powercontext-go90Apache-2.0
ob-labs/powercontext-go90Apache-2.0

Database snapshot: 13.11.2026 · package version 8f93a0859f90 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100project-dashboard
    This skill should be used when users ask 'where am I?', 'what is my progress?', mentions 'status', 'dashboard', 'progress', wants to know if they are ready for the next stage, or needs an overview of their project state.
  • 100project-dashboard
    This skill should be used when users ask 'where am I?', 'what is my progress?', mentions 'status', 'dashboard', 'progress', wants to know if they are ready for the next stage, or needs an overview of their project state.
  • 84bf-status
    Use when the user asks where a brownfield rebuild stands or which bf command is next.
  • 95recreate-status
    Shows where an Recreate project stands: which stages have run, what they produced, what has gone stale, what the working files get wrong, and the one stage to run next. Also starts a new project. Use when the user says "where are we", "what's next", "status", "did we do the…
  • 100status
    Show where a Builder Method project stands — which phases are done, which step is current, what is missing, pending decisions and unreviewed outputs — and refresh the visual progress page. Use when the user asks "where am I", "how far along is it" or "what's missing".
  • 100requirements-framework-status
    This skill should be used when the user asks to "requirements framework status", "show requirements project context", "what's the state of requirements framework", "requirements framework overview", or wants a comprehensive status report of the requirements framework…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.