fix: flip symlink structure - AGENTS.md is the real file
AGENTS.md is now the canonical instruction file, with CLAUDE.md, .cursorrules, and .github/copilot-instructions.md as symlinks to it. This is simpler and more intuitive - the main file is at the root, not buried in .github/. Updated all references across agents, commands, skills, and .memory/.
This commit is contained in:
@@ -140,7 +140,7 @@ Minimum viable workflow for well-understood follow-on work: **PLAN → EXECUTE
|
||||
- Memory: record reusable patterns in `.memory/decisions.md` under `## Retrospective: <topic>`.
|
||||
- **Librarian dispatch:** After significant feature work, dispatch `librarian` to:
|
||||
1. Update project documentation (README, docs/*)
|
||||
2. Update `.github/copilot-instructions.md` if project conventions/architecture changed
|
||||
2. Update `AGENTS.md` if project conventions/architecture changed
|
||||
3. Update `.memory/knowledge.md` with new architecture/pattern knowledge
|
||||
|
||||
## Knowledge Freshness Loop
|
||||
@@ -369,6 +369,6 @@ This is a ~30-second mental check, not a full review. If something looks obvious
|
||||
## Documentation Completion Gate
|
||||
|
||||
- For every completed project change set, documentation must be created or updated.
|
||||
- Minimum required documentation coverage: `README` + relevant `docs/*` files + `.github/copilot-instructions.md` when project conventions, commands, architecture, workflow, policies, or agent behavior changes.
|
||||
- Minimum required documentation coverage: `README` + relevant `docs/*` files + `AGENTS.md` when project conventions, commands, architecture, workflow, policies, or agent behavior changes.
|
||||
- **Documentation is a completion gate, not a follow-up task.** Do not declare a task done, ask "what's next?", or proceed to commit until doc coverage is handled or explicitly deferred by the user. Waiting for the user to ask is a failure.
|
||||
- **Always delegate to `librarian`** for documentation coverage checks and cross-tool instruction file maintenance. The librarian is the specialist — do not skip it or handle docs inline when the librarian can be dispatched.
|
||||
|
||||
@@ -14,7 +14,7 @@ You are the Librarian subagent.
|
||||
Purpose:
|
||||
|
||||
- Ensure project documentation and knowledge artifacts are created, updated, and accurate.
|
||||
- Maintain the instruction file (`.github/copilot-instructions.md`) and its symlinks.
|
||||
- Maintain the instruction file (`AGENTS.md`) and its symlinks.
|
||||
- Keep `.memory/` files accurate and useful as the project evolves.
|
||||
|
||||
## Core Responsibilities
|
||||
@@ -29,11 +29,11 @@ Purpose:
|
||||
|
||||
### 2. Instruction File
|
||||
|
||||
Maintain `.github/copilot-instructions.md` as the single source of truth:
|
||||
Maintain `AGENTS.md` as the single source of truth:
|
||||
|
||||
- **Update when project knowledge changes**: architecture, conventions, commands, structure
|
||||
- **Content should include**: project purpose, tech stack, architecture, conventions, build/test/lint commands, project structure
|
||||
- **Verify symlinks exist**: `AGENTS.md`, `CLAUDE.md`, `.cursorrules` should all point to `.github/copilot-instructions.md`
|
||||
- **Verify symlinks exist**: `CLAUDE.md`, `.cursorrules`, `.github/copilot-instructions.md` should all point to `AGENTS.md`
|
||||
- **Do NOT duplicate `.memory/` contents** — instruction file is for "how to work here", not "what we're doing"
|
||||
|
||||
### 3. Memory File Maintenance
|
||||
|
||||
Reference in New Issue
Block a user