agentme 0.28.1 → 0.30.0

package/.xdrs/agentme/edrs/principles/012-continuous-xdr-enrichment.md

@@ -35,7 +35,7 @@ When developers or coding agents need too much detailed steering to complete a t
 
 #### 04-coverage-target-should-be-80-percent
 
-Teams SHOULD aim to keep at least 80% of big coding decisions covered by accepted XDRs. Big decisions include framework or tool selection, overall code organization, monorepo structure, complex business flows, and coding standards. If a big decision is not yet covered, developers SHOULD either propose a new XDR or document why the decision is intentionally local and should not be shared.
+Teams SHOULD aim to keep at least 80% of big coding decisions covered by accepted XDRs. Big decisions include framework or tool selection, overall code organization, monorepo structure, complex business flows, and coding standards. If a big decision is not yet covered, developers SHOULD either propose a new XDR or document why the decision is intentionally local and SHOULD NOT be shared.
 
 #### 05-leaders-must-review-xdr-proposals
 
@@ -58,7 +58,7 @@ In SDD, specifications describe the feature being built; XDRs describe reusable
 
 ## References
 
-- [_core-adr-001](../../../_core/adrs/principles/001-xdrs-core.md)
+- [_core-adr-001](../../../_core/adrs/principles/001-xdrs-standards.md)
 - [_core-article-001](../../../_core/adrs/principles/articles/001-xdrs-overview.md)
 - [agentme-article-001](articles/001-continuous-xdr-improvement.md)
 - [002-write-policy skill](../../../_core/adrs/principles/skills/002-write-policy/SKILL.md)

package/.xdrs/agentme/edrs/principles/016-cross-language-module-structure.md

@@ -25,7 +25,7 @@ Language-specific EDRs MAY add ecosystem details, but they MUST NOT redefine the
 
 A module is the smallest independently buildable, testable, or publishable unit. It MUST live in its own folder and that folder MUST contain:
 
-- a `Makefile` following [agentme-edr-008](../platform/008-common-targets.md)
+- a `Makefile` following [agentme-edr-303](../platform/303-common-targets.md)
 - a `README.md` for the module itself
 - all configuration files needed to build, lint, test, package, or publish that module
 - its generated `dist/` directory when the module produces distributable artifacts
@@ -127,9 +127,9 @@ Benchmark tests MUST live in one of these locations:
 
 #### 08-module-makefiles-must-expose-shared-targets
 
-Every module `Makefile` MUST expose the common target names from [agentme-edr-008](../platform/008-common-targets.md). At minimum, modules MUST provide `build`, `lint`, and `test`, and SHOULD also provide `all`, `clean`, and `lint-fix` when meaningful.
+Every module `Makefile` MUST expose the common target names from [agentme-edr-303](../platform/303-common-targets.md). At minimum, modules MUST provide `build`, `lint`, and `test`, and SHOULD also provide `all`, `clean`, and `lint-fix` when meaningful.
 
 ## References
 
-- [agentme-edr-005](../platform/005-monorepo-structure.md) - Monorepo aggregation and delegation rules
-- [agentme-edr-008](../platform/008-common-targets.md) - Shared Makefile target names
+- [agentme-edr-301](../platform/301-monorepo-structure.md) - Monorepo aggregation and delegation rules
+- [agentme-edr-303](../platform/303-common-targets.md) - Shared Makefile target names

package/.xdrs/agentme/edrs/principles/017-skill-testing.md

