cap-pro 1.0.0

package/.claude-plugin/README.md

@@ -0,0 +1,26 @@
+# CAP — Claude Code Plugin Manifests
+
+This directory holds the two manifests Claude Code reads when CAP is installed as a plugin (alongside, or instead of, `npx code-as-plan@latest`).
+
+## Triple-name layout
+
+CAP ships under three related-but-distinct names. Knowing which is which avoids most install-time confusion:
+
+| Name | Where it appears | Purpose |
+|------|------------------|---------|
+| `code-as-plan` | `package.json`, npm registry, `.claude-plugin/marketplace.json` | **Distribution slug.** The npm package name and the marketplace listing both use this kebab-case form so `/plugin install code-as-plan` and `npx code-as-plan@latest` stay symmetric. |
+| `cap` | `.claude-plugin/plugin.json` → `name`, slash commands (`/cap:init`, `/cap:status`, …), plugin cache directory (`~/.claude/plugins/cache/cap@…`) | **Plugin identity.** Short and command-friendly. All user-facing commands are namespaced `/cap:*`. |
+| `code-as-plan` | GitHub repository, homepage URL | **Project identity.** Repository URL and documentation live under the descriptive long-form. |
+
+The single source of truth for these names is [`cap/bin/lib/cap-plugin-manifest.cjs`](../cap/bin/lib/cap-plugin-manifest.cjs) (`PLUGIN_NAME`, `MARKETPLACE_NAME`, `NPM_PACKAGE_NAME`, `RESERVED_MARKETPLACE_NAMES`). Doctor checks, install detection, and tests all read from there.
+
+## Why two manifests?
+
+- **`plugin.json`** — consumed by Claude Code when the plugin is loaded. Declares metadata (name, version, author, commands directory) and is the file `isCapPluginManifest()` gates the local-dev install detection on.
+- **`marketplace.json`** — consumed by the `/plugin install <name>` flow. Lists CAP as a marketplace entry so users can install via `/plugin install code-as-plan` without knowing the plugin's internal name.
+
+Both coexist with the npx path. A user who installs via both routes gets a non-fatal warning from `cap:doctor` (dual-install is not an error — the npx copy and the plugin cache live in separate directories and do not collide).
+
+## Coexistence with `npx`
+
+`npx code-as-plan@latest` stays the primary install method. The plugin manifests are additive: they enable `/plugin install` as an alternative for users who prefer the marketplace UI, without deprecating the npx flow or fragmenting the CLI surface.

package/.claude-plugin/marketplace.json

@@ -0,0 +1,24 @@
+{
+  "name": "cap-pro",
+  "owner": {
+    "name": "TÂCHES"
+  },
+  "metadata": {
+    "description": "Official marketplace for CAP Pro — Code-First engineering framework.",
+    "version": "1.0.0"
+  },
+  "plugins": [
+    {
+      "name": "cap-pro",
+      "source": "./",
+      "description": "CAP Pro — build first, plan from code, annotation-driven workflow.",
+      "category": "productivity",
+      "tags": [
+        "engineering",
+        "workflow",
+        "annotation-driven",
+        "code-first"
+      ]
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -0,0 +1,24 @@
+{
+  "name": "cap-pro",
+  "version": "1.0.0",
+  "description": "CAP Pro — Code-First engineering framework. Build first, plan from code.",
+  "author": {
+    "name": "TÂCHES"
+  },
+  "homepage": "https://github.com/dwall-sys/code-as-plan",
+  "repository": "https://github.com/dwall-sys/code-as-plan",
+  "license": "MIT",
+  "keywords": [
+    "cap",
+    "cap-pro",
+    "claude",
+    "claude-code",
+    "ai",
+    "code-first",
+    "engineering-framework",
+    "prototype-driven",
+    "annotation-driven",
+    "farley"
+  ],
+  "commands": "./commands/cap/"
+}

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Lex Christopherson
+
+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.