agentme 0.19.0 → 0.20.1

package/.filedist-package.yml

@@ -1,5 +1,5 @@
 sets:
-  - package: xdrs-core@0.28.3
+  - package: xdrs-core@0.30.0
   # - package: git:https://github.com/flaviostutz/xdrs-core.git@main
     selector:
       files:
@@ -41,38 +41,3 @@ sets:
     presets:
       - basic
 
-  - selector:
-      files:
-        - .github/agents/speckit*
-        - .github/prompts/speckit*
-        - .specify/**
-      exclude:
-        - .specify/templates/**
-    output:
-      path: .
-      gitignore: false
-      readonly: true
-    presets:
-      - speckit
-
-  - selector:
-      files:
-        - .specify/templates/**
-    output:
-      path: .
-      gitignore: false
-      readonly: false
-    presets:
-      - speckit
-
-  - selector:
-      files:
-        - .vscode/settings.json
-    output:
-      path: .
-      managed: false
-      skipIfExists: true
-      readonly: false
-      gitignore: false
-    presets:
-      - speckit

package/.xdrs/agentme/edrs/application/019-ai-agents-development-standards.md

@@ -178,7 +178,7 @@ e.g.: Respond with a JSON object matching this schema: ... ALWAYS return valid J
 </WORKFLOW_CONTEXT>
 
 <SYSTEM_CONTEXT>
-The current date/time is [now in ISO 8601 format].
+The current date is [today in YYYY-MM-DD format].
 The current OS is: [operating system name].
 </SYSTEM_CONTEXT>
 ```
@@ -187,7 +187,7 @@ The current OS is: [operating system name].
 
 | Section | Required? | Notes |
 |---|---|---|
-| `<SYSTEM_CONTEXT>` | Optional | Runtime environment context injected at invocation time (e.g., current date/time in ISO 8601, OS). Include whenever the agent may need temporal or environment awareness. |
+| `<SYSTEM_CONTEXT>` | Optional | Runtime environment context injected at invocation time (e.g., current date in YYYY-MM-DD, OS). Include whenever the agent may need temporal or environment awareness. Time MUST NOT be included — it changes every second and breaks prompt caching. |
 | `<OBJECTIVE>` | Required | One or two sentences summarising the agent's main deliverable. |
 | `<ROLE>` | Required | Agent persona and expertise. When inside a workflow, MUST reference its node name from `<WORKFLOW_CONTEXT>`. |
 | `<INPUT>` | Required | List ALL inputs. For workflow agents: workflow-level inputs first, then agent-specific inputs. |

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

@@ -1,5 +1,5 @@
 ---
-name: agentme-edr-skill-001-create-javascript-project
+name: 001-create-javascript-project
 description: >
   Scaffolds the initial boilerplate structure for a JavaScript/TypeScript 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: agentme-edr-skill-003-create-golang-project
+name: 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: agentme-edr-skill-004-select-relevant-xdrs
+name: 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
@@ -15,8 +15,7 @@ compatibility: Node.js 18+
 
 Installs the full agentme XDR set for a repository through the published CLI, then removes only the
 records that clearly do not fit the target project by passing explicit `--exclude` flags during
-extraction. When the repository also needs speckit workflow artifacts, the skill adds that decision
-separately instead of using presets to narrow the XDR set.
+extraction.
 
 ## Instructions
 
@@ -25,7 +24,7 @@ separately instead of using presets to narrow the XDR set.
 1. Discover how the current published package exposes extraction. Prefer the package CLI help,
    installed package metadata, and the agentme README so you know how to invoke:
    - the full XDR extraction path with `extract --all`
-   - any optional workflow artifacts such as `speckit`
+   - any optional workflow artifacts
 2. Build an explicit inventory of the shipped agentme XDR files so exclusions can be chosen by
    stable path.
 3. If the runtime environment cannot enumerate the shipped XDRs directly, fall back to the package
@@ -41,16 +40,13 @@ separately instead of using presets to narrow the XDR set.
    - project shape (single package, monorepo, library, application, CLI, service)
    - frameworks and tooling (`next.config.*`, `vite.config.*`, `jest.config.*`, `.mise.toml`,
      `docker-compose.*`, CI workflows, Makefiles)
-   - existing agent workflow files (`.xdrs/`, `AGENTS.md`, `.github/agents/`, `.github/prompts/`,
-     `.specify/`, `.vscode/settings.json`)
+   - existing agent workflow files (`.xdrs/`, `AGENTS.md`, `.github/agents/`, `.github/prompts/`)
 2. Determine whether the repository already has:
    - XDR-driven guidance in `.xdrs/`
-   - spec-driven workflow artifacts from speckit
    - local conventions that would make a preset redundant or conflicting
 3. Summarize the project in a short decision note before selecting exclusions:
    - what the project is
    - which languages and frameworks are present
-   - whether it appears to want only XDRs or also agent workflow scaffolding such as `speckit`
 4. From that analysis, build a candidate list of XDRs that are obviously out of scope for the
    repository. Only include exclusions when the mismatch is concrete, for example:
    - language-specific XDRs for languages not used in the repository
@@ -59,7 +55,7 @@ separately instead of using presets to narrow the XDR set.
 5. Do not exclude baseline or broadly applicable guidance just because the project is small or
    simple. Exclusions must remove only XDRs that would clearly mislead the repository.
 
-### Phase 3: Select exclusions and optional workflow artifacts
+### Phase 3: Select exclusions
 
 1. Start from the full shipped agentme XDR set as the default installation target.
 2. Reduce that set only by excluding the XDRs that clearly do not fit the repository. Use
@@ -68,18 +64,10 @@ separately instead of using presets to narrow the XDR set.
    - `.xdrs/agentme/edrs/devops/005-monorepo-structure.md` for non-monorepos
    - `.xdrs/agentme/edrs/observability/011-service-health-check-endpoint.md` for projects without
      a long-running service surface
-3. Decide separately whether the repository also needs `speckit` workflow artifacts.
-4. Use these default workflow selection rules for the current agentme artifact set:
-   - Install the full XDR set when the repository wants agentme decision records, `AGENTS.md`, or a
-     baseline decision framework.
-   - Add `speckit` only when the repository already uses speckit artifacts, explicitly asks for
-     specification-driven workflow support, or clearly needs the `.github/agents/`, `.github/prompts/`,
-     `.specify/`, and related workflow files shipped by that preset.
-5. If the repository does not want agentme XDRs and does not want any optional workflow artifacts,
-   stop and explain why instead of forcing an installation.
-6. State the final decision with:
+3. If the repository does not want agentme XDRs, stop and explain why instead of forcing an
+   installation.
+4. State the final decision with:
    - whether full XDR extraction will run
-   - whether `speckit` will be added
    - the final exclude list with one-line rationale per excluded XDR
 
 ### Phase 4: Install the selected presets
@@ -91,28 +79,18 @@ separately instead of using presets to narrow the XDR set.
    npx -y agentme extract --output . --all --exclude <xdr-path> --exclude <xdr-path>
    ```
 
-3. If the repository also needs `speckit`, run that extraction separately so the workflow decision
-   stays explicit:
-
-   ```sh
-   npx -y agentme extract --output . --presets speckit
-   ```
-
-4. If the user wants a pinned dependency instead of one-off extraction, prefer:
+3. If the user wants a pinned dependency instead of one-off extraction, prefer:
 
    ```sh
    pnpm add -D agentme
    pnpm exec agentme extract --output . --all --exclude <xdr-path> --exclude <xdr-path>
-   pnpm exec agentme extract --output . --presets speckit
    ```
 
-5. After extraction, verify that the expected XDR files now exist:
+4. After extraction, verify that the expected XDR files now exist:
    - `.xdrs/index.md`, `.xdrs/agentme/`, `AGENTS.md`
-6. If `speckit` was selected, verify that its workflow files now exist:
-   - `.github/agents/`, `.github/prompts/`, `.specify/`, `.vscode/settings.json`
-7. Also verify that each excluded XDR path is absent from the extracted output.
-8. Report whether full XDR extraction ran, whether `speckit` was added, which XDRs were excluded
-   with `--exclude`, and the paths that were added or updated.
+5. Also verify that each excluded XDR path is absent from the extracted output.
+6. Report whether full XDR extraction ran, which XDRs were excluded with `--exclude`, and the
+   paths that were added or updated.
 
 ### Phase 5: Handle conflicts and repeat runs
 
@@ -130,28 +108,24 @@ separately instead of using presets to narrow the XDR set.
 
 Input: "Install the right agentme XDR presets for this Node.js library"
 - Inventory the shipped agentme XDR files
-- Analyze the repository and detect a JavaScript library with Makefiles and no existing `.specify/`
+- Analyze the repository and detect a JavaScript library with Makefiles
 - Exclude `.xdrs/agentme/edrs/application/010-golang-project-tooling.md` and `.xdrs/agentme/edrs/observability/011-service-health-check-endpoint.md`
 - Run `npx -y agentme extract --output . --all --exclude .xdrs/agentme/edrs/application/010-golang-project-tooling.md --exclude .xdrs/agentme/edrs/observability/011-service-health-check-endpoint.md`
 
-Input: "Set up agentme for this repo and keep the speckit workflow we already use"
+Input: "Set up agentme for this repo"
 - Inventory the shipped agentme XDR files
-- Detect `.specify/`, `.github/agents/`, and `.github/prompts/`
-- Choose full XDR extraction and keep `speckit`
+- Detect `.xdrs/`, `.github/agents/`, and `.github/prompts/`
+- Choose full XDR extraction
 - Exclude only the XDRs that are concretely irrelevant for the repository shape
 - Run `npx -y agentme extract --output . --all --exclude <irrelevant-xdr-path>`
-- Run `npx -y agentme extract --output . --presets speckit`
 
 ## Edge Cases
 
 - If the CLI cannot directly list the shipped XDRs, use the package's published metadata or README
    as a fallback instead of failing immediately.
-- If the repository already has `.xdrs/` but no sign of speckit, install or update only the XDR
-   set unless the user requests the workflow files.
+- If the repository already has `.xdrs/`, install or update the XDR set.
 - If a candidate exclusion is debatable, keep the XDR. The skill should exclude only records that
    clearly do not make sense for the project.
-- If the user asks specifically for XDRs, do not add `speckit` unless they also request that
-  workflow.
 - If preset extraction would overwrite locally customized agent files, warn the user and describe the
   likely merge points.
 - If the repository is a spike or intentionally minimal experiment, still prefer the smallest preset

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

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

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

@@ -1,5 +1,5 @@
 ---
-name: agentme-edr-skill-002-monorepo-setup
+name: 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/README.md

@@ -1,6 +1,6 @@
 # agentme
 
-Curated distribution package of XDRs and speckit agent workflow files for AI-assisted software development.
+Curated distribution package of XDRs and AI agent workflow files for AI-assisted software development.
 
 This collection is being updated as we develop applications and feel the need for new instructions and skills to help with AI agents.
 
@@ -8,7 +8,7 @@ For guidance on turning recurring delivery friction into reusable decision recor
 
 ## Getting Started
 
-This will extract all the features of agentme (skills, github configurations, speckit, xdrs collection):
+This will extract all the features of agentme (skills, github configurations, xdrs collection):
 
 ```sh
 npx agentme
@@ -27,7 +27,6 @@ mise exec -- pnpm exec agentme check --output . --presets basic
 agentme is published as an npm package and consumed through `filedist`-based extraction. It ships a curated set of reusable artifacts for other repositories:
 
 - XDRs in `.xdrs/agentme/` for engineering, architecture, testing, tooling, and CI/CD standards.
-- speckit agent files in `.github/`, `.specify/`, and `.vscode/` for specification-driven AI development workflows.
 
 The package is intentionally static: consumers install it as a development dependency, extract files into their own repository, and commit the generated output.
 
@@ -36,7 +35,6 @@ The package is intentionally static: consumers install it as a development depen
 | Preset | Contents |
 | --- | --- |
 | `basic` | `xdrs-core` baseline ADRs, `AGENTS.md`, and agentme XDRs |
-| `speckit` | speckit agents, prompts, templates, scripts, memory files, and VS Code settings |
 | no preset | all shipped artifacts combined |
 
 Typical consumer workflow:
@@ -68,16 +66,6 @@ This is useful when you want feature work to leave behind maintainable documenta
 - product requirements and business constraints;
 - business decisions that explain why the feature behaves the way it does.
 
-### Keep project documentation current through the speckit workflow
-
-Use the `speckit` distribution when you want the delivery workflow itself to instruct agents to maintain ADRs, EDRs, and BDRs as implementation evolves. In this model, feature development and project documentation happen together: major technical and business decisions are continuously written back into XDRs instead of being deferred to a separate documentation pass.
-
-This is useful when you want to:
-
-- keep the project decision log up to date as new features are specified and implemented;
-- have architecture, engineering, and business documentation generated in a consistent XDR format;
-- reuse the same XDR-based approach across other repositories that consume agentme.
-
 ## Development
 
 Install [Mise](https://mise.jdx.dev/getting-started.html), then bootstrap the repository through the root `Makefile`:
@@ -110,8 +98,7 @@ What these targets do:
 ├── bin/                CLI entrypoint delegated to filedist
 ├── dist/               Generated npm package tarballs
 ├── examples/           Runnable verification of consumer extraction behavior
-├── .github/            Shipped speckit agent and prompt files
-├── .specify/           Shipped speckit memory, scripts, and templates
+├── .github/            Shipped agent and prompt files
 └── .xdrs/              Shipped XDRs plus local project-only decision records
 ```
 

package/package.json

@@ -1,9 +1,9 @@
 {
   "name": "agentme",
-  "version": "0.19.0",
+  "version": "0.20.1",
   "description": "",
   "dependencies": {
-    "filedist": "^0.35.0"
+    "filedist": "^0.36.0"
   },
   "bin": "bin/filedist.js",
   "files": [
@@ -11,17 +11,13 @@
     "bin/filedist.js",
     ".filedist-package.yml",
     ".xdrs/agentme/**",
-    ".xdrs/index.md",
-    ".github/agents/speckit*",
-    ".github/prompts/speckit*",
-    ".specify/**",
-    ".vscode/settings.json"
+    ".xdrs/index.md"
   ],
   "repository": {
     "type": "git",
     "url": "https://github.com/flaviostutz/agentme.git"
   },
   "devDependencies": {
-    "xdrs-core": "^0.28.3"
+    "xdrs-core": "^0.30.1"
   }
 }

package/.github/agents/speckit.analyze.agent.md

@@ -1,184 +0,0 @@
----
-description: Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
----
-
-## User Input
-
-```text
-$ARGUMENTS
-```
-
-You **MUST** consider the user input before proceeding (if not empty).
-
-## Goal
-
-Identify inconsistencies, duplications, ambiguities, and underspecified items across the three core artifacts (`spec.md`, `plan.md`, `tasks.md`) before implementation. This command MUST run only after `/speckit.tasks` has successfully produced a complete `tasks.md`.
-
-## Operating Constraints
-
-**STRICTLY READ-ONLY**: Do **not** modify any files. Output a structured analysis report. Offer an optional remediation plan (user must explicitly approve before any follow-up editing commands would be invoked manually).
-
-**Constitution Authority**: The project constitution (`.specify/memory/constitution.md`) is **non-negotiable** within this analysis scope. Constitution conflicts are automatically CRITICAL and require adjustment of the spec, plan, or tasks—not dilution, reinterpretation, or silent ignoring of the principle. If a principle itself needs to change, that must occur in a separate, explicit constitution update outside `/speckit.analyze`.
-
-## Execution Steps
-
-### 1. Initialize Analysis Context
-
-Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` once from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Derive absolute paths:
-
-- SPEC = FEATURE_DIR/spec.md
-- PLAN = FEATURE_DIR/plan.md
-- TASKS = FEATURE_DIR/tasks.md
-
-Abort with an error message if any required file is missing (instruct the user to run missing prerequisite command).
-For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
-
-### 2. Load Artifacts (Progressive Disclosure)
-
-Load only the minimal necessary context from each artifact:
-
-**From spec.md:**
-
-- Overview/Context
-- Functional Requirements
-- Non-Functional Requirements
-- User Stories
-- Edge Cases (if present)
-
-**From plan.md:**
-
-- Architecture/stack choices
-- Data Model references
-- Phases
-- Technical constraints
-
-**From tasks.md:**
-
-- Task IDs
-- Descriptions
-- Phase grouping
-- Parallel markers [P]
-- Referenced file paths
-
-**From constitution:**
-
-- Load `.specify/memory/constitution.md` for principle validation
-
-### 3. Build Semantic Models
-
-Create internal representations (do not include raw artifacts in output):
-
-- **Requirements inventory**: Each functional + non-functional requirement with a stable key (derive slug based on imperative phrase; e.g., "User can upload file" → `user-can-upload-file`)
-- **User story/action inventory**: Discrete user actions with acceptance criteria
-- **Task coverage mapping**: Map each task to one or more requirements or stories (inference by keyword / explicit reference patterns like IDs or key phrases)
-- **Constitution rule set**: Extract principle names and MUST/SHOULD normative statements
-
-### 4. Detection Passes (Token-Efficient Analysis)
-
-Focus on high-signal findings. Limit to 50 findings total; aggregate remainder in overflow summary.
-
-#### A. Duplication Detection
-
-- Identify near-duplicate requirements
-- Mark lower-quality phrasing for consolidation
-
-#### B. Ambiguity Detection
-
-- Flag vague adjectives (fast, scalable, secure, intuitive, robust) lacking measurable criteria
-- Flag unresolved placeholders (TODO, TKTK, ???, `<placeholder>`, etc.)
-
-#### C. Underspecification
-
-- Requirements with verbs but missing object or measurable outcome
-- User stories missing acceptance criteria alignment
-- Tasks referencing files or components not defined in spec/plan
-
-#### D. Constitution Alignment
-
-- Any requirement or plan element conflicting with a MUST principle
-- Missing mandated sections or quality gates from constitution
-
-#### E. Coverage Gaps
-
-- Requirements with zero associated tasks
-- Tasks with no mapped requirement/story
-- Non-functional requirements not reflected in tasks (e.g., performance, security)
-
-#### F. Inconsistency
-
-- Terminology drift (same concept named differently across files)
-- Data entities referenced in plan but absent in spec (or vice versa)
-- Task ordering contradictions (e.g., integration tasks before foundational setup tasks without dependency note)
-- Conflicting requirements (e.g., one requires Next.js while other specifies Vue)
-
-### 5. Severity Assignment
-
-Use this heuristic to prioritize findings:
-
-- **CRITICAL**: Violates constitution MUST, missing core spec artifact, or requirement with zero coverage that blocks baseline functionality
-- **HIGH**: Duplicate or conflicting requirement, ambiguous security/performance attribute, untestable acceptance criterion
-- **MEDIUM**: Terminology drift, missing non-functional task coverage, underspecified edge case
-- **LOW**: Style/wording improvements, minor redundancy not affecting execution order
-
-### 6. Produce Compact Analysis Report
-
-Output a Markdown report (no file writes) with the following structure:
-
-## Specification Analysis Report
-
-| ID | Category | Severity | Location(s) | Summary | Recommendation |
-|----|----------|----------|-------------|---------|----------------|
-| A1 | Duplication | HIGH | spec.md:L120-134 | Two similar requirements ... | Merge phrasing; keep clearer version |
-
-(Add one row per finding; generate stable IDs prefixed by category initial.)
-
-**Coverage Summary Table:**
-
-| Requirement Key | Has Task? | Task IDs | Notes |
-|-----------------|-----------|----------|-------|
-
-**Constitution Alignment Issues:** (if any)
-
-**Unmapped Tasks:** (if any)
-
-**Metrics:**
-
-- Total Requirements
-- Total Tasks
-- Coverage % (requirements with >=1 task)
-- Ambiguity Count
-- Duplication Count
-- Critical Issues Count
-
-### 7. Provide Next Actions
-
-At end of report, output a concise Next Actions block:
-
-- If CRITICAL issues exist: Recommend resolving before `/speckit.implement`
-- If only LOW/MEDIUM: User may proceed, but provide improvement suggestions
-- Provide explicit command suggestions: e.g., "Run /speckit.specify with refinement", "Run /speckit.plan to adjust architecture", "Manually edit tasks.md to add coverage for 'performance-metrics'"
-
-### 8. Offer Remediation
-
-Ask the user: "Would you like me to suggest concrete remediation edits for the top N issues?" (Do NOT apply them automatically.)
-
-## Operating Principles
-
-### Context Efficiency
-
-- **Minimal high-signal tokens**: Focus on actionable findings, not exhaustive documentation
-- **Progressive disclosure**: Load artifacts incrementally; don't dump all content into analysis
-- **Token-efficient output**: Limit findings table to 50 rows; summarize overflow
-- **Deterministic results**: Rerunning without changes should produce consistent IDs and counts
-
-### Analysis Guidelines
-
-- **NEVER modify files** (this is read-only analysis)
-- **NEVER hallucinate missing sections** (if absent, report them accurately)
-- **Prioritize constitution violations** (these are always CRITICAL)
-- **Use examples over exhaustive rules** (cite specific instances, not generic patterns)
-- **Report zero issues gracefully** (emit success report with coverage statistics)
-
-## Context
-
-$ARGUMENTS