agentme 0.7.5 → 0.8.1

package/.specify/memory/constitution.md

@@ -40,78 +40,59 @@ vibe coding, onboarding, and future feature development.
 - EDRs capture concrete engineering decisions: tooling, structure, practices.
 - Every non-trivial implementation decision MUST have a corresponding XDR entry before the implementation task is marked complete. Create new XDRs if necessary.
 
-### II. Preset Integrity (NON-NEGOTIABLE)
+### II. XDR as the Single Source of Truth for All Policies
 
-agentme distributes files to consumer projects via named presets (`basic`, `speckit`). Each
-preset MUST be independently coherent, non-overlapping, and verified on every build.
+All quality standards, business policies, architectural policies, and engineering policies that
+specs, plans, and implementations must follow MUST be captured exclusively in XDRs. The
+constitution does not restate those rules; it defers to them.
 
-- A preset MUST contain all files a consumer needs and nothing more.
-- Presets MUST NOT share extraction sets unless the consumer explicitly requests multiple presets.
-- The `examples/` folder MUST assert the exact file presence/absence for each preset combination
-  after every `make build`.
-- Adding a file to a preset or changing selector patterns is a public API change and requires a
-  version bump (MINOR or MAJOR depending on impact).
-
-### III. Consumer-First API Discipline
-
-XDRs, skills, and preset file sets are a public API consumed by external projects. Changes MUST
-respect semantic versioning.
-
-- MAJOR: removing or renaming a preset, removing or restructuring an XDR that external consumers
-  reference, or any change that requires consumer-side migration.
-- MINOR: adding a new preset, adding XDRs or skills, adding files to an existing preset.
-- PATCH: wording, clarifications, typo fixes inside XDRs or skills that carry no structural change.
-- Breaking changes MUST be documented in the release notes and in the relevant XDR's `Conflicts`
-  or `Implementation Details` section before merging.
-
-### IV. Self-Contained Artifacts
-
-Every XDR and skill MUST work without any implicit context outside itself.
-
-- XDRs MUST be under 100 lines (hard limit 200 for templates and elaborate decisions).
-- Skills MUST be under 500 lines; lengthy reference material goes in `references/`.
-- Internal cross-references MUST use relative file paths; no absolute or external URLs without
-  explanation.
-- A consumer reading an XDR or skill for the first time MUST be able to follow it without
-  accessing other systems.
-
-### V. Simplicity and Verified Quality
-
-The simplest solution that passes all tests is always preferred. Quality gates are non-negotiable.
-
-- `make test` MUST pass before any release; failures block publish.
-- Linting MUST be clean (`make lint-fix`) before merging.
-- Files MUST NOT exceed 400 lines (test files excepted).
-- No feature scope creep: implement only what the current spec requires.
-- Avoid adding error handling, fallbacks, or abstractions for hypothetical future scenarios.
-
-## Quality Requirements
-
-- `make test` in `examples/` MUST verify all preset extraction scenarios end-to-end.
-- XDRs produced during a feature MUST be reviewed for non-conflict before merging.
-- All XDR indexes (`_local`, `agentme`, `_core`) MUST be updated before a PR is merged.
-- New presets or selector changes MUST include updated test assertions in the examples Makefile.
+- Quality gates (testing, linting, coverage thresholds, file-size limits) → EDRs.
+- Business rules, consumer workflows, versioning contracts → BDRs.
+- Architectural patterns, cross-cutting concerns, dependency strategies → ADRs.
+- If a policy is not in an XDR, it is not an enforceable policy. Write the XDR first.
+- Agents and humans MUST consult the XDR index before starting any work and MUST follow every
+  relevant XDR found there without exception.
 
 ## Development Workflow
 
 1. Before starting a feature: check existing XDRs for applicable decisions.
 2. During specifying (`speckit.specify`): capture business requirements as BDRs in `_local`.
+   **After every `speckit.specify` run the agent MUST offer to run `speckit.clarify` (refine)
+   before proceeding to planning. This is non-negotiable.**
 3. During planning (`speckit.plan`): update or create ADRs and EDRs in `_local` that reflect
    architectural and engineering decisions made during the planning phase.
+   **After every `speckit.plan` run the agent MUST propose running `speckit.checklist` to enrich
+   the plan with domain-specific quality checks before generating tasks.**
 4. During implementation: follow XDRs; create new `_local` XDRs for decisions not yet captured.
 5. After implementation: delete feature specs and plans; XDRs remain permanently.
 6. Runtime guidance: see `.xdrs/index.md` and all linked scope indexes.
 
