@howlil/ez-agents 3.5.0 → 4.0.0

package/commands/ez/package-manager.md

@@ -1,316 +0,0 @@
-# Package Manager Command
-
-## Overview
-
-The `package-manager` command provides flexible package manager support for ez-agents, enabling seamless operation with **npm**, **yarn**, and **pnpm**. It automatically detects available package managers, respects existing lockfiles, and provides configuration-driven defaults for consistent team workflows.
-
-### Features
-
-- **Auto-Detection**: Intelligently detects available package managers (pnpm, yarn, npm) on the system
-- **Lockfile Respect**: Honors existing lockfiles (package-lock.json, yarn.lock, pnpm-lock.yaml)
-- **Configuration Control**: Configurable default package manager in `.planning/config.json`
-- **Cross-Platform Execution**: Consistent shell syntax across Windows, macOS, and Linux
-- **Full Command Support**: install, add, remove operations for all three package managers
-- **Backward Compatibility**: Maintains existing npm compatibility for legacy projects
-
-## Usage
-
-```bash
-ez package-manager <subcommand> [options]
-```
-
-### Subcommands
-
-#### `detect` - Detect available package manager
-
-Automatically detects the available package manager using a priority-based strategy.
-
-```bash
-ez package-manager detect
-```
-
-**Output format (JSON):**
-```json
-{
-  "manager": "pnpm",
-  "source": "lockfile",
-  "confidence": "high",
-  "lockfilePath": "/path/to/pnpm-lock.yaml"
-}
-```
-
-**Detection Sources:**
-- `config` - From `.planning/config.json` packageManager.default
-- `lockfile` - From existing lockfile presence
-- `system` - From system availability check
-- `fallback` - Default to npm when nothing else is available
-
-**Confidence Levels:**
-- `high` - Config or lockfile detection
-- `medium` - System availability detection
-- `low` - Fallback to npm
-
----
-
-#### `install` - Install dependencies
-
-Install dependencies from lockfile.
-
-```bash
-ez package-manager install [--frozen] [--production]
-```
-
-**Options:**
-- `--frozen` - Use frozen lockfile install (CI/CD safe)
-- `--production` - Production install (exclude devDependencies)
-
-**Examples:**
-```bash
-# Standard install
-ez package-manager install
-
-# Frozen lockfile install (CI/CD)
-ez package-manager install --frozen
-
-# Production install
-ez package-manager install --production
-```
-
-**Package Manager Commands:**
-- npm: `npm install [--frozen-lockfile] [--production]`
-- yarn: `yarn install [--frozen-lockfile] [--production]`
-- pnpm: `pnpm install [--frozen-lockfile] [--prod]`
-
----
-
-#### `add` - Add package(s)
-
-Add new package(s) to the project.
-
-```bash
-ez package-manager add <package> [--dev|-D]
-```
-
-**Options:**
-- `--dev` or `-D` - Add as devDependency
-
-**Examples:**
-```bash
-# Add production dependency
-ez package-manager add lodash
-
-# Add dev dependency
-ez package-manager add eslint --dev
-ez package-manager add prettier -D
-
-# Add multiple packages
-ez package-manager add react react-dom
-```
-
-**Package Manager Commands:**
-- npm: `npm install [--save-dev] <package>`
-- yarn: `yarn add [--dev] <package>`
-- pnpm: `pnpm add [--save-dev] <package>`
-
----
-
-#### `remove` - Remove package(s)
-
-Remove package(s) from the project.
-
-```bash
-ez package-manager remove <package>
-```
-
-**Examples:**
-```bash
-# Remove single package
-ez package-manager remove lodash
-
-# Remove multiple packages
-ez package-manager remove eslint prettier
-```
-
-**Package Manager Commands:**
-- npm: `npm uninstall <package>`
-- yarn: `yarn remove <package>`
-- pnpm: `pnpm remove <package>`
-
----
-
-#### `info` - Show package manager info
-
-Display current package manager information.
-
-```bash
-ez package-manager info
-```
-
-**Output format (JSON):**
-```json
-{
-  "manager": "pnpm",
-  "source": "lockfile",
-  "cwd": "/path/to/project",
-  "lockfile": "/path/to/pnpm-lock.yaml"
-}
-```
-
----
-
-## Configuration
-
-Configure package manager behavior in `.planning/config.json`:
-
-```json
-{
-  "packageManager": {
-    "default": "npm",
-    "autoDetect": true,
-    "respectLockfile": true,
-    "frozenLockfileInCI": true
-  }
-}
-```
-
-### Configuration Options
-
-| Option | Type | Default | Description |
-|--------|------|---------|-------------|
-| `default` | string | `"npm"` | Default package manager (`npm`, `yarn`, or `pnpm`) |
-| `autoDetect` | boolean | `true` | Enable automatic package manager detection |
-| `respectLockfile` | boolean | `true` | Respect existing lockfiles when detecting |
-| `frozenLockfileInCI` | boolean | `true` | Use frozen lockfile installs in CI environments |
-
----
-
-## Detection Priority
-
-The package manager detection follows a priority-based strategy:
-
-```
-┌─────────────────────────────────────────────────────────────┐
-│              Package Manager Detection Pipeline              │
-├─────────────────────────────────────────────────────────────┤
-│  Layer 1: Configuration (highest priority)                  │
-│  - Check .planning/config.json → packageManager.default    │
-│  - If found and installed, use configured manager           │
-├─────────────────────────────────────────────────────────────┤
-│  Layer 2: Lockfile Detection                                │
-│  - Check for pnpm-lock.yaml → use pnpm                     │
-│  - Check for yarn.lock → use yarn                          │
-│  - Check for package-lock.json → use npm                   │
-├─────────────────────────────────────────────────────────────┤
-│  Layer 3: System Availability                               │
-│  - Check which managers are installed                       │
-│  - Prefer pnpm > yarn > npm (performance order)            │
-├─────────────────────────────────────────────────────────────┤
-│  Layer 4: Fallback                                          │
-│  - Default to npm (always available with Node)             │
-└─────────────────────────────────────────────────────────────┘
-```
-
-### Detection Examples
-
-| Scenario | Detected Manager | Source |
-|----------|-----------------|--------|
-| Config says `pnpm`, pnpm installed | `pnpm` | config |
-| No config, `pnpm-lock.yaml` exists | `pnpm` | lockfile |
-| No config, `yarn.lock` exists | `yarn` | lockfile |
-| No config, `package-lock.json` exists | `npm` | lockfile |
-| No lockfile, pnpm/yarn/npm installed | `pnpm` | system |
-| No lockfile, only npm installed | `npm` | system |
-| Nothing detected | `npm` | fallback |
-
----
-
-## Cross-Platform Support
-
-The package manager command works identically across all platforms:
-
-- **Windows** - Uses `execFile` for cross-platform execution
-- **macOS** - Native Unix shell compatibility
-- **Linux** - Native Unix shell compatibility
-
-### Implementation Details
-
-- All commands use `execFile` (not `exec`) for security and cross-platform compatibility
-- All paths use `path.join()` for proper path separator handling
-- No shell injection vulnerabilities (shell: false)
-- 5-minute timeout for all operations
-- 10MB buffer for command output
-
----
-
-## Package Manager Commands Reference
-
-### npm
-
-| Operation | Command |
-|-----------|---------|
-| Install | `npm install` |
-| Frozen Install | `npm install --frozen-lockfile` |
-| Add Package | `npm install <pkg>` |
-| Add Dev Package | `npm install --save-dev <pkg>` |
-| Remove Package | `npm uninstall <pkg>` |
-| Lockfile | `package-lock.json` |
-
-### yarn
-
-| Operation | Command |
-|-----------|---------|
-| Install | `yarn install` |
-| Frozen Install | `yarn install --frozen-lockfile` |
-| Add Package | `yarn add <pkg>` |
-| Add Dev Package | `yarn add --dev <pkg>` |
-| Remove Package | `yarn remove <pkg>` |
-| Lockfile | `yarn.lock` |
-
-### pnpm
-
-| Operation | Command |
-|-----------|---------|
-| Install | `pnpm install` |
-| Frozen Install | `pnpm install --frozen-lockfile` |
-| Add Package | `pnpm add <pkg>` |
-| Add Dev Package | `pnpm add --save-dev <pkg>` |
-| Remove Package | `pnpm remove <pkg>` |
-| Lockfile | `pnpm-lock.yaml` |
-
----
-
-## Error Handling
-
-The command provides detailed error messages for common issues:
-
-- **No package manager detected** - Falls back to npm with warning
-- **Lockfile validation failed** - Logs warning but continues
-- **Command execution failed** - Returns stderr output with context
-- **Unknown subcommand** - Lists available subcommands
-
----
-
-## Library API
-
-The package manager modules are also available for programmatic use:
-
-```javascript
-const {
-  PackageManagerService,
-  PackageManagerDetector,
-  PackageManagerExecutor,
-  LockfileValidator
-} = require('./ez-agents/bin/lib/index.cjs');
-
-// Use the service
-const service = new PackageManagerService(cwd);
-await service.initialize();
-await service.install({ frozenLockfile: true });
-await service.add(['lodash'], { dev: true });
-```
-
-See individual module files for detailed API documentation:
-- `ez-agents/bin/lib/package-manager-detector.cjs`
-- `ez-agents/bin/lib/package-manager-executor.cjs`
-- `ez-agents/bin/lib/lockfile-validator.cjs`
-- `ez-agents/bin/lib/package-manager-service.cjs`

