@harness-engineering/cli 1.1.0 → 1.2.0

package/dist/index.d.ts

@@ -39,6 +39,74 @@ declare class CLIError extends Error {
  */
 declare function handleError(error: unknown): never;
 
+interface CheckPhaseGateOptions {
+    cwd?: string;
+    configPath?: string;
+    json?: boolean;
+    verbose?: boolean;
+    quiet?: boolean;
+}
+interface CheckPhaseGateResult {
+    pass: boolean;
+    skipped: boolean;
+    severity?: 'error' | 'warning';
+    missingSpecs: Array<{
+        implFile: string;
+        expectedSpec: string;
+    }>;
+    checkedFiles: number;
+}
+declare function runCheckPhaseGate(options: CheckPhaseGateOptions): Promise<Result<CheckPhaseGateResult, CLIError>>;
+
+interface CrossCheckResult {
+    specToPlan: string[];
+    planToImpl: string[];
+    staleness: string[];
+    warnings: number;
+}
+interface CrossCheckOptions {
+    specsDir: string;
+    plansDir: string;
+    projectPath: string;
+}
+declare function runCrossCheck(options: CrossCheckOptions): Promise<Result<CrossCheckResult, CLIError>>;
+
+interface CreateSkillOptions {
+    name: string;
+    description: string;
+    cognitiveMode?: string;
+    reads?: string[];
+    produces?: string;
+    preChecks?: string[];
+    postChecks?: string[];
+    outputDir?: string;
+}
+interface GeneratedFiles {
+    skillYamlPath: string;
+    skillMdPath: string;
+}
+declare function generateSkillFiles(opts: CreateSkillOptions): GeneratedFiles;
+
+type Platform = 'claude-code' | 'gemini-cli';
+interface GenerateOptions {
+    platforms: Platform[];
+    global: boolean;
+    output?: string;
+    skillsDir: string;
+    dryRun: boolean;
+    yes: boolean;
+}
+
+interface GenerateResult {
+    platform: string;
+    added: string[];
+    updated: string[];
+    removed: string[];
+    unchanged: string[];
+    outputDir: string;
+}
+declare function generateSlashCommands(opts: GenerateOptions): GenerateResult[];
+
 declare const OutputMode: {
     readonly JSON: "json";
     readonly TEXT: "text";
@@ -540,4 +608,4 @@ declare function runPersona(persona: Persona, executor: CommandExecutor): Promis
 
 declare function createProgram(): Command;
 
-export { CLIError, type CommandExecutor, ExitCode, type HarnessConfig, OutputFormatter, OutputMode, type Persona, type PersonaMetadata, type PersonaRunReport, type RenderedFiles, type TemplateContext, TemplateEngine, buildPreamble, createProgram, findConfigFile, generateAgentsMd, generateCIWorkflow, generateRuntime, handleError, listPersonas, loadConfig, loadPersona, logger, resolveConfig, runPersona };
+export { CLIError, type CommandExecutor, type CreateSkillOptions, ExitCode, type GenerateResult, type HarnessConfig, OutputFormatter, OutputMode, type Persona, type PersonaMetadata, type PersonaRunReport, type RenderedFiles, type TemplateContext, TemplateEngine, buildPreamble, createProgram, findConfigFile, generateAgentsMd, generateCIWorkflow, generateRuntime, generateSkillFiles, generateSlashCommands, handleError, listPersonas, loadConfig, loadPersona, logger, resolveConfig, runCheckPhaseGate, runCrossCheck, runPersona };

package/dist/index.js

@@ -8,15 +8,21 @@ import {
   generateAgentsMd,
   generateCIWorkflow,
   generateRuntime,
+  generateSlashCommands,
   listPersonas,
   loadConfig,
   loadPersona,
   resolveConfig,
+  runCheckPhaseGate,
   runPersona
-} from "./chunk-JR7ZYYNL.js";
+} from "./chunk-IXT3KLVN.js";
+import {
+  runCrossCheck
+} from "./chunk-3U5VZYR7.js";
 import {
   CLIError,
   ExitCode,
+  generateSkillFiles,
   handleError,
   logger
 } from "./chunk-EFZOLZFB.js";
@@ -32,11 +38,15 @@ export {
   generateAgentsMd,
   generateCIWorkflow,
   generateRuntime,
+  generateSkillFiles,
+  generateSlashCommands,
   handleError,
   listPersonas,
   loadConfig,
   loadPersona,
   logger,
   resolveConfig,
+  runCheckPhaseGate,
+  runCrossCheck,
   runPersona
 };

package/dist/validate-cross-check-LNIZ7KGZ.js

@@ -0,0 +1,6 @@
+import {
+  runCrossCheck
+} from "./chunk-3U5VZYR7.js";
+export {
+  runCrossCheck
+};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@harness-engineering/cli",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "CLI for Harness Engineering toolkit",
   "type": "module",
   "bin": {

package/dist/agents/agents/personas/architecture-enforcer.yaml

@@ -1,27 +0,0 @@
-version: 1
-name: Architecture Enforcer
-description: Validates architectural constraints and dependency rules
-role: Enforce layer boundaries, detect circular dependencies, block forbidden imports
-skills:
-  - enforce-architecture
-  - check-mechanical-constraints
-commands:
-  - check-deps
-  - validate
-triggers:
-  - event: on_pr
-    conditions:
-      paths: ["src/**"]
-  - event: on_commit
-    conditions:
-      branches: ["main", "develop"]
-  - event: scheduled
-    cron: "0 6 * * 1"
-config:
-  severity: error
-  autoFix: false
-  timeout: 300000
-outputs:
-  agents-md: true
-  ci-workflow: true
-  runtime-config: true

package/dist/agents/agents/personas/documentation-maintainer.yaml

@@ -1,25 +0,0 @@
-version: 1
-name: Documentation Maintainer
-description: Keeps documentation in sync with source code
-role: Detect documentation drift, validate doc coverage, align docs with code changes
-skills:
-  - detect-doc-drift
-  - align-documentation
-commands:
-  - check-docs
-  - validate
-triggers:
-  - event: on_pr
-    conditions:
-      paths: ["src/**", "docs/**"]
-  - event: on_commit
-    conditions:
-      branches: ["main"]
-config:
-  severity: warning
-  autoFix: false
-  timeout: 300000
-outputs:
-  agents-md: true
-  ci-workflow: true
-  runtime-config: true

package/dist/agents/agents/personas/entropy-cleaner.yaml

@@ -1,21 +0,0 @@
-version: 1
-name: Entropy Cleaner
-description: Detects and fixes codebase entropy (drift, dead code, pattern violations)
-role: Run scheduled cleanup, detect documentation drift, fix pattern violations
-skills:
-  - cleanup-dead-code
-  - detect-doc-drift
-commands:
-  - cleanup
-  - fix-drift
-triggers:
-  - event: scheduled
-    cron: "0 6 * * 1"
-config:
-  severity: warning
-  autoFix: false
-  timeout: 600000
-outputs:
-  agents-md: true
-  ci-workflow: true
-  runtime-config: true

package/dist/agents/agents/skills/.turbo/turbo-test.log

@@ -1,16 +0,0 @@
-
-> @harness-engineering/skills@1.0.0 test /Users/cwarner/Projects/harness-engineering/agents/skills
-> vitest
-
-
- RUN  v4.0.18 /Users/cwarner/Projects/harness-engineering/agents/skills
-
- ✓ tests/schema.test.ts (10 tests) 5ms
- ✓ tests/structure.test.ts (91 tests) 10ms
- ✓ tests/references.test.ts (48 tests) 41ms
-
- Test Files  3 passed (3)
-      Tests  149 passed (149)
-   Start at  12:08:55
-   Duration  572ms (transform 58ms, setup 0ms, import 443ms, tests 56ms, environment 0ms)
-

package/dist/agents/agents/skills/README.md

@@ -1,64 +0,0 @@
-# Harness Engineering Agent Skills
-
-Agent skills for Claude Code and Gemini CLI that implement harness engineering practices.
-
-## Structure
-
-```
-agents/skills/
-├── shared/           # Shared prompt fragments
-├── claude-code/      # Claude Code skills
-├── gemini-cli/       # Gemini CLI skills
-└── tests/            # Validation tests
-```
-
-## Available Skills
-
-### Enforcement
-
-- `validate-context-engineering` - Validate AGENTS.md, doc coverage, knowledge map
-- `enforce-architecture` - Check layer boundaries and circular deps
-- `check-mechanical-constraints` - Run all mechanical checks
-
-### Workflow
-
-- `harness-tdd` - Test-driven development guidance
-- `harness-code-review` - Structured code review
-- `harness-refactoring` - Safe refactoring process
-
-### Entropy
-
-- `detect-doc-drift` - Find stale documentation
-- `cleanup-dead-code` - Find unused code
-- `align-documentation` - Auto-fix doc drift
-
-### Setup
-
-- `initialize-harness-project` - Scaffold new project
-- `add-harness-component` - Add components
-
-## Usage
-
-### Claude Code
-
-```
-/validate-context-engineering
-```
-
-### Gemini CLI
-
-```
-@validate-context-engineering
-```
-
-## Testing
-
-```bash
-pnpm test
-```
-
-## Adding New Skills
-
-1. Create directory under `claude-code/` and `gemini-cli/`
-2. Add `skill.yaml`, `prompt.md`, `README.md`
-3. Run tests to validate

package/dist/agents/agents/skills/claude-code/add-harness-component/skill.yaml

@@ -1,32 +0,0 @@
-name: add-harness-component
-version: "1.0.0"
-description: Add a component to an existing harness project
-cognitive_mode: constructive-architect
-triggers:
-  - manual
-platforms:
-  - claude-code
-  - gemini-cli
-tools:
-  - Bash
-  - Read
-  - Write
-  - Edit
-  - Glob
-cli:
-  command: harness skill run add-harness-component
-  args:
-    - name: path
-      description: Project root path
-      required: false
-mcp:
-  tool: run_skill
-  input:
-    skill: add-harness-component
-    path: string
-type: flexible
-state:
-  persistent: false
-  files: []
-depends_on:
-  - initialize-harness-project

package/dist/agents/agents/skills/claude-code/align-documentation/SKILL.md

@@ -1,181 +0,0 @@
-# Align Documentation
-
-> Sync documentation with code after implementation changes. Keep AGENTS.md, API docs, and architecture docs accurate by mapping code changes to their documentation impact.
-
-## When to Use
-
-- After completing a feature implementation (post-merge or post-commit)
-- After fixing a bug that changes observable behavior
-- After a refactoring that renames, moves, or restructures code
-- When detect-doc-drift reports findings that need fixing
-- When `on_post_feature` or `on_post_merge` triggers fire
-- NOT during active development — wait until the code is stable
-- NOT for creating documentation for a brand-new project (use validate-context-engineering for initial setup)
-- NOT for fixing code — this skill only changes documentation
-
-## Process
-
-### Phase 1: Detect — Identify What Changed
-
-1. **Run `git diff` against the appropriate baseline.** Choose the baseline based on context:
-   - After a feature: diff against the branch point (`git diff main...HEAD`)
-   - After a bug fix: diff against the commit before the fix
-   - After a refactoring: diff against the commit before refactoring started
-   - Periodic sync: diff against the last documentation sync commit
-
-2. **Extract the list of changed files.** For each changed file, note:
-   - File path (current and previous if renamed/moved)
-   - Nature of change (added, modified, deleted, renamed)
-   - Changed exports (new, removed, renamed, signature changed)
-   - Changed behavior (different return values, new error types, new side effects)
-
-3. **Run `harness check-docs`** to identify any documentation that already has broken references due to the changes.
-
-### Phase 2: Map — Connect Code Changes to Documentation
-
-For each changed file, identify all documentation that references it:
-
-**AGENTS.md sections:**
-
-- Knowledge map entries that reference the file path
-- Architecture descriptions that mention the module
-- Constraint documentation that references the file's layer or patterns
-- Onboarding guides that walk through the file
-
-**API documentation:**
-
-- JSDoc/TSDoc comments in the changed files themselves
-- Generated API doc pages that pull from the changed files
-- README examples that demonstrate the changed functions
-- Tutorial or guide pages that use the changed code
-
-**Architecture documentation:**
-
-- Diagrams that include the changed module
-- Data flow descriptions that reference the changed functions
-- Layer descriptions that list the changed file
-- Dependency documentation that references the changed imports
-
-**Inline code comments:**
-
-- Comments in OTHER files that reference the changed file or function
-- TODO comments that reference the changed behavior
-- Workaround comments that may no longer apply after the change
-
-### Phase 3: Generate — Draft Documentation Updates
-
-For each affected documentation location:
-
-1. **Draft the specific text change.** Show the old text and the new text. Keep the existing style and tone — documentation updates should be invisible in terms of voice.
-
-2. **Preserve context.** When updating a section, do not just change the specific reference — read the surrounding paragraph and ensure it still makes sense. A renamed function may require updating the explanatory text around it, not just the function name.
-
-3. **Handle deletions carefully.** When code is deleted, do not just delete the documentation reference. Consider whether the section should be removed entirely, replaced with information about the replacement, or noted as deprecated.
-
-4. **Add new sections when needed.** If a new module was added, draft a complete documentation section following the existing AGENTS.md structure and style.
-
-### Phase 4: Validate — Verify Documentation Accuracy
-
-1. **Run `harness check-docs`** to verify all links and references resolve correctly after the updates.
-
-2. **Cross-check each update against the actual code.** Read the updated documentation and verify every claim by looking at the code. Documentation that is wrong is worse than documentation that is missing.
-
-3. **Verify no orphaned references remain.** Search documentation files for any remaining references to old names, old paths, or deleted features.
-
-4. **Run `harness fix-drift`** to catch any remaining simple drift issues that manual review missed.
-
-5. **Commit the documentation update.** Use a commit message that references the original change: "docs: update AGENTS.md for notification service refactoring" or "docs: sync API docs after auth module rename."
-
-## What to Update
-
-### AGENTS.md Knowledge Map
-
-- File paths and module names (renamed or moved files)
-- Module purpose descriptions (changed responsibilities)
-- Constraint descriptions (new or changed rules)
-- Relationship descriptions (new or changed dependencies)
-- Gotcha sections (resolved gotchas, new gotchas)
-
-### Inline Code Comments
-
-- Function/class doc comments in the changed files (JSDoc, TSDoc)
-- Comments in other files that reference the changed code
-- TODO comments that reference completed or changed work
-- Workaround comments for issues that may now be resolved
-
-### Documentation Pages (docs/)
-
-- API reference pages that describe changed functions
-- Architecture pages that diagram changed modules
-- Tutorial and guide pages that demonstrate changed code
-- Getting-started guides if entry points changed
-- Changelog entries for user-facing changes
-
-## Harness Integration
-
-- **`harness check-docs`** — Run before and after updates. Identifies broken references and validates that all documentation links resolve.
-- **`harness fix-drift`** — Auto-fix simple drift issues (broken file paths, renamed references) after manual review confirms correctness.
-- **`harness fix-drift --json`** — Machine-readable output for tracking what was auto-fixed.
-- **`harness validate`** — Run after documentation changes to verify overall project health is maintained.
-
-## Success Criteria
-
-- `harness check-docs` passes with zero errors after documentation updates
-- Every code change from the diff has been mapped to its documentation impact
-- All file paths in documentation match current file locations
-- All function/class names in documentation match current code
-- All behavioral descriptions in documentation match current implementation
-- Documentation updates are committed with clear references to the triggering code change
-- No orphaned references to old names, paths, or deleted features remain
-
-## Examples
-
-### Example: Syncing docs after a module rename
-
-**Code change:** `src/services/mailer.ts` renamed to `src/services/email-service.ts`. Functions `sendMail()` and `formatMailBody()` renamed to `sendEmail()` and `formatEmailBody()`.
-
-**Documentation impact map:**
-
-```
-AGENTS.md:34      — "mailer.ts handles email delivery" → update path and description
-AGENTS.md:78      — "Use sendMail() for all outbound email" → update function name
-docs/api.md:156   — sendMail() API reference → update name and import path
-docs/arch.md:45   — architecture diagram lists "mailer" → update to "email-service"
-src/controllers/user-controller.ts:12 — comment "// delegates to mailer" → update
-```
-
-**Updates applied:**
-
-- AGENTS.md: updated two sections with new file path and function names
-- docs/api.md: updated function reference and import example
-- docs/arch.md: updated module name in architecture description
-- src/controllers/user-controller.ts: updated inline comment
-
-**Validation:** `harness check-docs` passes. All references resolve. Commit: "docs: sync documentation after mailer rename to email-service"
-
-### Example: Syncing docs after adding error handling
-
-**Code change:** `createUser()` in `src/services/user-service.ts` now throws `ValidationError` instead of returning `null` on invalid input.
-
-**Documentation impact map:**
-
-```
-docs/api.md:89    — "Returns null if validation fails" → update to describe thrown error
-AGENTS.md:52      — No mention of error handling → add note about ValidationError
-src/services/user-service.ts:15 — JSDoc @returns tag → update, add @throws tag
-```
-
-**Updates applied:**
-
-- docs/api.md: replaced "returns null" with "throws ValidationError" and added example
-- AGENTS.md: added note about error handling pattern in user-service section
-- JSDoc: updated @returns, added @throws ValidationError
-
-**Validation:** `harness check-docs` passes. Commit: "docs: update documentation for createUser error handling change"
-
-## Escalation
-
-- **When you cannot determine what documentation is affected:** Run `harness check-docs` for automated detection. For manual analysis, search all `.md` files and code comments for the old name/path. If the change is large, use detect-doc-drift first to get a complete inventory.
-- **When documentation is in an external system (wiki, Confluence):** Document the needed change and flag it for manual update. Include the specific text that needs changing and the correct replacement.
-- **When the code change is so large that documentation needs a rewrite:** Break the documentation update into sections. Update one section at a time, validating after each. Do not attempt a full rewrite in one pass.
-- **When you disagree with the existing documentation style:** Follow the existing style. Documentation alignment is about accuracy, not style improvement. Style changes should be a separate, deliberate effort.

package/dist/agents/agents/skills/claude-code/align-documentation/skill.yaml

@@ -1,31 +0,0 @@
-name: align-documentation
-version: "1.0.0"
-description: Auto-fix documentation drift issues
-cognitive_mode: meticulous-verifier
-triggers:
-  - manual
-platforms:
-  - claude-code
-  - gemini-cli
-tools:
-  - Bash
-  - Read
-  - Write
-  - Edit
-cli:
-  command: harness skill run align-documentation
-  args:
-    - name: path
-      description: Project root path
-      required: false
-mcp:
-  tool: run_skill
-  input:
-    skill: align-documentation
-    path: string
-type: flexible
-state:
-  persistent: false
-  files: []
-depends_on:
-  - detect-doc-drift