+## XDR Compliance Check (Mandatory at Every Stage)
+
+Every Spec, Refinement (clarify), Plan, Checklist, and Implementation task MUST include an
+explicit step that verifies compliance with the XDRs present in the repository:
+
+1. Read `.xdrs/index.md` and all linked scope indexes (`_local`, `agentme`, `_core`).
+2. Identify every XDR relevant to the work being performed.
+3. Confirm that the artifact (spec, plan, task list, or code change) does not contradict any
+   relevant XDR.
+4. If a contradiction or gap is found: either update the artifact to comply, or create/update the
+   relevant XDR to reflect the new decision before continuing.
+5. Document the compliance check result in the artifact (e.g., a "XDR Compliance" section or
+   comment) so reviewers can audit it.
+
+No artifact may be considered complete without a passed XDR compliance check.
+
 ## Governance
 
 This constitution supersedes all other development practices within this repository. Amendments
 require:
-1. A version bump following semantic versioning rules stated in Principle III.
+1. A version bump following semantic versioning rules stated in the relevant BDR/ADR/EDR.
 2. An updated `LAST_AMENDED_DATE` in this file.
-3. A review of all five principles for continued non-conflict.
+3. A review of all principles for continued non-conflict.
 4. An updated Sync Impact Report (HTML comment at the top of this file).
 
-All PRs MUST include a "Constitution Check" section confirming compliance with all five principles.
+All PRs MUST include a "Constitution Check" section confirming compliance with all principles.
 Complexity MUST be justified; if a solution requires deviation from a principle, that deviation
 MUST be documented in a new or updated XDR in `_local`.
 

package/.xdrs/agentme/edrs/application/003-javascript-project-tooling.md

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-003-javascript-project-tooling-and-structure
+name: agentme-edr-policy-003-javascript-project-tooling-and-structure
 description: Defines the standard JavaScript and TypeScript project toolchain and layout using Mise, pnpm, TypeScript, ESLint, Jest, and Makefiles. Use when scaffolding or reviewing JavaScript projects.
 ---
 
-# agentme-edr-003: JavaScript project tooling and structure
+# agentme-edr-policy-003: JavaScript project tooling and structure
 
 ## Context and Problem Statement
 

package/.xdrs/agentme/edrs/application/010-golang-project-tooling.md

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-010-go-project-tooling-and-structure
+name: agentme-edr-policy-010-go-project-tooling-and-structure
 description: Defines the standard Go project toolchain, layout, and Makefile workflow using Mise for agentme-based projects. Use when scaffolding or reviewing Go projects.
 ---
 
-# agentme-edr-010: Go project tooling and structure
+# agentme-edr-policy-010: Go project tooling and structure
 
 ## Context and Problem Statement
 

package/.xdrs/agentme/edrs/application/014-python-project-tooling.md

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-014-python-project-tooling-and-structure
+name: agentme-edr-policy-014-python-project-tooling-and-structure
 description: Defines the standard Python project toolchain, layout, and Makefile workflow using Mise, uv, ruff, pyright, pytest, and pip-audit. Use when scaffolding or reviewing Python projects.
 ---
 
-# agentme-edr-014: Python project tooling and structure
+# agentme-edr-policy-014: Python project tooling and structure
 
 ## Context and Problem Statement
 

package/.xdrs/agentme/edrs/application/015-cli-tool-standards.md

@@ -1,10 +1,9 @@
 ---
-name: agentme-edr-015-cli-tool-standards
+name: agentme-edr-policy-015-cli-tool-standards
 description: Defines how distributable CLI tools should separate command handling from library logic and expose consistent command behavior. Use when designing or reviewing CLI interfaces.
-applied-to: Distributable CLI tools and their standalone libraries
 ---
 
-# agentme-edr-015: CLI tool standards
+# agentme-edr-policy-015: CLI tool standards
 
 ## Context and Problem Statement
 

package/.xdrs/agentme/edrs/application/skills/001-create-javascript-project/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: 001-create-javascript-project
+name: agentme-edr-skill-001-create-javascript-project
 description: >
   Scaffolds the initial boilerplate structure for a JavaScript/TypeScript library project following
   the standard tooling and layout defined in agentme-edr-003. Activate this skill when the user

package/.xdrs/agentme/edrs/application/skills/003-create-golang-project/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: 003-create-golang-project
+name: agentme-edr-skill-003-create-golang-project
 description: >
   Scaffolds the initial boilerplate structure for a Go (Golang) CLI or library project following
   the standard tooling and layout defined in agentme-edr-010. Activate this skill when the user

