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:
2026-03-09 12:34:26 +00:00
parent fd5bdd6b0b
commit 33180d6e04
12 changed files with 49 additions and 98 deletions

View File

@@ -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.