@zalom/plastic 1.0.0-alpha.3 → 1.0.0-alpha.31

package/skills/install/SKILL.md

@@ -1,22 +1,64 @@
 ---
-name: plastic:install
-description: Use when initializing Plastic globally (~/.plastic/) or locally in a project. Global install is recommended — creates the global intent store as a git-backed repository. Local install creates .plastic/ in the current project for testing.
+name: plastic-install
+description: Use when initializing Plastic globally (~/.plastic/) or locally in a project, or to re-install/repair a broken installation. Accepts channel flags (--alpha, --beta, --latest) to select release channel. Default is --latest (stable). Global install is recommended — creates the global intent store as a git-backed repository. Local install creates .plastic/ in the current project for testing.
 ---
 
 # Install Plastic
 
+> **Recommended path:** for a first install, run `npx @zalom/plastic@latest install --claude`
+> in your shell (or `bunx @zalom/plastic@latest --claude` if you use Bun). This skill
+> exists to **re-install or repair** an existing setup from inside the agent, and to
+> drive interactive global configuration. Whenever this skill performs an install or
+> re-install, it **runs `/plastic-doctor` afterward** and reports the result.
+
+## Re-install / repair
+
+If Plastic is already installed but something is broken (skills missing, hooks not
+firing, leftover legacy plugin), re-run the installer — it is idempotent, prunes
+files that no longer ship, and removes any legacy plugin/marketplace layout:
+
+```bash
+npx @zalom/plastic@latest install --reinstall --claude   # or @beta / @alpha to match your channel
+```
+
+Then **run `/plastic-doctor`** and report what it found.
+
+## Channel Flags
+
+| Flag | Behavior |
+|------|----------|
+| `--latest` | Install from stable channel (default) |
+| `--beta` | Install from beta channel |
+| `--alpha` | Install from alpha channel |
+
+When invoked from within Claude Code (re-install or channel switch), the skill
+runs the appropriate npx command:
+
+```bash
+# Stable (default)
+npx @zalom/plastic install --claude
+
+# Beta
+npx @zalom/plastic@beta install --claude
+
+# Alpha
+npx @zalom/plastic@alpha install --claude
+```
+
+The installed version and channel are recorded in `~/.plastic/VERSION`.
+
 ## Modes
 
 ### Global Install (default, recommended)
 
-Run `/plastic:install` with no arguments.
+Run `/plastic-install` with no arguments.
 
 #### Procedure
 
 **Step 1: Check for existing installation**
 
 Check if `~/.plastic/INDEX.md` exists.
-- If yes: announce "Plastic is already installed at ~/.plastic/. Run `/plastic:update` to sync core files."
+- If yes: announce "Plastic is already installed at ~/.plastic/. Run `/plastic-update` to sync core files."
 - If no: proceed with fresh install.
 
 **Step 2: Create ~/.plastic/ as a git repo**
@@ -106,13 +148,32 @@ Update `config.yml` with any additional roots.
 
 Auto-commit the config change.
 
-**Step 4: Announce**
+**Step 4: Verify with doctor**
+
+Run `/plastic-doctor` and report the result. Resolve any fixable findings before
+announcing success.
+
+**Step 5: Register stores with QMD (optional)**
+
+QMD is an optional search layer. If it is installed, register the Plastic stores so
+they are searchable:
+
+```bash
+ruby ~/.plastic/scripts/qmd-sync detect && ruby ~/.plastic/scripts/qmd-sync register --all
+```
+
+`qmd-sync` no-ops cleanly when QMD is absent, so this is safe to run unconditionally.
+It registers `plastic-global` and every project store from `projects.yml`, then indexes
+them. Report what was registered, or that QMD was not detected and the step was skipped.
+
+**Step 6: Announce**
 
-> "Plastic installed globally at ~/.plastic/. Create your first intent with `/plastic:creating-intent`."
+> "Plastic installed globally at ~/.plastic/. Health check: [doctor summary].
+> Create your first intent with `/plastic-creating-intent`."
 
 ### Local Install (testing/legacy)
 