package/.xdrs/agentme/edrs/application/skills/004-select-relevant-xdrs/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: 004-select-relevant-xdrs
+name: agentme-edr-skill-004-select-relevant-xdrs
 description: >
    Analyzes a client repository, extracts the full agentme XDR set, and excludes the records that do
    not fit the project's structure and workflow needs. Activate this skill when the user asks to

package/.xdrs/agentme/edrs/application/skills/005-create-python-project/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: 005-create-python-project
+name: agentme-edr-skill-005-create-python-project
 description: >
   Scaffolds the initial boilerplate structure for a Python library or CLI project following the
   standard tooling and layout defined in agentme-edr-014. Activate this skill when the user asks

package/.xdrs/agentme/edrs/devops/005-monorepo-structure.md

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-005-monorepo-structure
+name: agentme-edr-policy-005-monorepo-structure
 description: Defines the standard monorepo layout, naming, and build conventions using shared areas, Mise, and Makefiles. Use when creating or reviewing monorepos.
 ---
 
-# agentme-edr-005: Monorepo structure
+# agentme-edr-policy-005: Monorepo structure
 
 ## Context and Problem Statement
 

package/.xdrs/agentme/edrs/devops/006-github-pipelines.md

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-006-github-ci-cd-pipelines
+name: agentme-edr-policy-006-github-ci-cd-pipelines
 description: Defines the standard GitHub Actions workflow split for CI, release tagging, and publishing. Use when configuring project automation.
 ---
 
-# agentme-edr-006: GitHub CI/CD pipelines
+# agentme-edr-policy-006: GitHub CI/CD pipelines
 
 ## Context and Problem Statement
 

package/.xdrs/agentme/edrs/devops/008-common-targets.md

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-008-common-development-script-names
+name: agentme-edr-policy-008-common-development-script-names
 description: Defines standard Makefile target names and the mandatory tool-execution flow using Mise. Use when designing build, lint, test, and release entry points.
 ---
 
-# agentme-edr-008: Common development script names
+# agentme-edr-policy-008: Common development script names
 
 ## Context and Problem Statement
 

package/.xdrs/agentme/edrs/devops/017-tool-execution-and-scripting.md

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-017-tool-execution-and-scripting
+name: agentme-edr-policy-017-tool-execution-and-scripting
 description: Defines how Makefiles, CI pipelines, and optional wrapper scripts execute project commands. Use when designing project automation or command entry points.
 ---
 
-# agentme-edr-017: Tool execution and scripting
+# agentme-edr-policy-017: Tool execution and scripting
 
 ## Context and Problem Statement
 

package/.xdrs/agentme/edrs/devops/skills/002-monorepo-setup/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: 002-monorepo-setup
+name: agentme-edr-skill-002-monorepo-setup
 description: >
   Step-by-step instructions for setting up and scaffolding a new monorepo following the standard
   layout, naming conventions, Makefiles, Mise tooling, and README requirements defined in

package/.xdrs/agentme/edrs/governance/013-contributing-guide-requirements.md

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-013-contributing-guide-requirements
+name: agentme-edr-policy-013-contributing-guide-requirements
 description: Defines the minimum contributor workflow guidance required in root CONTRIBUTING.md files. Use when scaffolding or reviewing contribution processes.
 ---
 
-# agentme-edr-013: Contributing guide requirements
+# agentme-edr-policy-013: Contributing guide requirements
 
 ## Context and Problem Statement
 

package/.xdrs/agentme/edrs/observability/011-service-health-check-endpoint.md

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-011-service-health-check-endpoint
+name: agentme-edr-policy-011-service-health-check-endpoint
 description: Defines the required health endpoint contract for service availability and dependency readiness checks. Use when implementing or reviewing service health endpoints.
 ---
 
-# agentme-edr-011: Service health check endpoint
+# agentme-edr-policy-011: Service health check endpoint
 
 ## Context and Problem Statement
 

package/.xdrs/agentme/edrs/principles/002-coding-best-practices.md

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-002-coding-best-practices
+name: agentme-edr-policy-002-coding-best-practices
 description: Defines cross-language coding practices for keeping code readable, modular, and synchronized with tests and documentation. Apply across projects adopting agentme engineering standards.
 ---
 
-# agentme-edr-002: Coding best practices
+# agentme-edr-policy-002: Coding best practices
 
 ## Context and Problem Statement
 