package/commands/ez/pause-work.md

@@ -1,38 +0,0 @@
----
-name: ez:pause-work
-description: Create context handoff when pausing work mid-phase
-allowed-tools:
-  - Read
-  - Write
-  - Bash
----
-
-<objective>
-Create `.continue-here.md` handoff file to preserve complete work state across sessions.
-
-Routes to the pause-work workflow which handles:
-- Current phase detection from recent files
-- Complete state gathering (position, completed work, remaining work, decisions, blockers)
-- Handoff file creation with all context sections
-- Git commit as WIP
-- Resume instructions
-</objective>
-
-<execution_context>
-@~/.claude/ez-agents/workflows/pause-work.md
-</execution_context>
-
-<context>
-State and phase progress are gathered in-workflow with targeted reads.
-</context>
-
-<process>
-**Follow the pause-work workflow** from `@~/.claude/ez-agents/workflows/pause-work.md`.
-
-The workflow handles all logic including:
-1. Phase directory detection
-2. State gathering with user clarifications
-3. Handoff file writing with timestamp
-4. Git commit
-5. Confirmation with resume instructions
-</process>

package/commands/ez/plan-milestone-gaps.md

@@ -1,34 +0,0 @@
----
-name: ez:plan-milestone-gaps
-description: Create phases to close all gaps identified by milestone audit
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
-  - Grep
-  - AskUserQuestion
----
-<objective>
-Create all phases necessary to close gaps identified by `/ez:audit-milestone`.
-
-Reads MILESTONE-AUDIT.md, groups gaps into logical phases, creates phase entries in ROADMAP.md, and offers to plan each phase.
-
-One command creates all fix phases — no manual `/ez:add-phase` per gap.
-</objective>
-
-<execution_context>
-@~/.claude/ez-agents/workflows/plan-milestone-gaps.md
-</execution_context>
-
-<context>
-**Audit results:**
-Glob: .planning/v*-MILESTONE-AUDIT.md (use most recent)
-
-Original intent and current planning state are loaded on demand inside the workflow.
-</context>
-
-<process>
-Execute the plan-milestone-gaps workflow from @~/.claude/ez-agents/workflows/plan-milestone-gaps.md end-to-end.
-Preserve all workflow gates (audit loading, prioritization, phase grouping, user confirmation, roadmap updates).
-</process>

