panxiao81/postgresql-tenant-operator
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: 确立规格先行开发流程

Browse Source
This commit is contained in:
panxiao81
2026-09-10 02:41:45 +00:00
parent 227994bc10
commit 0def13f0c7
1 changed files with 18 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+18
View File
@@ -1,5 +1,23 @@
# postgresql-tenant-operator - AI Agent Guide # postgresql-tenant-operator - AI Agent Guide
## Specification-Driven Development
- Use specification-driven development for every new feature and externally observable
behavior change: decide and document the contract before writing implementation code.
- Create or update the relevant specification first. It must define scope, non-goals,
observable behavior, validation, failure semantics, security boundaries, and acceptance
criteria at the level needed for a human to make the pending decisions.
- Stop after the specification reaches a reviewable state and ask the user to approve it
before implementing the behavior. Approval of a plan, issue, or earlier specification
does not imply approval of materially new decisions.
- Derive tests from the approved acceptance criteria, then implement the smallest vertical
slice that makes those tests pass. Keep specification, tests, and implementation
traceable to one another.
- If implementation exposes an ambiguity or requires changing the approved behavior, stop,
update the specification, and request review again before continuing.
- Keep specifications focused on contracts and decisions. Do not prematurely freeze internal
Go package structure, function names, or SQL details unless they are part of the contract.
## Human-Reviewable Changes ## Human-Reviewable Changes
- Break every feature into small, coherent changes that a human can review independently. - Break every feature into small, coherent changes that a human can review independently.