bmad-project-context

Curate and maintain verified project context files for AI coding agents.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-project-context-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-project-context
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/bmad-project-context
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-project-context-tuanpa-nhg-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? AI agents work better with a small set of verified, non-derivable project truths than with generated documentation. This Skill builds and maintains that context system: a tiny always-loaded kernel file plus a bundle of small verified knowledge entries covering architecture rationale, conventions, landmines, and org requirements. ## Core Features & Use Cases - Ingest, Query, and Audit intents: Build context from brownfield codebases or greenfield specs, answer questions from the bundle without loading it all, and shrink or re-verify stale entries over time. - Deterministic mechanics script: A bundled Python CLI handles config resolution, index generation, validation, staleness sweeps, cross-project resolution, and syncing kernel content into AGENTS.md files. - Trust tracking and memlog: Every claim is marked verified or generated, every decision lands in an append-only memlog, and refresh runs diff against prior state instead of starting over. - Use Case: Point it at a legacy repo and say "generate project context" — it scans code and docs, confirms claims with you in short rounds, and writes a kernel.md with commands, conventions, and landmines plus linked bundle entries. ## Quick Start Ask the agent to generate project context for this repository and answer its confirmation questions as it scans the code and docs.

Frequently Asked Questions about bmad-project-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate project context for AI agents in my repo?

Invoke the skill with a phrase like "generate project context" and it scans your code, configs, and docs, then confirms inferred claims with you in short rounds. It writes a kernel.md of always-loaded truths plus small bundle entries, all verified before being stated as fact.

What is the difference between the kernel and the bundle?

The kernel is one always-loaded file capped at roughly 150-200 instructions holding only non-derivable, behavior-changing truths. The bundle is a directory of small entries with frontmatter providing depth on demand, indexed by a generated index.md and never loaded wholesale.

Does this work in a repo without a BMad install?

Yes. In a standalone repo the skill bootstraps its context.py script into _bmad/scripts/ and defaults to agent-files placement, writing a managed block into AGENTS.md. No BMad modules or config are required.

How does context refresh avoid re-asking settled questions?

Refresh reads the append-only memlog of every prior run and diffs against it instead of restarting. The sweep command path-checks claims against the current code, and stale or missing-source claims are updated, superseded, or removed.

Can it answer questions from another project's context?

Yes, through the resolve command, which follows a self, workspace, cache, remote order using an obeya registry. It returns a local path, SHA, and freshness for entries linked via [[project:entry]] syntax without crawling the filesystem.

Why does the skill refuse to document things visible in the code?

Its governing thesis is that generated documentation makes agents worse while a curated minimum of verified, non-derivable truths makes them better. Entries that paraphrase readable code fail audit and are deleted.