product-spec 0.2.0

package/CHANGELOG.md

@@ -0,0 +1,49 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [Unreleased]
+
+### Changed
+
+- Renamed the published package, CLI, assistant command prefix, and managed manifest path to `product-spec`
+- Updated current-facing documentation, CLI help text, and packaged assistant assets to use `product-spec`
+- Updated current-facing repository guidance to use the `product-spec` name consistently
+
+## [0.2.0] - 2026-03-29
+
+### Added
+
+- TypeScript-based `product-spec` CLI scaffolding with `add`, `remove`, `check`, `doctor`, `help`, and `version`
+- Claude Code and Codex adapter structure with manifest-based ownership tracking
+- Versioned `assets/` tree for `/product-spec-*` assistant commands and shared `.product` templates
+- Vitest-based unit and integration coverage for manifest and CLI lifecycle flows
+- GitHub Actions for CI and tag-driven release publishing to GitHub Releases and npm
+
+### Changed
+
+- README now documents npm-first installation and direct `npx` execution for the `product-spec` CLI
+- `.npmignore` and package metadata prepared for npm distribution
+- npm package name is now `product-spec`
+
+### Removed
+
+- Legacy `install.sh` installer
+- Legacy tracked `/pm-*` Claude command files from the repository root command set
+
+## [2026-03-29]
+
+### Added
+
+- Feature specification, implementation plan, research, data model, CLI contract, quickstart, and task breakdown for the prime-time CLI and multi-agent release
+- Repository `.gitignore` cleanup for editor files, temp files, local agent directories, and generated local state
+- README status update describing current behavior and planned next-version direction
+- Initial `CHANGELOG.md`
+
+## [2026-03-28]
+
+### Added
+
+- Initial product-spec command set: `/pm-domain`, `/pm-press`, `/pm-faq`, and `/pm-align`
+- Product document templates for domain, press, FAQ, and requirements
+- Shell-based installer and README reorganization for the current Claude Code workflow

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Ehud
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,152 @@
+# product-spec
+
+The product management counterpart to [spec-kit](https://github.com/github/spec-kit). product-spec brings product management disciplines to spec-driven development, following Amazon's Working Backwards (PR/FAQ) methodology.
+
+While spec-kit handles engineering specifications, product-spec handles the product narrative: the domain context, press releases, FAQs, and requirements that define what you're building and why before spec-kit defines how.
+
+## Installation
+
+### Recommended: install globally from npm
+
+```sh
+npm install -g product-spec
+```
+
+Then inside any project:
+
+```sh
+product-spec add claude
+product-spec add codex
+product-spec add both
+product-spec check both
+```
+
+### Option 2: run directly without a global install
+
+```sh
+npx --yes --package product-spec product-spec add claude
+```
+
+Use the same pattern for other commands:
+
+```sh
+npx --yes --package product-spec product-spec check both
+```
+
+### Option 3: install from GitHub source
+
+This is the least recommended path, but it is useful when testing unpublished changes:
+
+```sh
+npm install -g github:ehud-am/product-spec
+```
+
+## CLI Usage
+
+Project integration commands:
+
+```text
+product-spec add claude
+product-spec add codex
+product-spec add both
+product-spec remove claude
+product-spec remove codex
+product-spec remove both
+product-spec check both
+product-spec doctor both
+product-spec version
+product-spec help
+```
+
+| Command | Purpose |
+|---------|---------|
+| `product-spec add <target>` | Add product-spec-managed assistant commands and shared templates to the current project |
+| `product-spec remove <target>` | Remove only product-spec-managed files for the selected target |
+| `product-spec check [target]` | Validate that managed integrations are present and healthy |
+| `product-spec doctor [target]` | Show richer diagnostics and recovery guidance |
+| `product-spec version` | Print the installed CLI version |
+| `product-spec help` | Show command help and examples |
+
+## Assistant Commands
+
+After adding an integration, use the installed slash commands inside the assistant:
+
+```text
+/product-spec-domain ...
+/product-spec-press ...
+/product-spec-faq
+/product-spec-align
+```
+
+| Target | Command directory | Slash commands |
+|--------|-------------------|----------------|
+| Claude Code | `.claude/commands/` | `/product-spec-domain`, `/product-spec-press`, `/product-spec-faq`, `/product-spec-align` |
+| Codex | `.Codex/commands/` | `/product-spec-domain`, `/product-spec-press`, `/product-spec-faq`, `/product-spec-align` |
+
+## How It Works
+
+product-spec creates a `.product/` folder in your project that maintains a living, cumulative view of the product across releases. Each document grows over time, telling the full story of the project from its first release to the one currently under development.
+
+### Documents
+
+| File | Purpose |
+|------|---------|
+| `.product/domain.md` | Industry context, target users, terminology, competitive landscape |
+| `.product/press.md` | Press releases for every release, upcoming first and historical below |
+| `.product/faq.md` | External and internal FAQs for every release, upcoming first and historical below |
+| `.product/requirements.md` | Release-independent, complete view of all product use cases and capabilities |
+
+### Workflow
+
+```text
+/product-spec-domain  -->  /product-spec-press  -->  /product-spec-faq  -->  /speckit.specify  -->  /product-spec-align
+    (context)       (promise)         (challenge)       (engineer)             (reconcile)
+```
+
+1. `/product-spec-domain` establishes the domain context: who the users are, what problem matters, and who the alternatives are.
+2. `/product-spec-press` writes a press release as if the next release has already shipped.
+3. `/product-spec-faq` challenges the press release with hard questions from customers and stakeholders.
+4. `/speckit.specify` hands off to spec-kit for engineering specifications.
+5. `/product-spec-align` reconciles product docs with the final engineering scope.
+
+## Key Concepts
+
+### Cumulative Documents
+
+Unlike traditional release notes, product-spec documents are cumulative. The press release file contains all press releases ever written for the project, with the upcoming release at the top and historical releases below. The same applies to FAQs.
+
+### `requirements.md` as the Product Spec
+
+While `press.md` and `faq.md` are organized by release, `requirements.md` is organized by functional area. It is the release-independent, always-current answer to "what does this product do?"
+
+### Working Backwards
+
+The methodology is Amazon's PR/FAQ approach:
+- start with the customer experience, not the technical solution
+- force hard questions early before committing engineering resources
+- treat the press release as a contract for value, clarity, and scope
+
+## Release and Publishing
+
+GitHub Actions now handles:
+- CI validation on pushes and pull requests
+- packaging tagged releases
+- publishing the npm package when a `v*` tag is pushed
+
+## Rename Notes
+
+`product-spec` is now the canonical package name, CLI name, assistant command prefix, and project-local manifest path.
+
+## Requirements
+
+- Node.js and npm
+- [Claude Code](https://claude.ai/code) and/or Codex for assistant integration targets
+- [spec-kit](https://github.com/github/spec-kit) for the `/speckit.specify` portion of the workflow
+
+## Changelog
+
+Project history lives in [CHANGELOG.md](CHANGELOG.md).
+
+## License
+
+MIT

package/assets/claude/commands/product-spec-align.md

@@ -0,0 +1,37 @@
+---
+description: Reconcile the .product folder with changes made in .specify specs — update press, faq, and requirements.
+handoffs:
+  - label: Update Press Release
+    agent: product-spec-press
+    prompt: Refine the press release based on alignment findings
+  - label: Update FAQs
+    agent: product-spec-faq
+    prompt: Update the FAQs based on alignment findings
+  - label: Update Domain
+    agent: product-spec-domain
+    prompt: Update domain knowledge based on what we learned during alignment
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+You are reconciling the product documents in `.product/` with the engineering specifications in `.specify/`.
+
+### Pre-Execution
+
+1. Load `.product/domain.md`, `.product/press.md`, `.product/faq.md`, and `.product/requirements.md` when present.
+2. Discover all `spec.md` files under `.specify/`.
+3. Use `.product/templates/requirements-template.md` if `requirements.md` does not yet exist.
+
+### Execution Flow
+
+1. Compare press release promises against the actual engineering specs.
+2. Update FAQs and requirements to reflect reality.
+3. Preserve historical product narrative and produce an alignment report.

package/assets/claude/commands/product-spec-domain.md

@@ -0,0 +1,32 @@
+---
+description: Provide domain knowledge as background context for the project.
+handoffs:
+  - label: Write Press Release
+    agent: product-spec-press
+    prompt: Write the press release for the next release
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+You are creating or updating the domain knowledge document at `.product/domain.md`. This document captures the industry context, problem space, target users, terminology, and competitive landscape that inform all product decisions.
+
+### Pre-Execution
+
+1. **Ensure `.product/` exists**: If the `.product/` directory does not exist, create it.
+2. **Check for existing domain doc**: Read `.product/domain.md` if it exists.
+   - If it exists and has content beyond the template, this is an **update** — preserve existing content and merge new information.
+   - If it does not exist, load `.product/templates/domain-template.md` as the starting structure.
+
+### Execution Flow
+
+1. **Parse user input**: The text after `/product-spec-domain` is the domain context the user wants to capture.
+2. Create or update `.product/domain.md` using the same quality checks and guidelines as the existing product-spec domain workflow.
+3. Suggest `/product-spec-press` as the next step when appropriate.

package/assets/claude/commands/product-spec-faq.md

@@ -0,0 +1,34 @@
+---
+description: Create or update FAQs that challenge and support the press release claims.
+handoffs:
+  - label: Update Press Release
+    agent: product-spec-press
+    prompt: Update the press release based on what we learned from the FAQs
+  - label: Build Specification
+    agent: speckit.specify
+    prompt: Create a technical spec for the next feature. I want to build...
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+You are creating or updating the FAQ document at `.product/faq.md`.
+
+### Pre-Execution
+
+1. Ensure `.product/` exists.
+2. Load `.product/domain.md` and `.product/press.md` when available.
+3. If `.product/faq.md` is missing, start from `.product/templates/faq-template.md`.
+
+### Execution Flow
+
+1. The text after `/product-spec-faq` describes what to generate or update.
+2. Produce external and internal FAQs that challenge the current press release honestly.
+3. Preserve historical FAQ sections and suggest `/speckit.specify` when the feature is ready for engineering.

package/assets/claude/commands/product-spec-press.md

@@ -0,0 +1,31 @@
+---
+description: Provide the press release for the project following Amazon's Working Backwards methodology.
+handoffs:
+  - label: Write FAQs
+    agent: product-spec-faq
+    prompt: Write the FAQs that challenge this press release
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+You are creating or updating the press release document at `.product/press.md`.
+
+### Pre-Execution
+
+1. Ensure `.product/` exists.
+2. Load `.product/domain.md` if it exists.
+3. Read `.product/press.md` if it exists; otherwise use `.product/templates/press-template.md`.
+
+### Execution Flow
+
+1. The text after `/product-spec-press` describes what to write.
+2. Create or update the current upcoming press release using Amazon's Working Backwards format.
+3. Preserve historical entries and suggest `/product-spec-faq` when appropriate.

package/assets/codex/commands/product-spec-align.md

@@ -0,0 +1,25 @@
+---
+description: Reconcile the .product folder with changes made in .specify specs — update press, faq, and requirements.
+handoffs:
+  - label: Update Press Release
+    agent: product-spec-press
+    prompt: Refine the press release based on alignment findings
+  - label: Update FAQs
+    agent: product-spec-faq
+    prompt: Update the FAQs based on alignment findings
+  - label: Update Domain
+    agent: product-spec-domain
+    prompt: Update domain knowledge based on what we learned during alignment
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+You are reconciling `.product/` with `.specify/` specs so product-facing documents stay aligned with the engineering scope.

package/assets/codex/commands/product-spec-domain.md

@@ -0,0 +1,19 @@
+---
+description: Provide domain knowledge as background context for the project.
+handoffs:
+  - label: Write Press Release
+    agent: product-spec-press
+    prompt: Write the press release for the next release
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+You are creating or updating the domain knowledge document at `.product/domain.md`. This document captures the industry context, problem space, target users, terminology, and competitive landscape that inform all product decisions.

package/assets/codex/commands/product-spec-faq.md

@@ -0,0 +1,22 @@
+---
+description: Create or update FAQs that challenge and support the press release claims.
+handoffs:
+  - label: Update Press Release
+    agent: product-spec-press
+    prompt: Update the press release based on what we learned from the FAQs
+  - label: Build Specification
+    agent: speckit.specify
+    prompt: Create a technical spec for the next feature. I want to build...
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+You are creating or updating the FAQ document at `.product/faq.md`, generating honest external and internal questions that stress-test the current press release.

package/assets/codex/commands/product-spec-press.md

@@ -0,0 +1,19 @@
+---
+description: Provide the press release for the project following Amazon's Working Backwards methodology.
+handoffs:
+  - label: Write FAQs
+    agent: product-spec-faq
+    prompt: Write the FAQs that challenge this press release
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+You are creating or updating the press release document at `.product/press.md`, preserving historical entries and writing from the customer's point of view.

package/assets/product/templates/domain-template.md

@@ -0,0 +1,52 @@
+# Domain Knowledge: [PROJECT_NAME]
+
+**Last Updated**: [DATE]
+
+## Industry Context
+
+[Describe the industry or market this project operates in. What is the broader landscape? Who are the key players? What trends are shaping this space?]
+
+## Problem Space
+
+[What fundamental problem does this project address? Why does this problem matter? Who experiences this problem most acutely?]
+
+## Target Users
+
+### Primary Users
+
+- **[Persona 1]**: [Role, goals, pain points, and how they relate to this project]
+- **[Persona 2]**: [Role, goals, pain points, and how they relate to this project]
+
+### Secondary Users
+
+- **[Persona 3]**: [Role, goals, and indirect relationship to the project]
+
+## Key Concepts & Terminology
+
+| Term | Definition |
+|------|-----------|
+| [Term 1] | [Clear, concise definition as used in this project's context] |
+| [Term 2] | [Clear, concise definition as used in this project's context] |
+| [Term 3] | [Clear, concise definition as used in this project's context] |
+
+## Competitive Landscape
+
+| Competitor / Alternative | Approach | Strengths | Weaknesses |
+|--------------------------|----------|-----------|------------|
+| [Competitor 1] | [How they solve the problem] | [What they do well] | [Where they fall short] |
+| [Competitor 2] | [How they solve the problem] | [What they do well] | [Where they fall short] |
+| [Status quo / manual process] | [How people cope today] | [Why they stick with it] | [Cost of not changing] |
+
+## Constraints & Regulations
+
+- [Industry regulation, compliance requirement, or technical constraint that shapes product decisions]
+- [Market expectation or standard that must be met]
+
+## Key Metrics & Success Indicators
+
+- [How success is measured in this domain — e.g., adoption rate, time-to-value, retention]
+- [Industry benchmarks or standards to aim for]
+
+## Open Questions
+
+- [Unresolved domain questions that may affect product direction]

package/assets/product/templates/faq-template.md

@@ -0,0 +1,38 @@
+# Frequently Asked Questions: [PROJECT_NAME]
+
+**Last Updated**: [DATE]
+
+---
+
+## [RELEASE_NAME] — [TARGET_DATE] *(upcoming)*
+
+### External FAQs (Customer-Facing)
+
+**Q: [Question a customer would ask after reading the press release]**
+A: [Clear, honest answer. No jargon. If the answer is "not yet," say so and explain the plan.]
+
+**Q: [Question about pricing, availability, or getting started]**
+A: [Direct answer with specifics where possible.]
+
+**Q: [Question about how this compares to alternatives]**
+A: [Honest comparison. Acknowledge competitor strengths. Explain your differentiation.]
+
+**Q: [Question about limitations or edge cases]**
+A: [Transparent answer about what the product does NOT do and why.]
+
+### Internal FAQs (Stakeholder-Facing)
+
+**Q: [Question about feasibility — "Can we actually build this?"]**
+A: [Technical assessment. What's proven vs. what's risky? What needs prototyping?]
+
+**Q: [Question about scope — "Why not also do X?"]**
+A: [Explain the scoping decision. What's deferred and why? What's the cost of adding it?]
+
+**Q: [Question about metrics — "How will we know this is working?"]**
+A: [Specific metrics, measurement approach, and success thresholds.]
+
+**Q: [Question about dependencies or risks]**
+A: [Identify dependencies, risks, and mitigation strategies.]
+
+**Q: [Question about timeline or resources]**
+A: [Honest assessment of what it takes to deliver.]

package/assets/product/templates/press-template.md

@@ -0,0 +1,26 @@
+# Press Releases: [PROJECT_NAME]
+
+<!--
+  This document contains all press releases for this project, ordered reverse-chronologically.
+-->
+
+---
+
+## [RELEASE_NAME] — [TARGET_DATE] *(upcoming)*
+
+**[CITY, STATE]** — [One-sentence opening that names the customer segment and the key benefit they now have. This is the hook.]
+
+[Second paragraph: What is the problem customers faced? Why was it painful or costly? Set up the "before" state in 2-3 sentences.]
+
+[Third paragraph: What does the product/feature do? Describe it in customer terms — what they can now do that they couldn't before. No implementation details. Keep it to 3-4 sentences.]
+
+> "[Customer quote expressing delight about how this changes their workflow/life. Should feel authentic, specific, and human.]"
+> — [Customer Name], [Title], [Company/Context]
+
+[Fourth paragraph: How to get started. What does a customer do next? One clear call to action.]
+
+### Key Benefits
+
+- **[Benefit 1]**: [One sentence explaining the customer value]
+- **[Benefit 2]**: [One sentence explaining the customer value]
+- **[Benefit 3]**: [One sentence explaining the customer value]

package/assets/product/templates/requirements-template.md

@@ -0,0 +1,34 @@
+# Product Requirements: [PROJECT_NAME]
+
+**Last Updated**: [DATE]
+
+## Product Overview
+
+[2-3 sentences describing what the product does, who it's for, and the core value proposition.]
+
+## Use Cases
+
+### UC-001: [Use Case Name]
+
+- **Actor**: [Who performs this]
+- **Goal**: [What they want to accomplish]
+- **Description**: [How the product supports this goal, end to end]
+- **Status**: [Complete | Partial | Planned]
+
+## Functional Summary
+
+### [Functional Area 1]
+
+| Capability | Description | Status |
+|-----------|-------------|--------|
+| [Capability] | [What it does from the user's perspective] | [Shipped / In Progress / Planned] |
+
+## Cross-Cutting Concerns
+
+- **[Concern]**: [How it's handled across the product]
+
+## Changelog
+
+| Date | Change | Source |
+|------|--------|--------|
+| [DATE] | [What changed in this document] | [Which spec or release triggered the update] |

package/dist/adapters/claude.d.ts

@@ -0,0 +1,2 @@
+import type { AssistantAdapter } from "./types.js";
+export declare const claudeAdapter: AssistantAdapter;

package/dist/adapters/claude.js

@@ -0,0 +1,26 @@
+import { joinProjectPath, pathExists } from "../core/fs/project.js";
+async function describeHealthIssues(context) {
+    const issues = [];
+    for (const asset of context.targetAssets) {
+        const absolutePath = joinProjectPath(context.rootDir, asset.targetPath);
+        if (!(await pathExists(absolutePath))) {
+            issues.push({
+                code: "CLAUDE_MISSING_FILE",
+                severity: "error",
+                message: `Missing Claude Code asset ${asset.targetPath}`,
+                path: asset.targetPath
+            });
+        }
+    }
+    return issues;
+}
+export const claudeAdapter = {
+    key: "claude",
+    displayName: "Claude Code",
+    commandDir: ".claude/commands",
+    resolveCommandTarget(fileName) {
+        return `.claude/commands/${fileName}`;
+    },
+    describeHealthIssues
+};
+//# sourceMappingURL=claude.js.map

package/dist/adapters/claude.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"claude.js","sourceRoot":"","sources":["../../src/adapters/claude.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,eAAe,EAAE,UAAU,EAAE,MAAM,uBAAuB,CAAC;AAEpE,KAAK,UAAU,oBAAoB,CAAC,OAA6B;IAC/D,MAAM,MAAM,GAAkB,EAAE,CAAC;IAEjC,KAAK,MAAM,KAAK,IAAI,OAAO,CAAC,YAAY,EAAE,CAAC;QACzC,MAAM,YAAY,GAAG,eAAe,CAAC,OAAO,CAAC,OAAO,EAAE,KAAK,CAAC,UAAU,CAAC,CAAC;QACxE,IAAI,CAAC,CAAC,MAAM,UAAU,CAAC,YAAY,CAAC,CAAC,EAAE,CAAC;YACtC,MAAM,CAAC,IAAI,CAAC;gBACV,IAAI,EAAE,qBAAqB;gBAC3B,QAAQ,EAAE,OAAO;gBACjB,OAAO,EAAE,6BAA6B,KAAK,CAAC,UAAU,EAAE;gBACxD,IAAI,EAAE,KAAK,CAAC,UAAU;aACvB,CAAC,CAAC;QACL,CAAC;IACH,CAAC;IAED,OAAO,MAAM,CAAC;AAChB,CAAC;AAED,MAAM,CAAC,MAAM,aAAa,GAAqB;IAC7C,GAAG,EAAE,QAAQ;IACb,WAAW,EAAE,aAAa;IAC1B,UAAU,EAAE,kBAAkB;IAC9B,oBAAoB,CAAC,QAAgB;QACnC,OAAO,oBAAoB,QAAQ,EAAE,CAAC;IACxC,CAAC;IACD,oBAAoB;CACrB,CAAC"}

package/dist/adapters/codex.d.ts

@@ -0,0 +1,2 @@
+import type { AssistantAdapter } from "./types.js";
+export declare const codexAdapter: AssistantAdapter;

package/dist/adapters/codex.js

@@ -0,0 +1,26 @@
+import { joinProjectPath, pathExists } from "../core/fs/project.js";
+async function describeHealthIssues(context) {
+    const issues = [];
+    for (const asset of context.targetAssets) {
+        const absolutePath = joinProjectPath(context.rootDir, asset.targetPath);
+        if (!(await pathExists(absolutePath))) {
+            issues.push({
+                code: "CODEX_MISSING_FILE",
+                severity: "error",
+                message: `Missing Codex asset ${asset.targetPath}`,
+                path: asset.targetPath
+            });
+        }
+    }
+    return issues;
+}
+export const codexAdapter = {
+    key: "codex",
+    displayName: "Codex",
+    commandDir: ".Codex/commands",
+    resolveCommandTarget(fileName) {
+        return `.Codex/commands/${fileName}`;
+    },
+    describeHealthIssues
+};
+//# sourceMappingURL=codex.js.map

package/dist/adapters/codex.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"codex.js","sourceRoot":"","sources":["../../src/adapters/codex.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,eAAe,EAAE,UAAU,EAAE,MAAM,uBAAuB,CAAC;AAEpE,KAAK,UAAU,oBAAoB,CAAC,OAA6B;IAC/D,MAAM,MAAM,GAAkB,EAAE,CAAC;IAEjC,KAAK,MAAM,KAAK,IAAI,OAAO,CAAC,YAAY,EAAE,CAAC;QACzC,MAAM,YAAY,GAAG,eAAe,CAAC,OAAO,CAAC,OAAO,EAAE,KAAK,CAAC,UAAU,CAAC,CAAC;QACxE,IAAI,CAAC,CAAC,MAAM,UAAU,CAAC,YAAY,CAAC,CAAC,EAAE,CAAC;YACtC,MAAM,CAAC,IAAI,CAAC;gBACV,IAAI,EAAE,oBAAoB;gBAC1B,QAAQ,EAAE,OAAO;gBACjB,OAAO,EAAE,uBAAuB,KAAK,CAAC,UAAU,EAAE;gBAClD,IAAI,EAAE,KAAK,CAAC,UAAU;aACvB,CAAC,CAAC;QACL,CAAC;IACH,CAAC;IAED,OAAO,MAAM,CAAC;AAChB,CAAC;AAED,MAAM,CAAC,MAAM,YAAY,GAAqB;IAC5C,GAAG,EAAE,OAAO;IACZ,WAAW,EAAE,OAAO;IACpB,UAAU,EAAE,iBAAiB;IAC7B,oBAAoB,CAAC,QAAgB;QACnC,OAAO,mBAAmB,QAAQ,EAAE,CAAC;IACvC,CAAC;IACD,oBAAoB;CACrB,CAAC"}