elliot-stack 1.0.10 → 1.0.12

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "elliot-stack",
-  "version": "1.0.10",
+  "version": "1.0.12",
   "description": "Elliot's skill stack for Claude Code — install via npx elliot-stack@latest",
   "bin": {
     "elliot-stack": "bin/install.cjs"

package/skills/estack-better-title/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: estack-better-title
-description: (estack-better-title) Suggest better chat session titles and rename the session
+description: (better-title) Suggest better chat session titles and rename the session
 disable-model-invocation: true
 allowed-tools: Bash, AskUserQuestion
 ---

package/skills/estack-chris-voss/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: estack-chris-voss
 description: >
-  (estack-chris-voss) Applies Chris Voss negotiation principles from *Never Split the Difference* to any situation
+  (chris-voss) Applies Chris Voss negotiation principles from *Never Split the Difference* to any situation
   where understanding human psychology, persuasion, or influence would improve the output. Use
   when the user is navigating a situation involving another person, drafting communication that
   needs to land a certain way, or asking for advice on how to approach a difficult conversation —

package/skills/estack-customer-discovery/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: estack-customer-discovery
-description: (estack-customer-discovery) Guide users through customer discovery — validating business ideas, identifying target customers, crafting outreach, preparing interview questions, and analyzing interview results. Use this skill whenever the user mentions customer discovery, customer interviews, validating an idea, market research, finding product-market fit, talking to customers, outreach messages, interview guides, or analyzing customer feedback. Also use when someone says they have a business idea and want to test it, or when they're preparing to talk to potential customers.
+description: (customer-discovery) Guide users through customer discovery — validating business ideas, identifying target customers, crafting outreach, preparing interview questions, and analyzing interview results. Use this skill whenever the user mentions customer discovery, customer interviews, validating an idea, market research, finding product-market fit, talking to customers, outreach messages, interview guides, or analyzing customer feedback. Also use when someone says they have a business idea and want to test it, or when they're preparing to talk to potential customers.
 ---
 
 # Customer Discovery
@@ -28,16 +28,22 @@ If they describe their situation without picking a step, route them based on whe
 - Have interviews scheduled but need questions → **Step 3: Interview Execution**
 - Have done interviews and need to make sense of them → **Step 4: Analysis & Signals**
 
-### Step 2: Read the right step file
+### Step 2: Read the right step file — MANDATORY
 
-Each step has its own workflow file with detailed instructions. Read the one you need:
+<CRITICAL>
+You MUST read the step file AND its corresponding reference file BEFORE responding to the user. Do NOT skip this. These files contain the actual frameworks and instructions — without reading them, your output will be generic and wrong.
+</CRITICAL>
 
-- **Step 1: Strategy & Targeting** → Read `steps/step-1-strategy.md`
-- **Step 2: Outreach** → Read `steps/step-2-outreach.md`
-- **Step 3: Interview Execution** → Read `steps/step-3-interviews.md`
-- **Step 4: Analysis & Signals** → Read `steps/step-4-analysis.md`
+Each step has its own workflow file with detailed instructions. **Read the step file first, then read the reference file it points to.** Both reads are required — not optional, not "if you have time."
 
-The step file will tell you to also read the corresponding reference document. The reference docs are the source of truth — they contain the principles and frameworks. The step files tell you how to work through them with the user.
+| Step | Step file (read first) | Reference file (read second) |
+|---|---|---|
+| 1. Strategy & Targeting | `steps/step-1-strategy.md` | `references/01-strategy-and-targeting.md` |
+| 2. Outreach | `steps/step-2-outreach.md` | `references/02-outreach.md` |
+| 3. Interview Execution | `steps/step-3-interviews.md` | `references/03-interview-execution.md` |
+| 4. Analysis & Signals | `steps/step-4-analysis.md` | `references/04-analysis-and-signals.md` |
+
+The reference docs are the source of truth — they contain the principles and frameworks. The step files tell you how to work through them with the user.
 
 ### Step 3: Be adaptive
 

package/skills/estack-customer-discovery/steps/step-1-strategy.md

@@ -1,8 +1,10 @@
 # Step 1: Strategy & Targeting
 
-## Before anything else
+## Before anything else — BLOCKING REQUIREMENT
 
-Read `references/01-strategy-and-targeting.md` in the skill directory. That's your source of truth for this step. Internalize it before working with the user.
+<CRITICAL>
+You MUST read `references/01-strategy-and-targeting.md` BEFORE responding to the user. Do NOT skip this. This file contains the actual frameworks and instructions — without reading it, your output will be generic and wrong.
+</CRITICAL>
 
 ## What this step accomplishes
 

package/skills/estack-customer-discovery/steps/step-2-outreach.md

@@ -1,8 +1,10 @@
 # Step 2: Outreach
 
-## Before anything else
+## Before anything else — BLOCKING REQUIREMENT
 
-Read `references/02-outreach.md` in the skill directory. That's your source of truth for this step.
+<CRITICAL>
+You MUST read `references/02-outreach.md` BEFORE responding to the user. Do NOT skip this. This file contains the actual frameworks and instructions — without reading it, your output will be generic and wrong.
+</CRITICAL>
 
 ## What this step accomplishes
 

package/skills/estack-customer-discovery/steps/step-3-interviews.md

@@ -1,8 +1,10 @@
 # Step 3: Interview Execution
 
-## Before anything else
+## Before anything else — BLOCKING REQUIREMENT
 
-Read `references/03-interview-execution.md` in the skill directory. That's your source of truth for this step.
+<CRITICAL>
+You MUST read `references/03-interview-execution.md` BEFORE responding to the user. Do NOT skip this. This file contains the actual frameworks and instructions — without reading it, your output will be generic and wrong.
+</CRITICAL>
 
 ## What this step accomplishes
 

package/skills/estack-customer-discovery/steps/step-4-analysis.md

@@ -1,8 +1,10 @@
 # Step 4: Analysis & Signals
 
-## Before anything else
+## Before anything else — BLOCKING REQUIREMENT
 
-Read `references/04-analysis-and-signals.md` in the skill directory. That's your source of truth for this step.
+<CRITICAL>
+You MUST read `references/04-analysis-and-signals.md` BEFORE responding to the user. Do NOT skip this. This file contains the actual frameworks and instructions — without reading it, your output will be generic and wrong.
+</CRITICAL>
 
 ## What this step accomplishes
 

package/skills/estack-github-issue-tracker/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: estack-github-issue-tracker
 description: >
-  (estack-github-issue-tracker) GitHub issue tracker management. Checks all open issues the user is involved in,
+  (github-issue-tracker) GitHub issue tracker management. Checks all open issues the user is involved in,
   finds related/duplicate issues, reports what changed, and recommends next steps.
   Run anytime for a check-in — works the same whether it's the first run or a daily habit.
   The tracker file acts as a cache to make repeat runs faster.

package/skills/estack-repo-search/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: estack-repo-search
 description: >-
-  (estack-repo-search) Clone and search external GitHub repositories to answer questions about their
+  (repo-search) Clone and search external GitHub repositories to answer questions about their
   code. Use this skill whenever the user references a repo you don't have local
   context for, asks about code in an external project, wants to compare
   implementations across repos, or needs information from a codebase that isn't