-Run `/plastic:install --local`.
+Run `/plastic-install --local`.
 
 #### Procedure
 
@@ -131,4 +192,4 @@ Run `/plastic:install --local`.
 
 **Step 4:** Commit in project: `git add .plastic/ && git commit -m "chore: initialize Plastic local store"`
 
-**Step 5:** Announce: "Plastic initialized locally. This is a testing/legacy mode. Consider `/plastic:install` for global mode."
+**Step 5:** Announce: "Plastic initialized locally. This is a testing/legacy mode. Consider `/plastic-install` for global mode."

package/skills/intent-curator/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:intent-curator
+name: plastic-intent-curator
 description: |
   Use when completing or reviewing intents, reorganizing the index,
   or when the intent store needs maintenance. Examples:
@@ -15,7 +15,7 @@ description: |
 
 # Intent Curator
 
-Dispatches to the `plastic:intent-curator` agent for intent store maintenance.
+Dispatches to the `plastic-intent-curator` agent for intent store maintenance.
 
 ## When to Use
 - Completing or reviewing intents
@@ -25,7 +25,7 @@ Dispatches to the `plastic:intent-curator` agent for intent store maintenance.
 
 ## Workflow
 
-Invoke the `plastic:intent-curator` agent via the Agent tool with `subagent_type: "plastic:intent-curator"`. Pass the user's request as the prompt, including:
+Invoke the `plastic-intent-curator` agent via the Agent tool with `subagent_type: "plastic-intent-curator"`. Pass the user's request as the prompt, including:
 
 1. **What to do** — complete intent, reorganize, triage stale, etc.
 2. **Which store** — global (`~/.plastic/`) or project (`.plastic/store/`)

package/skills/linking-intents/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:linking-intents
+name: plastic-linking-intents
 description: Use when creating connections between intents, the user says "link" or "connect", or when discovering that two intents are related. Manages sources, chain, and cross-reference links.
 ---
 
@@ -70,3 +70,7 @@ Add a wikilink in the `## Links` section of **both** intents (bidirectional).
 
 ### 4. Update INDEX.md Clusters
 If both intents share a topic, ensure they're in the same cluster.
+
+## References
+
+- Read `references/zettelkasten.md` for the three Zettelkasten structures (Folgezettel, directed graph, tags), ID encoding rules, and dual-mode (Obsidian + programmatic) design

package/skills/linking-intents/references/zettelkasten.md

@@ -0,0 +1,33 @@
+# Zettelkasten Structure
+
+Plastic implements three Zettelkasten structures:
+
+| Structure | Implementation | Purpose |
+|---|---|---|
+| Folgezettel (linked list) | `sources` + `chain` in frontmatter | Sequential provenance |
+| Directed graph (web of notes) | `## Links` with wikilinks | Obsidian navigation |
+| Tag-based taxonomy | `tags` in frontmatter | Topic grouping |
+
+INDEX.md is a structure note (hub), not a table of contents.
+
+## Folgezettel IDs
+
+IDs encode lineage using Luhmann's alternating convention:
+- Root intents: sequential numbers (`1`, `2`, `3`...)
+- Branches alternate letters and numbers: `1` → `1a` → `1a1` → `1a1a` → ...
+- Multiple branches from the same parent increment: `1a`, `1b`, `1c`
+- IDs are assigned at creation time and never change
+
+## Knowledge Graph
+
+`sources` + `chain` form the double-linked knowledge graph:
+- `sources` = what fed into this intent (parents, inspirations, prerequisites)
+- `chain` = what this intent produced (children, follow-ups, spin-offs)
+
+## Dual-Mode
+
+This store works in two modes without modification:
+- **Obsidian** (human, offline) — browse, link, write markdown
+- **Programmatic** (any agent) — read/write via filesystem operations
+
+No special tooling required for either mode.

package/skills/managing-index/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:managing-index
+name: plastic-managing-index
 description: Use after creating, completing, or abandoning intents, when the user says "index" or "organize", or when INDEX.md needs maintenance. Curates the INDEX.md structure note.
 ---
 
