docs: adopt the shared methodology for projects and labs #1

Merged
claude_bot Bot merged 3 commits from docs/unified-method-20261002 into main 2026-10-02 22:28:43 +00:00
2 changed files with 20 additions and 0 deletions

No files matched your search

+15
View File
@@ -0,0 +1,15 @@
# AGENTS.md — PDAT/claude-plugins
## Adopted shared methodology
The single operating source is the [PDAT shared development method](https://git.pda.cz/PDAT/vision/src/commit/67c9679f4e61437794a13bcaf12cafe7be6ffd18/methodology/development.md), adopted at `67c9679f4e61437794a13bcaf12cafe7be6ffd18`. Common rules take precedence over conflicting process clauses in older guidance below: provider-based roles, WIP/checkpoints, Go code-size limits, specification format, routine commit/push/merge approval and owned-artifact cleanup.
Product vision, accepted architecture, security/auth, existing technical checks, ADR/spec ratification, data/physical-operation and production gates retain their authority. Runtime permissions and provider authentication identities are unchanged. `AGENTS.md` is the common bootstrap; `CLAUDE.md` imports it.
## Project profile
Product/software profile: use the shared [product specification and evidence rules](https://git.pda.cz/PDAT/vision/src/commit/67c9679f4e61437794a13bcaf12cafe7be6ffd18/methodology/spec-lifecycle.md#products). Keep this project's architecture, security, language/build/test and deployment contracts. Small fixes and documentation use proportionate acceptance evidence under the shared method.
## Project context
Read the existing README, architecture/decisions and assigned work record where present. Inspect local status before edits; preserve foreign or active work. Select the applicable technical checks from the project and task; this bootstrap does not assert product readiness or create a new implementation assignment.
+5
View File
@@ -0,0 +1,5 @@
# CLAUDE.md — PDAT/claude-plugins
@AGENTS.md
Read `AGENTS.md` first. It is the common process and project contract; provider-specific settings below retain their existing authentication identity and cannot assign a separate provider-based manager.