package/.xdrs/agentme/edrs/principles/004-unit-test-requirements.md

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-004-unit-test-requirements
+name: agentme-edr-policy-004-unit-test-requirements
 description: Defines unit test requirements for assertions, offline execution, coverage, shared setup, and real-code preference. Use when writing or reviewing tests.
 ---
 
-# agentme-edr-004: Unit test requirements
+# agentme-edr-policy-004: Unit test requirements
 
 ## Context and Problem Statement
 

package/.xdrs/agentme/edrs/principles/007-project-quality-standards.md

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-007-project-quality-standards
+name: agentme-edr-policy-007-project-quality-standards
 description: Defines minimum project quality standards for README onboarding, testing, linting, XDR compliance, and runnable examples. Use when scaffolding or reviewing projects.
 ---
 
-# agentme-edr-007: Project quality standards
+# agentme-edr-policy-007: Project quality standards
 
 ## Context and Problem Statement
 

package/.xdrs/agentme/edrs/principles/009-error-handling.md

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-009-error-handling
+name: agentme-edr-policy-009-error-handling
 description: Defines error handling practices for catching, propagating, surfacing, and testing failures consistently across projects. Use when implementing interfaces and failure paths.
 ---
 
-# agentme-edr-009: Error handling
+# agentme-edr-policy-009: Error handling
 
 ## Context and Problem Statement
 

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

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-012-continuous-xdr-improvement-policy
+name: agentme-edr-policy-012-continuous-xdr-improvement-policy
 description: Defines how teams should promote reusable implementation guidance into shared XDRs instead of keeping it in prompts or local habits. Use when recurring decisions surface during delivery.
 ---
 
-# agentme-edr-012: Continuous xdr improvement policy
+# agentme-edr-policy-012: Continuous xdr improvement policy
 
 ## Context and Problem Statement
 
@@ -41,4 +41,4 @@ Developers must treat reusable missing guidance discovered during implementation
 - [_core-adr-001](../../../_core/adrs/principles/001-xdrs-core.md)
 - [_core-article-001](../../../_core/adrs/principles/articles/001-xdrs-overview.md)
 - [agentme-article-001](articles/001-continuous-xdr-improvement.md)
-- [002-write-xdr skill](../../../../.github/skills/002-write-xdr/SKILL.md)
+- [002-write-policy skill](../../../../.github/skills/002-write-policy/SKILL.md)

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

@@ -1,9 +1,9 @@
 ---
-name: agentme-edr-016-cross-language-module-structure
+name: agentme-edr-policy-016-cross-language-module-structure
 description: Defines the baseline module-root structure, artifact locations, cache placement, README expectations, examples layout, and test folder conventions across languages. Use when creating or reviewing buildable modules.
 ---
 
-# agentme-edr-016: Cross-language module structure
+# agentme-edr-policy-016: Cross-language module structure
 
 ## Context and Problem Statement
 

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

@@ -1,4 +1,4 @@
-# agentme-article-001: Continuous XDR improvement
+# agentme-edr-article-001: Continuous XDR improvement
 
 ## Overview
 
@@ -90,4 +90,4 @@ If the same clarification would likely be needed in another feature, by another
 - [_core-adr-001](../../../../_core/adrs/principles/001-xdrs-core.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-xdr skill](../../../../../.github/skills/002-write-xdr/SKILL.md) - Step-by-step procedure for drafting new XDRs
+- [002-write-policy skill](../../../../../.github/skills/002-write-policy/SKILL.md) - Step-by-step procedure for drafting new XDRs

package/.xdrs/index.md

@@ -6,6 +6,8 @@ This index points to all type- and scope-specific XDR indexes. XDRs (Decision Re
 
 XDRs in scopes listed last override the ones listed first
 
+XDRS scopes listed last override the ones listed first
+
 ### _core
 
 Decisions about how XDRs work

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "agentme",
-  "version": "0.7.5",
+  "version": "0.8.1",
   "description": "",
   "dependencies": {
-    "filedist": "^0.26.0",
-    "xdrs-core": "^0.21.0"
+    "filedist": "^0.31.0",
+    "xdrs-core": "^0.26.0"
   },
   "bin": "bin/filedist.js",
   "files": [
@@ -24,7 +24,7 @@
   "filedist": {
     "sets": [
       {
-        "package": "xdrs-core",
+        "package": "xdrs-core@latest",
         "selector": {
           "files": [
             ".xdrs/_core/**",