@@ -64,3 +64,7 @@ When 3+ intents share tags but aren't in a cluster, suggest a new cluster headin
 Intents with no links (empty `sources`, empty `chain`, no `## Links` entries, not in any cluster) should be flagged for curation.
 
 REQUIRED BACKGROUND: linking-intents (for understanding connection types and Zettelkasten theory)
+
+## References
+
+- Read `references/zettelkasten-linking.md` for the three structural layers (Folgezettel, directed graph, tags) and how they map to INDEX.md organization

package/skills/releasing/SKILL.md

@@ -1,30 +1,67 @@
 ---
-name: plastic:releasing
+name: plastic-releasing
 description: Use when merging a feature branch to main and tagging a release, bumping the version, or when the user says "release", "tag", or "ship it"
 ---
 
 # Releasing
 
 Merge, bump, tag, push. Annotated tags with changelogs. Semantic versioning.
+Project configuration drives the workflow — no hardcoded assumptions.
 
 ## Checklist
 
-- [ ] All tests pass
+- [ ] Read project config
+- [ ] All tests pass (or verification skipped per config)
 - [ ] Merge feature branch to main
-- [ ] Bump version in plugin.json and marketplace.json
+- [ ] Bump version in configured version files
 - [ ] Commit version bump
 - [ ] Create annotated tag
 - [ ] Push to remote with tags
+- [ ] Run post-push actions (GitHub release, npm publish, etc.)
+- [ ] Complete active intent
 
 ## Workflow
 
+### 0. Read Project Config
+
+Before anything else, determine which project we are releasing and load its config.
+
+1. Read `~/.plastic/projects.yml` — find the project whose `path` matches the current working directory.
+2. Extract the project slug (the key under `projects:`).
+3. Read `~/.plastic/projects/{slug}/project.yml` — this contains the `release:` section.
+
+Expected `release:` keys in project.yml:
+
+```yaml
+release:
+  verify: "bin/rails test"              # command to run before release
+  version_file: package.json            # single file containing the version
+  version_files:                        # multiple files (overrides version_file)
+    - package.json
+    - .claude-plugin/plugin.json
+  tag_format: "v{{version}}"            # tag naming pattern ({{version}} is replaced)
+  on_green:                             # actions to run after push succeeds
+    - github_release
+    - npm_publish
+  on_complete: commit_and_push          # what to do with the version bump commit
+  on_red: stop                          # what to do if verification fails
+```
+
+**Fallback:** If no project.yml exists or it has no `release:` section, fall back to asking the user for each step — verify command, version files, tag format, and post-push actions.
+
 ### 1. Verify Tests Pass
 
+Run the verification command from `release.verify` in project.yml:
+
 ```bash
-ruby test/read_config_test.rb && ruby test/config_template_test.rb
+# Example: release.verify = "ruby -Itest test/*_test.rb"
+<verify-command-from-config>
 ```
 
-All tests must pass before release. Do not proceed if any fail.
+- If `release.verify` is present: run it. All checks must pass before proceeding.
+- If `release.verify` is absent or empty: skip verification. Log that no verify command is configured.
+- If `release.on_red` is `stop`: abort the release on failure.
+- If `release.on_red` is `fix_and_retry`: ask the user to fix and re-run.
 
 ### 2. Determine Version Bump
 
@@ -47,18 +84,26 @@ Always `--no-ff` to preserve branch history in the merge commit.
 
 ### 4. Bump Version
 
-Update ALL THREE files — they must stay in sync:
-- `package.json` → `"version": "X.Y.Z"`
-- `.claude-plugin/plugin.json` → `"version": "X.Y.Z"`
-- `.claude-plugin/marketplace.json` → `"version": "X.Y.Z"`
+Determine which files to update from project.yml:
+
+- If `release.version_files` is set: update ALL listed files (they must stay in sync).
+- Else if `release.version_file` is set: update that single file.
+- Else: ask the user which files contain the version.
+
+Update the version string in each file, then commit:
 
 ```bash
-git add package.json .claude-plugin/plugin.json .claude-plugin/marketplace.json
+git add <version-files>
 git commit -m "chore: bump version to X.Y.Z — [one-line summary]"
 ```
 
 ### 5. Create Annotated Tag
 
