@zalom/plastic 1.0.0-alpha.5 → 1.0.0-alpha.7

package/scripts/hook-session-start

@@ -172,7 +172,14 @@ exit 0 if all_active.empty? && stale.empty? && all_future.empty? && active_depre
 parts = []
 
 if current_project
-  parts << "PLASTIC — Global store | Project: #{current_project["slug"]} (#{current_project["path"]})\n"
+  slug = current_project["slug"]
+  banner = "Project: #{slug} | Store: ~/.plastic/projects/#{slug}/store/"
+  if project_active.any? && project_active.first =~ /\[([^\]]+)\].*store\/([\w-]+)\//
+    intent_name, dir_name = $1, $2
+    intent_id = dir_name.split("--").first
+    banner += "\nActive: [#{intent_id} — #{intent_name}] | Artifacts → store/#{dir_name}/"
+  end
+  parts << banner + "\n"
 else
   parts << "PLASTIC — Global store loaded from ~/.plastic/\n"
 end

package/scripts/install.rb

@@ -153,6 +153,7 @@ def distribute(mode)
     "scripts/hook-future-intent-check" => "scripts/hook-future-intent-check",
     "scripts/hook-gate-check" => "scripts/hook-gate-check",
     "scripts/lib/bridge.rb" => "scripts/lib/bridge.rb",
+    "scripts/doctor.rb" => "scripts/doctor.rb",
   }
 
   core_files.each do |src, dest|

package/skills/_active-intent-gate.md

@@ -0,0 +1,26 @@
+## 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` for intent entries
+   - If exactly one active intent → use it
+   - If multiple active intents → ask user which one
+   - If no active intent → refuse: "No active intent. Create one first with /plastic:creating-intent"
+
+3. **Resolve paths:**
+   - Intent directory: `{store}/store/{id}--{slug}/`
+   - Spec: `{intent_dir}/spec.md`
+   - Plan: `{intent_dir}/plan.md`
+   - Checklist: `{intent_dir}/checklist.md`
+   - Resources: `{intent_dir}/resources/`
+   - Outcome: `{intent_dir}/outcome.md`
+
+All lifecycle artifacts MUST be written to the intent directory. Never write to `docs/superpowers/specs/`, `docs/superpowers/plans/`, or any other external path.