package/commands/ez/preflight.md

@@ -1,79 +0,0 @@
----
-name: preflight
-description: Run release checklist validation without creating a release. Shows pass/fail for all tier checklist items.
-usage: /ez:release preflight <tier>
----
-
-# /ez:release preflight
-
-Run the release checklist for a tier without creating a branch, tag, or changelog. Use this to see what's blocking or passing before you commit to a release.
-
-## Usage
-
-```
-/ez:release preflight <tier>
-```
-
-## Arguments
-
-| Argument | Required | Description |
-|----------|----------|-------------|
-| `tier` | Yes | `mvp`, `medium`, or `enterprise` |
-
-## What It Checks
-
-Runs security gates + tier checklist without side effects:
-
-```
-/ez:release preflight medium
-
-Security Gates (4/4):
-  ✓ No secrets in committed files
-  ✓ npm audit — no critical vulnerabilities
-  ✓ No production TODOs
-  ✓ .env files in .gitignore
-
-Medium Checklist (12/18):
-  ✓ All @must BDD scenarios passing
-  ✗ Test coverage ≥ 80% — Coverage: 71% (need 9% more)
-  ✓ npm audit — clean
-  ✓ No secrets in committed files
-  ✓ Application starts
-  ✓ Rollback documented
-  ✓ All @should BDD scenarios passing
-  ✗ Test coverage ≥ 80% — 71% (need +9%)
-  ? Staging environment parity — requires manual verification
-  ? Monitoring/alerts configured — requires manual verification
-  ✓ No console.log in prod
-  ? Performance baseline — requires manual verification
-  ...
-
-Production Readiness Score: 74/100 — CONDITIONAL
-
-Blockers: 0
-Warnings: 2 (coverage below threshold)
-Manual items: 6 (need human verification)
-
-To release: /ez:release medium v1.5.0
-```
-
-## When to Use
-
-- Before starting a release to know what you need to fix
-- When onboarding to a new tier to understand the gap
-- During development to track progress toward release readiness
-
-## Legend
-
-| Symbol | Meaning |
-|--------|---------|
-| ✓ | Automated check passed |
-| ✗ | Automated check failed |
-| ? | Requires manual human verification |
-| ○ | Skipped (not applicable) |
-
-## Related Commands
-
-- `/ez:release mvp v1.0.0` — Execute the actual release
-- `/ez:hotfix` — Emergency fix on released version
-- `/ez:standup` — Sprint health check