+Read `release.tag_format` from project.yml to determine the tag name:
+
+- If set (e.g. `"v{{version}}"`): replace `{{version}}` with the new version string.
+- If not set: default to `vX.Y.Z`.
+
 Generate the changelog from commits since the last tag:
 
 ```bash
@@ -68,7 +113,7 @@ git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges | grep -E
 Create the tag with a multi-line message:
 
 ```bash
-git tag -a vX.Y.Z -m "vX.Y.Z — [release name]
+git tag -a <tag-name> -m "<tag-name> — [release name]
 
 - [changelog bullet points from feat/fix/refactor commits]"
 ```
@@ -79,16 +124,50 @@ git tag -a vX.Y.Z -m "vX.Y.Z — [release name]
 git push origin main --tags
 ```
 
-### 7. GitHub Release
+### 7. Post-Push Actions
 
-Create a GitHub release from the tag. Use `--generate-notes` to auto-generate changelog from commits since the previous tag:
+Read `release.on_green` from project.yml. This is a list of actions to run after a successful push. Execute each in order:
+
+#### `github_release`
+
+Create a GitHub release from the tag:
 
 ```bash
-gh release create vX.Y.Z --title "vX.Y.Z — [release name]" --generate-notes --notes-start-tag <previous-tag>
+gh release create <tag-name> --title "<tag-name> — [release name]" --generate-notes --notes-start-tag <previous-tag>
 ```
 
 For the first release (no previous tag), write notes manually with `--notes "..."` instead.
 
+#### `npm_publish`
+
+Publish the package to npm with the appropriate dist-tag:
+
+```bash
+# Alpha pre-release (version contains -alpha):
+npm publish --access public --tag alpha
+
+# Beta pre-release (version contains -beta):
+npm publish --access public --tag beta
+
+# Stable release (no pre-release suffix, >= 1.0.0):
+npm publish --access public
+```
+
+The dist-tag is derived from the version string in `package.json`:
+- Contains `-alpha` → `--tag alpha`
+- Contains `-beta` → `--tag beta`
+- No pre-release suffix → no `--tag` flag (publishes to `latest`)
+
+#### Other values
+
+If `on_green` contains an action not listed above, log it:
+
+```
+[releasing] Action "<action>" is configured but not yet implemented. Skipping.
+```
+
+If `on_green` is empty or absent: skip post-push actions entirely.
+
 ### 8. Complete Active Intent
 
 A release IS a delivery. The active intent that drove this work must be completed as part of the release process. This is NOT optional.