package/skills/brainstorming/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: plastic:brainstorming
+description: "Explore intent requirements and design before implementation. Produces spec.md in the active intent directory."
+---
+
+# Brainstorming Ideas Into Designs
+
+Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
+
+Announce: "I'm using the brainstorming skill to explore the design for intent {id} — {name}."
+
+Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.
+
+<HARD-GATE>
+Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity.
+</HARD-GATE>
+
+## 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}/`
+
+All artifacts go to the intent directory. Never write to external paths.
+
+## Anti-Pattern: "This Is Too Simple To Need A Design"
+
+Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.
+
+## Checklist
+
+You MUST create a task for each of these items and complete them in order:
+
+1. **Explore project context** — check files, docs, recent commits, read active intent
+2. **Ask clarifying questions** — one at a time, understand purpose/constraints/success criteria
+3. **Propose 2-3 approaches** — with trade-offs and your recommendation
+4. **Present design** — in sections scaled to their complexity, get user approval after each section
+5. **Write spec** — save to `{intent_dir}/spec.md` and commit to store repo
+6. **Spec self-review** — placeholder scan, consistency, scope, ambiguity
+7. **User reviews written spec** — ask user to review before proceeding
+8. **Transition to planning** — invoke `plastic:writing-plans`
+
+## Process Flow
+
+```dot
+digraph brainstorming {
+    "Explore project context" [shape=box];
+    "Ask clarifying questions" [shape=box];
+    "Propose 2-3 approaches" [shape=box];
+    "Present design sections" [shape=box];
+    "User approves design?" [shape=diamond];
+    "Write spec" [shape=box];
+    "Spec self-review\n(fix inline)" [shape=box];
+    "User reviews spec?" [shape=diamond];
+    "Invoke plastic:writing-plans" [shape=doublecircle];
+
+    "Explore project context" -> "Ask clarifying questions";
+    "Ask clarifying questions" -> "Propose 2-3 approaches";
+    "Propose 2-3 approaches" -> "Present design sections";
+    "Present design sections" -> "User approves design?";
+    "User approves design?" -> "Present design sections" [label="no, revise"];
+    "User approves design?" -> "Write spec" [label="yes"];
+    "Write spec" -> "Spec self-review\n(fix inline)";
+    "Spec self-review\n(fix inline)" -> "User reviews spec?";
+    "User reviews spec?" -> "Write spec" [label="changes requested"];
+    "User reviews spec?" -> "Invoke plastic:writing-plans" [label="approved"];
+}
+```
+
+**The terminal state is invoking `plastic:writing-plans`.** Do NOT invoke any other implementation skill. The ONLY skill you invoke after brainstorming is `plastic:writing-plans`.
+
+## The Process
+
+**Understanding the idea:**
+- Check out the current project state first (files, docs, recent commits)
+- Before asking detailed questions, assess scope: if the request describes multiple independent subsystems (e.g., "build a platform with chat, file storage, billing, and analytics"), flag this immediately. Don't spend questions refining details of a project that needs to be decomposed first.
+- If the project is too large for a single spec, help the user decompose into sub-projects: what are the independent pieces, how do they relate, what order should they be built? Then brainstorm the first sub-project through the normal design flow. Each sub-project gets its own spec → plan → implementation cycle.
+- For appropriately-scoped projects, ask questions one at a time to refine the idea
+- Prefer multiple choice questions when possible, but open-ended is fine too
+- Only one question per message - if a topic needs more exploration, break it into multiple questions
+- Focus on understanding: purpose, constraints, success criteria
+
+**Exploring approaches:**
+- Propose 2-3 different approaches with trade-offs
+- Present options conversationally with your recommendation and reasoning
+- Lead with your recommended option and explain why
+
+**Presenting the design:**
+- Once you believe you understand what you're building, present the design
+- Scale each section to its complexity: a few sentences if straightforward, up to 200-300 words if nuanced
+- Ask after each section whether it looks right so far
+- Cover: architecture, components, data flow, error handling, testing
+- Be ready to go back and clarify if something doesn't make sense
+
+**Design for isolation and clarity:**
+- Break the system into smaller units that each have one clear purpose, communicate through well-defined interfaces, and can be understood and tested independently
+- For each unit, you should be able to answer: what does it do, how do you use it, and what does it depend on?
+- Can someone understand what a unit does without reading its internals? Can you change the internals without breaking consumers? If not, the boundaries need work.
+- Smaller, well-bounded units are also easier for you to work with - you reason better about code you can hold in context at once, and your edits are more reliable when files are focused. When a file grows large, that's often a signal that it's doing too much.
+
+**Working in existing codebases:**
+- Explore the current structure before proposing changes. Follow existing patterns.
+- Where existing code has problems that affect the work (e.g., a file that's grown too large, unclear boundaries, tangled responsibilities), include targeted improvements as part of the design - the way a good developer improves code they're working in.
+- Don't propose unrelated refactoring. Stay focused on what serves the current goal.
+
+## After the Design
+**Documentation:**
+- Write the validated design (spec) to `{intent_dir}/spec.md`
+- Use elements-of-style:writing-clearly-and-concisely skill if available
+- Commit to the store repo:
+  ```
+  cd {store_root} && git add . && git commit -m "docs: spec for intent {id} — {name}"
+  ```
+
+**Spec Self-Review:**
+After writing the spec document, look at it with fresh eyes:
+1. **Placeholder scan:** Any "TBD", "TODO", incomplete sections, or vague requirements? Fix them.
+2. **Internal consistency:** Do any sections contradict each other? Does the architecture match the feature descriptions?
+3. **Scope check:** Is this focused enough for a single implementation plan, or does it need decomposition?
+4. **Ambiguity check:** Could any requirement be interpreted two different ways? If so, pick one and make it explicit.
+
+Fix any issues inline. No need to re-review — just fix and move on.
+
+**User Review Gate:**
+After the spec review loop passes, ask the user to review the written spec before proceeding:
+> "Spec written and committed to `{intent_dir}/spec.md`. Please review it and let me know if you want to make any changes before we start writing out the implementation plan."
+
+Wait for the user's response. If they request changes, make them and re-run the spec review loop. Only proceed once the user approves.
+
+**Implementation:**
+- Invoke `plastic:writing-plans` to create the implementation plan
+- Do NOT invoke any other skill. `plastic:writing-plans` is the next step.
+
+## Key Principles
+
+- **One question at a time** - Don't overwhelm with multiple questions
+- **Multiple choice preferred** - Easier to answer than open-ended when possible
+- **YAGNI ruthlessly** - Remove unnecessary features from all designs
+- **Explore alternatives** - Always propose 2-3 approaches before settling
+- **Incremental validation** - Present design, get approval before moving on
+- **Be flexible** - Go back and clarify when something doesn't make sense

package/skills/doctor/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: doctor
+description: Use when diagnosing Plastic installation health, after updates, or when something seems broken. Runs checks and reports findings with fix options.
+---
+
+# Doctor — Plastic Health Check
+
+## When to Use
+
+- User invokes `/plastic:doctor`
+- After `plastic:update` completes (automatically)
+- When hooks aren't firing, skills aren't loading, or something seems broken
+- When the user says "check plastic", "diagnose", "what's wrong with plastic"
+
+## Procedure
+
+### Step 1: Run the diagnostic script
+
+```bash
+ruby ~/.plastic/scripts/doctor.rb --agent claude
+```
+
+Replace `claude` with the current agent type if known (`codex`, `hermes`).
+
+Parse the JSON output from stdout. The script is read-only and never modifies
+files. Errors go to stderr.
+
+Exit codes indicate check results, not script failure:
+- `0` — all checks passed
+- `1` — warnings found
+- `2` — failures found
+
+All three exit codes mean the script ran successfully. Do not treat non-zero
+as an error.
+
+### Step 2: Determine overall status
+
+Read the `status` field from the JSON root:
+
+| Status | Meaning |
+|--------|---------|
+| `pass` | Everything is healthy |
+| `warn` | Warnings found but Plastic works normally |
+| `fail` | Blocking issues that prevent Plastic from operating |
+
+### Step 3: Fill the report template
+
+Read `report.md` from the same directory as this SKILL.md
+(`~/.plastic/skills/doctor/report.md` at runtime, or the plugin source
+`skills/doctor/report.md` during development).
+
+Group checks by category. For each category, list the checks with their
+status icon and message. If a check has `details`, list them as sub-items.
+
+Present the filled template to the user.
+
+### Step 4: Offer fixes (if applicable)
+
+If any checks have `fixable: true` AND status is not `pass`:
+
+1. Group fixable items by category
+2. Show what each fix would do (from `fix_hint`)
+3. Ask the user: **"Fix all / Select individually / Skip"**
+
+If no fixable issues exist, skip this step.
+
+### Step 5: Apply fixes
+
+Use the `fix_hint` value to determine the correct action:
+
+| Fix hint pattern | Agent action |
+|---|---|
+| "chmod +x on the listed files" | Run `chmod +x` on each file listed in `details` |
+| "Create missing directory" | Run `mkdir -p` on the path |
+| "Create INDEX.md with required sections" | Write INDEX.md with the 5 sections: Active, Future, Clusters, Abandoned, Completed |
+| "Add missing entries to INDEX.md" | Add orphaned intents to the appropriate INDEX.md section |
+| "Remove stale references from INDEX.md" | Edit INDEX.md to remove ghost references |
+| "Re-run installer" | Run `npx @zalom/plastic@latest --agent` |
+
+For fixes the agent cannot handle automatically, explain what the user needs
+to do manually.
+
+### Step 6: Verify
+
+After applying fixes, re-run the diagnostic script:
+
+```bash
+ruby ~/.plastic/scripts/doctor.rb --agent claude
+```
+
+Show the updated results.
+
+- If all checks pass: announce success.
+- If issues remain: explain what is still wrong and what the user can do.
+
+## Post-Update Mode
+
+When invoked from `plastic:update` (not directly by the user):
+
+1. Run the diagnostic script as in Step 1.
+2. If all checks pass: show a single line — **"Health check: all clear."**
+3. If issues are found: show the full report (Steps 3-6).
+
+This keeps the update flow clean when nothing is wrong.
+
+## Important Notes
+
+- The script is **read-only**. It inspects but never modifies files.
+  All fixes are performed by the agent using standard tools.
+- The script outputs JSON to stdout. Any diagnostic errors go to stderr.
+- Non-zero exit codes mean "issues found", not "script crashed".
+  Always parse stdout regardless of exit code.

package/skills/doctor/report.md

@@ -0,0 +1,96 @@
+# Plastic Doctor Report
+
+<!-- =======================================================================
+  AGENT INSTRUCTIONS -- How to fill this template
+  =========================================================================
+  1. Run the doctor script. It outputs JSON with check results.
+  2. Replace every {{placeholder}} below with the corresponding JSON value.
+  3. For the category sections: the template shows ONE example section.
+     Repeat that pattern for each unique category in the checks array.
+     The six known categories and their display names are:
+       global_store       -> "Global Store"
+       conventions        -> "Conventions"
+       agent_registration -> "Agent Registration"
+       core_files         -> "Core Files"
+       project_stores     -> "Project Stores"
+       deprecations       -> "Deprecations"
+  4. For each check within a category, emit one line with the status icon
+     and the check message. If the check has non-empty details, list them
+     as indented sub-items.
+  5. The "Fixable Issues" section should ONLY appear if at least one check
+     has fixable=true AND status is not "pass". Omit the entire section
+     otherwise.
+  6. Status icons (plain text, no emoji):
+       pass -> [PASS]
+       warn -> [WARN]
+       fail -> [FAIL]
+  7. The overall status icon in the header uses the same mapping.
+  8. After filling, remove all HTML comments -- they are instructions only.
+  ======================================================================= -->
+
+## {{overall_status_icon}} Overall: {{status}} -- Plastic v{{version}}
+
+Checked at: {{timestamp}}
+
+### Summary
+
+{{pass}} passed, {{warn}} warnings, {{fail}} failed -- {{total}} checks total
+
+---
+
+<!-- =====================================================================
+  CATEGORY SECTIONS
+  ======================================================================
+  Repeat the block below ONCE PER CATEGORY present in the checks array.
+  Group checks by their "category" field. Use the display name mapping
+  above for the heading. Within each category, list every check as a
+  single line: status icon + message. If a check has non-empty "details",
+  list each detail as an indented bullet beneath.
+
+  Example category section (for agent_registration with two checks):
+  ===================================================================== -->
+
+### Agent Registration
+
+- [PASS] Claude Code adapter registered
+- [FAIL] 2 hook scripts not executable
+  - ~/.claude/hooks/plastic-session-start
+  - ~/.claude/hooks/plastic-gate-check
+
+<!-- =====================================================================
+  Repeat the above pattern for each category found in the checks array.
+  Only include categories that have at least one check.
+  Order categories as they appear in the checks array.
+  ===================================================================== -->
+
+---
+
+<!-- =====================================================================
+  FIXABLE ISSUES SECTION
+  ======================================================================
+  Include this section ONLY if one or more checks have fixable=true AND
+  status is "warn" or "fail". If no fixable issues exist, omit everything
+  from the "Fixable Issues" heading through the end of the horizontal
+  rule that follows the table.
+
+  For each fixable check that is not "pass", emit one table row:
+    | status_icon | check_message | fix_hint |
+  ===================================================================== -->
+
+### Fixable Issues
+
+| Status | Issue | Fix |
+|--------|-------|-----|
+| [FAIL] | 2 hook scripts not executable | chmod +x on the listed files |
+
+<!-- =====================================================================
+  Repeat one row per fixable non-pass check.
+  ===================================================================== -->
+
+---
+
+<!-- =====================================================================
+  FOOTER -- always include this line exactly as written.
+  ===================================================================== -->
+
+Run `plastic doctor --fix` to auto-fix all fixable issues, or ask me to fix them now.

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.

package/skills/update/SKILL.md

@@ -54,13 +54,21 @@ Key changes in this version:
 Recommendation: run /clear for a clean session with all new conventions loaded.
 ```
 
-### Step 4: Commit
+### Step 4: Run health check
+
+Invoke `plastic:doctor` to verify the installation is healthy after the update.
+
+If all checks pass, show: **"Health check: all clear."**
+
+If issues are found, show the full doctor report and offer to fix any fixable items.
+
+### Step 5: Commit
 
 ```bash
 cd ~/.plastic && git add PLASTIC.md scripts/ AGENTS.md VERSION 2>/dev/null && git commit -m "chore: update Plastic core files" --allow-empty
 ```
 
-### Step 5: Clear update cache
+### Step 6: Clear update cache
 
 ```bash
 rm -f ~/.plastic/.cache/update-check.json