create-pathfinder 3.0.0 → 3.1.0

package/CLAUDE.md

@@ -70,6 +70,8 @@ Ask before actions identified in `context/ai-interaction.md`, especially depende
 
 Canonical Pathfinder skills are tool-neutral and live under `skills/`. Harness-specific representations — `.claude/skills/`, `.agents/skills/` — are generated integration artifacts and must not become independent behavior contracts. Edit the canonical file; regenerate the adapter.
 
+The Claude Code plugin declared by `.claude-plugin/plugin.json` is a third discovery surface, and the only one that generates nothing: it exposes the canonical `skills/` tree itself, namespaced `/pathfinder:<skill>`. There is no plugin copy of any skill and there must never be one. If a discovery surface and its canonical skill disagree, the canonical skill is correct.
+
 An adapter carries the canonical skill's frontmatter and a pointer to it, and nothing else. If an adapter and its canonical skill disagree, the canonical skill is correct.
 
 ## Available skills

package/README.md

@@ -261,6 +261,23 @@ Pathfinder also never writes to personal/global skill directories such as:
 ~/.agents/skills/
 ```
 
+### The Claude Code plugin is a separate path
+
+Pathfinder is also distributed as a Claude Code plugin, installed with
+`/plugin marketplace add rikilamadrid/pathfinder` followed by
+`/plugin install pathfinder@lamadrid-labs`. It does not replace this installer
+and does not change anything it does.
+
+The two install different things. The plugin installs commands, always
+namespaced `/pathfinder:<skill>`, into your Claude Code installation and writes
+nothing into your repository — no kit, no adapters. This installer copies the
+kit your repository keeps under version control, and generates the adapters that
+expose the bare `/<skill>` names.
+
+A repository can have both, and then carries both command forms running the same
+canonical skill body. If you arrived through the plugin with no kit yet,
+`/pathfinder:kickstart-pathfinder` offers to install one for you.
+
 ### Interactive selection
 
 In an interactive terminal, the installer asks which supported tools to

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-pathfinder",
-  "version": "3.0.0",
+  "version": "3.1.0",
   "description": "Install the Pathfinder AI-assisted, human-in-the-loop workflow kit into a Git repository.",
   "keywords": [
     "pathfinder",

package/skills/kickstart-pathfinder/SKILL.md

@@ -36,18 +36,57 @@ When the user is unsure, provide a small recommendation with reasoning and alter
 
 ## Process
 
-1. Read the kit context and inspect relevant repository facts.
-2. Ask the minimum unresolved questions in small groups.
-3. Summarize requirements, preferences, constraints, open decisions, and contradictions.
-4. Route uncertain product/technical choices to `debate-me` when useful.
-5. Present the proposed context and request human corrections or approval.
-6. Update `context/project-overview.md`, `context/coding-standards.md`, `context/ai-interaction.md`, `CLAUDE.md`, and `AGENTS.md` only after the choices are sufficiently clear.
+1. If the project is missing kit files, and this session loaded this skill from
+   the Pathfinder plugin, offer to install the kit before going further. See
+   `Kit Bootstrap` below. Otherwise start at the next step.
+2. Read the kit context and inspect relevant repository facts.
+3. Ask the minimum unresolved questions in small groups.
+4. Summarize requirements, preferences, constraints, open decisions, and contradictions.
+5. Route uncertain product/technical choices to `debate-me` when useful.
+6. Present the proposed context and request human corrections or approval.
+7. Update `context/project-overview.md`, `context/coding-standards.md`, `context/ai-interaction.md`, `CLAUDE.md`, and `AGENTS.md` only after the choices are sufficiently clear.
    `context/project-overview.md` does not ship; create it from `templates/project-overview.template.md` at this step.
    Project facts go there; approval rules and tool actions requiring a human go
    in `context/ai-interaction.md`. Fill the sections the project has and mark
    the rest `TBD` or `None`. Do not add sections the template does not carry,
    and do not leave a field blank.
-7. Recommend `debate-me`, `prototype`, or `to-specs` as the next action.
+8. Recommend `debate-me`, `prototype`, or `to-specs` as the next action.
+
+## Kit Bootstrap
+
+The Pathfinder plugin distributes commands. It does not distribute project
+state. A repository reached through `/plugin install` therefore has every
+Pathfinder command and none of the files those commands read.
+
+This step applies only when both are true: the project is missing kit files,
+and this skill was loaded from the plugin, which is what makes
+`${CLAUDE_PLUGIN_ROOT}` — the plugin's install directory — a real path. When
+the kit installed this skill into the repository instead, there is no plugin
+root, the condition is false, and this whole section is skipped without being
+raised or quoted.
+
+When it does apply:
+
+- Copy from the plugin root into the project root, and copy only the kit. That
+  list is not restated here: `packages/create-pathfinder/copy-list.json`, inside
+  the plugin root, is the one statement of it. Read that file and copy the
+  entries it names.
+- Exclude exactly what the installer excludes, and read that from the installer
+  too: `NEVER_SHIPS` in `packages/create-pathfinder/src/kit.mjs`, also inside
+  the plugin root, is the one statement of it. Skip every kit-relative path it
+  holds. Those files are one repository's own working state and would be wrong
+  in any other project. Restating them here would be a second list to keep in
+  step, and the first time it drifted this step would hand a project what
+  `npx create-pathfinder` refuses to.
+- Name every file before writing it, and wait for approval.
+- Overwrite nothing without asking about that file by name. Delete nothing.
+- Report exactly what was written, what was skipped, and what was left alone.
+- Generate no harness adapters. Plugin commands stay namespaced
+  `/<plugin-name>:<skill>`, and that is the intended plugin form.
+  `npx create-pathfinder --agents claude-code` is what generates adapters and
+  the bare command names, for a human who wants both.
+
+When the project already has the kit, change nothing and say so.
 
 ## Stop Condition