@@ -100,19 +179,37 @@ A release IS a delivery. The active intent that drove this work must be complete
    c. Update `## Insights` with final observations
    d. Move from `## Active` to `## Completed` in INDEX.md (with today's date)
    e. Update clusters to show `_(completed)_`
-3. Auto-commit: `cd ~/.plastic && git add . && git commit -m "feat: complete intent <ID> — delivered in v<X.Y.Z>"`
+3. Auto-commit: `cd ~/.plastic && git add . && git commit -m "feat: complete intent <ID> — delivered in <tag-name>"`
 
 **If no active intent exists for this release**, that itself is a problem — work happened outside the intent system. Log it and move on, but flag it.
 
 ## Conventions
 
 - **Annotated tags only** — `git tag -a`, never lightweight tags
-- **Tag format** — `vX.Y.Z` (lowercase v prefix)
-- **Tag message** — first line: `vX.Y.Z — [short name]`, then blank line, then bullet changelog
+- **Tag format** — driven by `release.tag_format` in project.yml (default: `vX.Y.Z`)
+- **Tag message** — first line: `<tag> — [short name]`, then blank line, then bullet changelog
 - **Commit prefixes** — `feat:`, `fix:`, `refactor:`, `chore:`, `docs:` (conventional commits)
-- **Version files** — package.json, plugin.json, and marketplace.json always match
+- **Version files** — driven by project.yml; all listed files must always match
 - **Branch cleanup** — delete merged feature branches: `git branch -d <branch>`
 
+## Promotion
+
+To promote a release across channels, use `--promote`:
+
+```bash
+plastic-releasing --promote beta    # promotes current alpha → beta
+plastic-releasing --promote stable  # promotes current beta → stable
+```
+
+**Promotion rules:**
+- Linear only: alpha → beta → stable. Cannot skip channels.
+- `--promote beta`: reads version from `package.json`, changes `-alpha.N` suffix
+  to `-beta.1`, publishes with `--tag beta`.
+- `--promote stable`: reads version from `package.json`, strips pre-release suffix
+  entirely (e.g., `1.0.0-beta.3` → `1.0.0`), publishes to `latest`.
+- Version files are bumped and committed as in a normal release.
+- An annotated tag is created for the promoted version.
+
 ## Retroactive Tagging
 
 For repos without prior tags, tag historical releases:
@@ -122,3 +219,7 @@ git tag -a v0.1.0 <commit-sha> -m "v0.1.0 — [description]"
 ```
 
 Use `git log --oneline` to find the right commits (look for version bump commits or major feature merges).
+
+## References
+
+- Read `references/deprecations.md` for the full deprecation process, severity levels, deprecations.yml schema, and dismissal rules when adding or managing deprecations

package/skills/releasing/references/deprecations.md

@@ -0,0 +1,60 @@
+# Deprecation Process
+
+When removing a feature, changing a convention, or making a breaking change:
+
+1. Add entry to `deprecations.yml` in the Plastic source root
+2. Set severity: `info` (awareness), `warning` (action needed), `critical` (urgent)
+3. Provide clear migration steps
+4. Set `removal` version at least 2 minor versions ahead
+5. SessionStart hook displays active deprecations automatically
+6. Remove the feature AND the deprecation entry together
+
+## Pre-1.0 removal policy
+
+The numbered process above is the steady-state rule: a deprecation rides until its `removal`
+version, which step 4 sets at least two minors ahead. While Plastic is still pre-1.0 (any
+version below `1.0.0`), one exception applies:
+
+- **Pre-1.0 exception.** Before `1.0.0`, a *satisfied* deprecation (the migration it
+  announced is complete on installed machines) may be removed immediately, rather than waiting
+  for its declared `removal` major. Delete the entry from `deprecations.yml` (leaving
+  `deprecations: []` if it was the last one) the moment the migration is done.
+
+This exception only holds below `1.0.0`. From `1.0.0` onward, the steady-state grace rule
+(step 4, removal at least two minors ahead) governs again, unchanged. The exception narrows
+*when* a satisfied entry may be pulled early during the pre-release line; it does not loosen
+the grace window for the released-product contract.
+
+## Severity Levels
+
+| Severity | When to use | Dismissable? |
+|----------|-------------|--------------|
+| `info` | Upcoming change | Yes |
+| `warning` | Action needed | Yes (re-shown at removal) |
+| `critical` | Urgent/security | Never |
+
+## deprecations.yml Schema
+
+```yaml
+deprecations:
+  - id: unique-slug
+    severity: info | warning | critical
+    summary: "One-line description"
+    migration_steps:
+      - "Step 1"
+      - "Step 2"
+    introduced: "0.9.0"
+    removal: "1.0.0"
+    link: "optional URL"
+```
+
+## Dismissal
+
+Users dismiss by adding the id to `deprecations_dismissed` in `config.yml`:
+
+```yaml
+deprecations_dismissed:
+  - some-deprecated-feature
+```
+
+Critical deprecations and final-version warnings ignore dismissal.

package/skills/research/SKILL.md

@@ -0,0 +1,114 @@
+---
+name: plastic-research
+description: "Research a topic for the active intent. Agent decides shallow vs deep based on scope. Produces reports in the intent's resources/ directory."
+---
+
+# Research
+
+Investigate a topic related to the active intent. Choose the right depth, produce a cited report.
+
+**Announce at start:** "I'm researching [topic] for intent {id} — {name}."
+
+## Active Intent Gate
+
+Before proceeding, resolve the active intent:
+
+1. **Detect store:** Read `~/.plastic/projects.yml`, match CWD against registered project paths. If match → project store at `~/.plastic/projects/{slug}/store/`. If no match → global store at `~/.plastic/store/`.
+2. **Find active intent:** Read `INDEX.md` from the detected store. Look under `## Active`. If exactly one → use it. If multiple → ask which. If none → refuse: "No active intent. Create one first with /plastic-creating-intent"
+3. **Resolve intent directory:** `{store}/store/{id}--{slug}/`
+
+## Depth Decision
+
+Before starting research, assess the question against these criteria:
+
+### Shallow Research
+Use when:
+- The question is narrow and factual (e.g., "what's the API for X?", "does library Y support Z?")
+- A single source or quick search is sufficient
+- The answer is likely well-documented
+- Time budget: minutes, not hours
+
+**Method:** Direct web search + codebase exploration + single-pass synthesis.
+
+### Deep Research
+Use when:
+- The question needs multiple sources and cross-verification
+- It's a landscape survey, competitive analysis, or architectural decision
+- The user explicitly asks for thorough/exhaustive/comprehensive research
+- Conflicting information exists and needs adversarial verification
+- Time budget: significant, user expects depth
+
+**Method:** Delegate to the native agent's deep research capability.
+- On Claude Code: invoke the `deep-research` skill via `Skill` tool
+- On other agents: use the agent's equivalent (see intent 7 for cross-agent mapping)
+- If no native deep research exists: fan out multiple web searches manually, cross-reference, synthesize
+
+### Decision Heuristic
+
+Ask yourself:
+1. Can I answer this with 1-2 searches? → **Shallow**
+2. Do I need to compare 3+ sources? → **Deep**
+3. Is the user asking for a survey or landscape view? → **Deep**
+4. Am I fact-checking a specific claim? → **Shallow**
+5. Could wrong information here cause architectural mistakes? → **Deep**
+
+Announce your choice: "This needs [shallow/deep] research because [reason]."
+
+## Output
+
+### File Location
+`{intent_dir}/resources/{type}--{topic}.md`
+
+Create the resources/ directory if it doesn't exist.
+
+### Naming Convention
+- `{type}` — one of: `deep-research`, `competitive-analysis`, `technical-spike`, `reference`, `landscape-survey`
+- `{topic}` — kebab-case description of the research subject
+
+Examples:
+- `deep-research--installer-patterns.md`
+- `technical-spike--sqlite-vec-performance.md`
+- `reference--claude-code-hooks-api.md`
+- `landscape-survey--ai-agent-ecosystem.md`
+
+### Report Structure
+
+```markdown
+# {Type}: {Topic}
+
+**Intent:** {id} — {name}
+**Depth:** shallow | deep
+**Date:** YYYY-MM-DD
+
+## Summary
+[2-3 sentence executive summary]
+
+## Findings
+
+### [Finding 1 title]
+[Details with inline citations where applicable]
+
+### [Finding 2 title]
+...
+
+## Sources
+- [Source 1 title](url) — what was learned from this source
+- [Source 2 title](url) — ...
+
+## Relevance to Intent
+[How these findings affect the active intent's decisions or design]
+```
+
+## After Research
+
+1. Commit to store repo:
+   ```
+   cd {store_root} && git add . && git commit -m "research: {type} — {topic} (intent {id})"
+   ```
+
+2. Log in intent's `## Insights`:
+   ```
+   - Research: {type} — {topic}. Key finding: [one sentence]. See resources/{filename}.
+   ```
+
+3. Research does NOT chain to any other skill. It's a side quest — the user decides what to do with the findings.