@@ -0,0 +1,77 @@
+---
+name: agentme-edr-policy-017-skill-testing
+description: >
+  Mandates a SKILL.test.md test file co-located with every skill, defines the test file format (scenarios with trigger, expected behaviour, and assertions), and requires execution before merging any change to the skill. Use when creating, updating, or reviewing skills.
+apply-to: contributors working in any scope that directly or transitively follows or extends agentme
+valid-from: 2026-08-06
+---
+
+# agentme-edr-policy-017: skill testing
+
+## Context and Problem Statement
+
+Skills evolve over time: phases are reworded, routing tables change, constraints are added. Without an executable specification of what the skill must do, regressions are silent — a changed skill may produce incorrect outputs or miss required steps and nothing catches it until a user files a complaint.
+
+How should skill correctness be verified after every change, in a way that is consistent, co-located with the skill, and executable by either a human or an agent?
+
+## Decision Outcome
+
+**Every skill MUST have a `SKILL.test.md` file in the same directory as its `SKILL.md`. The file defines test scenarios with explicit input triggers and falsifiable assertions. It MUST be executed — using the `200-run-skill-tests` skill or manually — before merging any PR that modifies the skill or its test file.**
+
+### Details
+
+#### 01-mandatory-presence
+
+A skill MUST have a `SKILL.test.md` file in the same directory as `SKILL.md`. The absence of `SKILL.test.md` is treated as an ERROR during any review of the skill directory.
+
+#### 02-file-format
+
+`SKILL.test.md` MUST follow this structure exactly:
+
+```markdown
+---
+skill: [skill-name matching the name: field in SKILL.md frontmatter]
+skill-version: "[x.y matching the version in SKILL.md metadata]"
+---
+
+## Test Scenarios
+
+### Scenario N: [Short Title]
+
+**Trigger / Input**
+[Exact prompt or agent context given to activate and exercise the skill. Must be
+specific enough that two independent agents produce comparable outputs.]
+
+**Expected Behaviour**
+[Numbered list of steps the skill must perform, derived from its Instructions section.]
+
+**Assertions**
+- [ ] [Specific, falsifiable check on the output or behaviour. Start with a verb.]
+- [ ] ...
+```
+
+Rules:
+- MUST contain at least two scenarios: one happy path and one edge or failure case.
+- Each scenario MUST have at least two assertions.
+- Assertions MUST be falsifiable (a pass/fail determination must be possible without ambiguity).
+- Assertion text MUST start with a verb ("Output contains …", "Skill asks …", "Review reports …").
+- MUST NOT duplicate SKILL.md content; reference phases by name only when needed.
+- `skill-version` in frontmatter MUST be updated whenever `version` in SKILL.md changes.
+
+#### 03-execution-requirement
+
+`SKILL.test.md` MUST be executed before merging any PR that modifies the skill or its test file. Execution means running each scenario and verifying all assertions pass.
+
+Use the `200-run-skill-tests` skill to execute the file, or run each scenario manually when automation is not available.
+
+
+## Considered Options
+
+- **Inline test section in SKILL.md** — rejected because it mixes specification and verification, inflating file size past the 6500-word limit and making test-only changes noisy in diffs.
+- **External test registry** — rejected because co-location is the simplest discoverability model and matches the skill folder convention already established by `_core-adr-policy-003`.
+- **Required only for new skills** — rejected because existing skills carry the same regression risk after every edit.
+
+## References
+
+- [`_core-adr-policy-003`](../../../_core/adrs/principles/003-skill-standards.md) — Skill package standards and folder layout
+- [`200-run-skill-tests`](../application/skills/200-run-skill-tests/SKILL.md) — Runner skill that executes `SKILL.test.md` scenarios

package/.xdrs/agentme/edrs/principles/articles/001-continuous-xdr-improvement.md

@@ -87,7 +87,7 @@ If the same clarification would likely be needed in another feature, by another
 
 ## References
 
-- [_core-adr-001](../../../../_core/adrs/principles/001-xdrs-core.md) - XDR structure, numbering, and mandatory template
+- [_core-adr-001](../../../../_core/adrs/principles/001-xdrs-standards.md) - XDR structure, numbering, and mandatory template
 - [_core-article-001](../../../../_core/adrs/principles/articles/001-xdrs-overview.md) - XDR introduction and general adoption guidance
 - [agentme-edr-012](../012-continuous-xdr-enrichment.md) - Shared-first XDR enrichment policy and 80% coverage target
 - [002-write-policy skill](../../../../_core/adrs/principles/skills/002-write-policy/SKILL.md) - Step-by-step procedure for drafting new XDRs

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentme",
-  "version": "0.28.1",
+  "version": "0.30.0",
   "description": "",
   "dependencies": {
     "filedist": "^0.39.0"
@@ -18,6 +18,6 @@
     "url": "https://github.com/flaviostutz/agentme.git"
   },
   "devDependencies": {
-    "xdrs-core": "^0.39.0"
+    "xdrs-core": "^0.45.0"
   }
 }