bmad-project-context

Creates and maintains verified AGENTS.md instruction blocks for AI agents in a repository.

Updated Sep 4, 2026
One-click install
npx skills add https://github.com/Joao-Victor-Medeiros/save-sc --skill bmad-project-context-joao-victor-medeiros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-project-context
Source: https://github.com/Joao-Victor-Medeiros/save-sc/tree/main/.agents/skills/bmad-project-context
Command: npx skills add https://github.com/Joao-Victor-Medeiros/save-sc --skill bmad-project-context-joao-victor-medeiros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Repositories accumulate stale, bloated, or missing agent instruction files, causing AI coding agents to repeat mistakes, run wrong commands, and violate team policies. This Skill produces a small, verified, managed block inside AGENTS.md so agents work correctly in that repo. ## Core Features & Use Cases - Setup, adopt, refresh, record, and audit intents: Scaffold new instructions, migrate existing CLAUDE.md or AGENTS.md content into a managed block, re-verify against the current codebase, capture observed agent mistakes as pitfalls, and prune dead lines. - Evidence-based verification: Scans package.json, Makefiles, pyproject.toml, and CI config, path-checks every claim, and diffs against a recorded commit SHA so the block never drifts from reality. - Ledger-driven migration: Every existing instruction is tracked through retain, rewrite, relocate, automate, or delete decisions with explicit grounds, so nothing is silently lost. - Use Case: A team adopting AI coding agents runs the adopt intent to consolidate a sprawling CLAUDE.md into a concise AGENTS.md block, with each original instruction accounted for and unverifiable claims removed. ## Quick Start Ask the agent to set up or refresh this repository's AGENTS.md agent instructions using the bmad-project-context skill.

Frequently Asked Questions about bmad-project-context

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

FAQPage Schema
How do I set up AGENTS.md instructions for AI coding agents?▼

Invoke the skill with the setup intent on a repository that has no meaningful instruction file. It scans configs and CI, interviews you only about what scans cannot answer, then shows the complete block for approval before writing it between managed markers.

How do I migrate CLAUDE.md to AGENTS.md without losing instructions?▼

Use the adopt intent, which treats the existing file as the baseline and opens a ledger entry for every instruction. Each entry settles as retain, rewrite, relocate, automate, or delete with explicit grounds, and the settled ledger is presented alongside the proposed block.

What belongs in a repository's agent instructions file?▼

Admit policy the code cannot express, command caveats configs cannot state, conventions differing from ecosystem defaults, observed pitfalls, and cross-component rules. Exclude directory trees, stack lists, style rules a linter enforces, and anything derivable fresh from the repo.

Can agent instructions be split across nested AGENTS.md files?▼

Yes, but only when rules are subtree-exclusive and substantial, the split materially reduces the root block, the user approves, and loading is verified for every harness in use. Otherwise rules stay at the root as path-qualified lines.

When should an instruction line be deleted during an audit?▼

Deletion requires one of four grounds: the line is stale or incorrect, a hook or CI check mechanically enforces it, it is harmful or contradictory, or the user approves the deletion as a line item. Brevity or recent inactivity is never sufficient grounds.