AGENTS.md

1# Project Agent Instructions
2 
3## Scope
4 
5These instructions apply to the whole repository.
6 
7## Truth Sources
8 
9- Core workflow: `plugins/spec-driven-develop/skills/spec-driven-develop/SKILL.md`
10- Shared workflow references: `plugins/spec-driven-develop/skills/spec-driven-develop/references/`
11- Claude Code sub-agent prompts: `plugins/spec-driven-develop/agents/`
12- OpenCode plugin entrypoint: `plugins/spec-driven-develop/opencode-plugin.js`
13- Plugin manifests: `plugins/spec-driven-develop/.claude-plugin/plugin.json`, `plugins/spec-driven-develop/.codex-plugin/plugin.json`, and the root `.claude-plugin/marketplace.json`
14- Validation and helper scripts: `scripts/`
15- User-facing docs: `README.md` and `README.zh-CN.md`
16- Persistent project memory: use the active coding agent's native project memory surface when available. Do not add a repository fallback memory file unless the workflow explicitly records that choice.
17 
18## Development Rules
19 
20- Keep this repository Markdown-first. Do not add runtime dependencies unless a requested feature truly needs executable tooling.
21- For workflow behavior changes, update the core `SKILL.md`, the affected references/templates, and the affected agent prompts together. Avoid one-line prompt patches that leave other execution surfaces stale.
22- When changing user-visible behavior, keep `README.md` and `README.zh-CN.md` consistent.
23- `AGENTS.md` and `CLAUDE.md` are active project-level instruction surfaces. Keep them aligned; use `CLAUDE.md` only for Claude Code-specific notes and point back here for shared rules.
24- New features or behavior changes must add or update relevant tests when an automated test surface exists. If no automated suite exists, run the closest static/syntax checks and document why no test was added.
25- Record stable cross-session decisions in the native project memory surface when one is available. If none is available, record only agent-facing rules in `AGENTS.md`/`CLAUDE.md`; do not invent a repo-local memory file without an explicit workflow decision.
26 
27## Validation
28 
29Run the standing consistency guard first; it subsumes the Python byte-compile check. Then use the closest checks for the changed surface:
30 
31- `bash scripts/validate.sh`
32- `bash -n scripts/install-codex.sh scripts/install-cursor.sh scripts/install-opencode.sh scripts/install-agents.sh scripts/install-all.sh`
33- Targeted `rg` checks for newly required workflow language
34- `git diff --check`
35