package/commands/ez/reapply-patches.md

@@ -1,124 +0,0 @@
----
-name: ez:reapply-patches
-description: Reapply local modifications after an EZ Agents update
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
----
-
-<purpose>
-After an EZ Agents update wipes and reinstalls files, this command merges user's previously saved local modifications back into the new version. Uses intelligent comparison to handle cases where the upstream file also changed.
-</purpose>
-
-<process>
-
-## Step 1: Detect backed-up patches
-
-Check for local patches directory:
-
-```bash
-# Global install — detect runtime config directory
-if [ -d "$HOME/.config/opencode/ez-local-patches" ]; then
-  PATCHES_DIR="$HOME/.config/opencode/ez-local-patches"
-elif [ -d "$HOME/.opencode/ez-local-patches" ]; then
-  PATCHES_DIR="$HOME/.opencode/ez-local-patches"
-elif [ -d "$HOME/.gemini/ez-local-patches" ]; then
-  PATCHES_DIR="$HOME/.gemini/ez-local-patches"
-else
-  PATCHES_DIR="$HOME/.claude/ez-local-patches"
-fi
-# Local install fallback — check all runtime directories
-if [ ! -d "$PATCHES_DIR" ]; then
-  for dir in .config/opencode .opencode .gemini .claude; do
-    if [ -d "./$dir/ez-local-patches" ]; then
-      PATCHES_DIR="./$dir/ez-local-patches"
-      break
-    fi
-  done
-fi
-```
-
-Read `backup-meta.json` from the patches directory.
-
-**If no patches found:**
-```
-No local patches found. Nothing to reapply.
-
-Local patches are automatically saved when you run /ez:update
-after modifying any EZ Agents workflow, command, or agent files.
-```
-Exit.
-
-## Step 2: Show patch summary
-
-```
-## Local Patches to Reapply
-
-**Backed up from:** v{from_version}
-**Current version:** {read VERSION file}
-**Files modified:** {count}
-
-| # | File | Status |
-|---|------|--------|
-| 1 | {file_path} | Pending |
-| 2 | {file_path} | Pending |
-```
-
-## Step 3: Merge each file
-
-For each file in `backup-meta.json`:
-
-1. **Read the backed-up version** (user's modified copy from `ez-local-patches/`)
-2. **Read the newly installed version** (current file after update)
-3. **Compare and merge:**
-
-   - If the new file is identical to the backed-up file: skip (modification was incorporated upstream)
-   - If the new file differs: identify the user's modifications and apply them to the new version
-
-   **Merge strategy:**
-   - Read both versions fully
-   - Identify sections the user added or modified (look for additions, not just differences from path replacement)
-   - Apply user's additions/modifications to the new version
-   - If a section the user modified was also changed upstream: flag as conflict, show both versions, ask user which to keep
-
-4. **Write merged result** to the installed location
-5. **Report status:**
-   - `Merged` — user modifications applied cleanly
-   - `Skipped` — modification already in upstream
-   - `Conflict` — user chose resolution
-
-## Step 4: Update manifest
-
-After reapplying, regenerate the file manifest so future updates correctly detect these as user modifications:
-
-```bash
-# The manifest will be regenerated on next /ez:update
-# For now, just note which files were modified
-```
-
-## Step 5: Cleanup option
-
-Ask user:
-- "Keep patch backups for reference?" → preserve `ez-local-patches/`
-- "Clean up patch backups?" → remove `ez-local-patches/` directory
-
-## Step 6: Report
-
-```
-## Patches Reapplied
-
-| # | File | Status |
-|---|------|--------|
-| 1 | {file_path} | ✓ Merged |
-| 2 | {file_path} | ○ Skipped (already upstream) |
-| 3 | {file_path} | ⚠ Conflict resolved |
-
-{count} file(s) updated. Your local modifications are active again.
-```
-
-</process>
-
-<success_criteria>
-- [ ] All backed-up patches processed
-- [ ] User modifications merged into new version
-- [ ] Conflicts resolved with user input
-- [ ] Status reported for each file
-</success_criteria>