@longtable/provider-claude 0.1.65 → 0.1.67

package/dist/skills.js

@@ -58,8 +58,8 @@ function baseSkillSpecs(surface = "compact") {
                 "- `longtable: use editor, reviewer, methods, measurement, and voice perspectives as a panel to evaluate this manuscript section. Do not collapse disagreement too early.`",
                 "- `$longtable-methods`, `$longtable-measure`, `$longtable-theory`, `$longtable-reviewer`, or `$longtable-voice` when the researcher explicitly wants that shortcut.",
                 "- `$longtable-start` to create or continue the first research-start interview.",
-                "- `$longtable-interview` to run a structured follow-up interview after a Research Specification exists.",
-                "- `$critical-interview` for a relentless LongTable interview that sharpens a research plan, argument, method, or product decision.",
+                "- `$longtable-interview` to run a LongTable grilling interview with one high-leverage question and a recommended answer at a time.",
+                "- `$critical-interview` as a compatibility alias for `$longtable-interview`.",
                 "- `$scholar-research` for scholarly evidence recovery, citation-slot research, and legal full-text readiness.",
                 "",
                 "## Rules",
@@ -70,7 +70,7 @@ function baseSkillSpecs(surface = "compact") {
                 "- For systematic review, meta-analysis, PDF collection, full-text extraction, institutionally licensed sources, or TDM work, ensure `longtable access setup` readiness exists or surface an ACCESS CHECKPOINT before continuing.",
                 "- Access setup records capability status only. The researcher handles VPN/proxy/library/SSO login directly; LongTable must not store passwords, API keys, tokens, PDFs, or full text in setup state.",
                 "- For `$longtable-start`, use natural-language turns for the interview and reserve structured options for final Research Specification confirmation; First Research Shape is only a shorter handle/resume layer.",
-                "- For `$longtable-interview`, use option-first follow-up choices only after a usable Research Specification exists. Always include an escape hatch such as Other, free text, or one open follow-up question.",
+                "- For `$longtable-interview`, ask one relentless sharpening question at a time. State the tension, give the recommended answer, and ask the researcher to accept, revise, or reject it. Stop when remaining questions repeat the same tension without producing a new decision.",
                 "- Do not let unrelated pending Researcher Checkpoints interrupt the interview. Mention them only as separate unresolved checkpoints, and treat them as blocking only when the researcher is confirming, saving, or recording a research decision.",
                 "- If a Researcher Checkpoint is needed, ask a short structured question with meaningful options and wait for the researcher.",
                 "- If changing LongTable product language, README positioning, or checkpoint policy, ask a Meta-Decision Checkpoint first.",
@@ -103,10 +103,10 @@ function baseSkillSpecs(surface = "compact") {
         },
         {
             name: "critical-interview",
-            description: "A relentless LongTable interview to sharpen a research plan, argument, method, or product decision.",
+            description: "Compatibility alias for `$longtable-interview`.",
             triggers: ["$critical-interview", "critical interview", "research grill", "grill my research"],
             body: [
-                "Run a LongTable critical interview session. Continue only while questions sharpen the research or design; stop when remaining questions repeat the same tension without producing a new decision."
+                "Compatibility alias: run `$longtable-interview`. Do not run a separate interview contract here."
             ]
         },
         {
@@ -157,8 +157,8 @@ function baseSkillSpecs(surface = "compact") {
                 "## Required Routing",
                 "",
                 "- Use this flow when the user invokes `$longtable-start`.",
-                "- Use this flow when the user invokes `$longtable-interview` but the workspace has no usable Research Specification.",
-                "- If only a First Research Shape exists, continue into the next Research Specification question or preview before any option-only follow-up interview.",
+                "- Use this flow when the user explicitly wants a first research-start interview rather than a pressure interview.",
+                "- If only a First Research Shape exists and the researcher wants to complete startup, continue into the next Research Specification question or preview.",
                 "",
                 "## Flow",
                 "",
@@ -250,37 +250,45 @@ function baseSkillSpecs(surface = "compact") {
         },
         {
             name: "longtable-interview",
-            description: "Use for `$longtable-interview`: run an option-first LongTable follow-up interview after a usable Research Specification exists; route to `$longtable-start` when no spec exists.",
+            description: "Use for `$longtable-interview`: run a LongTable grilling interview for research plans, arguments, methods, evidence standards, manuscripts, and product decisions.",
             triggers: ["$longtable-interview", "longtable interview", "follow-up research interview", "research specification interview"],
             body: [
                 "## Purpose",
                 "",
-                "Run a post-start LongTable interview inside Claude Code. This skill is for structured follow-up decisions after the research has a usable Research Specification.",
+                "Run a LongTable grilling interview inside Claude Code. The goal is to sharpen the next research decision, not to present a questionnaire.",
                 "",
-                "## Required Routing",
+                "## Required Context",
                 "",
                 "- First inspect `CURRENT.md` and `.longtable/state.json` when available.",
-                "- If MCP `read_research_specification` is available, use its `readiness.usableForInterview` result as the gate.",
-                "- Usable means the shared readiness gate allows interview, normally a confirmed Research Specification.",
-                "- If no usable Research Specification exists, route to `$longtable-start` immediately.",
-                "- If only a First Research Shape exists, route to `$longtable-start` and continue into the next Research Specification question or preview.",
-                "- Do not run an option-only interview before the Research Specification exists.",
+                "- If MCP `read_research_specification` is available, use it as context, not as a gate.",
+                "- If the answer can be found in `CURRENT.md`, `.longtable/`, the codebase, supplied documents, or cited evidence, inspect those first instead of asking.",
+                "- Do not route away to `$longtable-start` merely because a Research Specification is missing.",
+                "- If the researcher explicitly wants a first research-start interview, use `$longtable-start`; otherwise keep the grilling interview here.",
                 "",
-                "## Flow",
+                "## When To Use",
+                "",
+                "- The user invokes `$longtable-interview`.",
+                "- The user invokes `$critical-interview`; treat it as a compatibility alias for this skill.",
+                "- The user asks for a grill-me-style, critical, pressure, or relentless interview.",
+                "- The user wants to revise, extend, or resolve a decision in an existing Research Specification.",
+                "- The user needs a pressure interview around a checkpoint, spec patch, evidence boundary, method choice, coding rule, or protected decision.",
                 "",
-                "1. Read the current Research Specification and identify the decision or section being interviewed.",
-                "2. Present a small option-first choice set tied to the current specification.",
-                "3. Include an escape hatch such as `Other`, free text, or `ask one open question first`.",
-                "4. If the answer changes the specification, propose or apply a Research Specification patch through MCP/state when available.",
-                "5. Record the resulting decision as a `DecisionRecord` or explicit open tension; never silently overwrite conflicting research commitments.",
+                "## Grilling Loop",
                 "",
-                "## Option UI Policy",
+                "- Ask one question at a time.",
+                "- Each question must expose a decision, hidden assumption, weak boundary, unsupported claim, or evidence gap.",
+                "- For each question, state the tension, give the recommended answer, and ask the researcher to accept, revise, or reject it.",
+                "- Continue only while the next question can produce a new decision, sharper boundary, stronger evidence standard, or clearer open tension.",
+                "- Stop when remaining questions repeat the same tension without producing a new decision.",
+                "",
+                "## Flow",
                 "",
-                "- Use MCP/native structured elicitation when available.",
-                "- Use terminal selector only when the runtime has interactive TTY support.",
-                "- Use numbered/plain text fallback when structured UI is unavailable.",
-                "- Treat UI as transport. The durable product contract remains `QuestionRecord -> DecisionRecord`.",
-                "- Do not require tmux. If a future Codex popup transport is tmux-only, label it as optional and provide fallback."
+                "1. Read available project state and identify the highest-leverage unresolved tension.",
+                "2. Ask exactly one question.",
+                "3. Include `Tension:`, `Recommended answer:`, and `Question:` in the prompt.",
+                "4. Ask the researcher to accept, revise, or reject the recommended answer.",
+                "5. If the answer changes the specification, propose or apply a Research Specification patch through MCP/state when available.",
+                "6. Record the resulting decision as a `DecisionRecord`, Research Specification patch, or explicit open tension when MCP/state tools are available; never silently overwrite conflicting research commitments."
             ]
         },
         {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@longtable/provider-claude",
-  "version": "0.1.65",
+  "version": "0.1.67",
   "private": false,
   "description": "Claude adapter surface for LongTable",
   "type": "module",
@@ -21,9 +21,9 @@
     "typecheck": "tsc -p tsconfig.json --noEmit"
   },
   "dependencies": {
-    "@longtable/checkpoints": "0.1.65",
-    "@longtable/core": "0.1.65",
-    "@longtable/setup": "0.1.65"
+    "@longtable/checkpoints": "0.1.67",
+    "@longtable/core": "0.1.67",
+    "@longtable/setup": "0.1.67"
   },
   "devDependencies": {
     "typescript": "^5.6.0"