@winton979/task-cli 1.4.3 → 1.5.0

package/README.md

@@ -82,17 +82,13 @@ task init
 
 After initialization, Task CLI creates the `.ai/` workspace and installs workflow skills into both `.claude/skills/` and `.codex/skills/`.
 
-### Prerequisites
-
-Task CLI can use a Grill Me compatible skill for requirement and bug exploration.
-
-Recommended:
-
-```bash
-npx add-skill PJ-SBN-593844/skill-grill-me
-```
-
-If no Grill Me compatible skill is installed, `task-fast`, `task-explore`, and `bug-explore` fall back to built-in clarification prompts.
+### Exploration Protocol
+
+Task CLI embeds the `grilling` primitive from [Matt Pocock's skills collection](https://github.com/mattpocock/skills.git). Its wording is the methodological foundation for exploration, not a runtime dependency.
+
+`task-explore` and `bug-explore` preserve the primitive's body verbatim. Their only workflow-specific interpretation of it is that "act on it" means creating the brief. `task-fast` uses a narrower clarification loop so the fast path remains fast.
+
+Task CLI neither requires nor installs a companion interviewing skill.
 
 ---
 
@@ -314,13 +310,7 @@ This will:
 
 Unrelated custom skills in the same project are left untouched. Inspect the current setup first with `task doctor`.
 
----
-
-something else:
-> Task CLI does not install Grill Me automatically.
-> Users remain free to choose any Grill Me compatible implementation, and the explore skills fall back to built-in clarification if none is installed.
-
-## License
+## License
 
 MIT
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@winton979/task-cli",
-  "version": "1.4.3",
+  "version": "1.5.0",
   "description": "Lightweight task workflow CLI for AI-assisted development",
   "license": "MIT",
   "repository": {

package/src/init.js

@@ -13,11 +13,15 @@ const GITIGNORE_BLOCK = [
   '.ai/bugs/active/*.md',
 ].join('\n');
 
-const GRILL_ME_HINTS = [
-  'grill-me',
-  'skill-grill-me',
-  'grill me',
-];
+const GRILLING_GUIDANCE = `Grilling
+
+Interview me relentlessly about every aspect of this until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
+
+Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.
+
+If a *fact* can be found by exploring the environment (filesystem, tools, etc.), look it up rather than asking me. The *decisions*, though, are mine — put each one to me and wait for my answer.
+
+Do not act on it until I confirm we have reached a shared understanding.`;
 
 const DECISIONS_READ_GUIDANCE = `Decision Intake
 
@@ -60,23 +64,24 @@ Handle a small requirement in one continuous workflow with minimal ceremony.
 
 Workflow
 
-1. If a Grill Me compatible skill is available in the current environment, use it for requirement clarification.
-2. If no Grill Me compatible skill is available, clarify the requirement yourself with focused questions just far enough to remove ambiguity.
-3. Read the project code and conventions needed to avoid obvious conflicts.
-4. Read .ai/decisions/decisions.md if it exists and has entries. Pull in only decisions that materially constrain this task.
-5. Before finalizing the brief, perform a Complexity Assessment.
-6. Create a concise task brief and save it to:
+1. Read the project code and conventions needed to avoid obvious conflicts.
+2. If a fact can be found by exploring the environment, look it up rather than asking the user.
+3. Ask only questions whose answers can change the implementation or acceptance criteria. Ask them one at a time, waiting for feedback on each before continuing. For each question, provide your recommended answer.
+4. Put unresolved decisions to the user; do not make them on the user's behalf.
+5. Read .ai/decisions/decisions.md if it exists and has entries. Pull in only decisions that materially constrain this task.
+6. Before finalizing the brief, perform a Complexity Assessment.
+7. Create a concise task brief and save it to:
 
 .ai/tasks/active/YYYY-MM-DD-task-name.md
 
-7. Show the brief before coding.
-8. If the user does not object, implement immediately.
-9. Verify the result against the acceptance criteria.
-10. Archive the brief automatically by moving it to:
+8. Show the brief as the fast-path summary of shared understanding, ask the user to confirm it, and stop. Do not code until the user confirms.
+9. Once the user confirms the brief, implement immediately.
+10. Verify the result against the acceptance criteria.
+11. Archive the brief automatically by moving it to:
 
 .ai/tasks/archive/YYYY-MM-DD-task-name.md
 
-11. Summarize the outcome and any follow-up risks.
+12. Summarize the outcome and any follow-up risks.
 
 ${DECISIONS_READ_GUIDANCE}
 
@@ -123,10 +128,10 @@ TASK_DONE
 
   'task-explore': {
     name: 'task-explore',
-    description: 'Clarify a requirement and generate the execution brief in one step, without implementing.',
+    description: 'Grill the user relentlessly about a requirement; generate an execution brief only after shared understanding, without implementing.',
     content: `---
 name: task-explore
-description: Clarify a requirement and generate the execution brief in one step, without implementing.
+description: Grill the user relentlessly about a requirement; generate an execution brief only after shared understanding, without implementing.
 user-invocable: true
 ---
 
@@ -136,17 +141,17 @@ Clarify requirements and leave behind a ready-to-execute brief.
 
 Workflow
 
-1. If a Grill Me compatible skill is available in the current environment, use it for requirement exploration.
-2. If no Grill Me compatible skill is available, explore the requirement yourself through focused questions.
-3. Continue until the task is sufficiently understood.
-4. Do not write code.
-5. Do not create implementation details.
-6. Before writing the brief, inspect .ai/decisions/decisions.md if it exists and has entries. Pull in only decisions that materially constrain this task.
-7. Once the requirement is clear, generate a concise task brief and save it to:
+1. Grill the requirement using the Grilling section below.
+2. Do not write code or create implementation details.
+3. Before writing the brief, inspect .ai/decisions/decisions.md if it exists and has entries. Pull in only decisions that materially constrain this task.
+4. For this workflow, "act on it" means creating the brief.
+5. Generate a concise task brief and save it to:
 
 .ai/tasks/active/YYYY-MM-DD-task-name.md
 
-8. Show the saved brief and stop.
+6. Show the saved brief and stop.
+
+${GRILLING_GUIDANCE}
 
 ${DECISIONS_READ_GUIDANCE}
 
@@ -358,10 +363,10 @@ TASK_CANCELLED
 
   'bug-explore': {
     name: 'bug-explore',
-    description: 'Investigate a bug and generate a fix brief in one step, without writing code.',
+    description: 'Grill the user relentlessly about a bug while investigating its evidence; generate a fix brief only after shared understanding, without writing code.',
     content: `---
 name: bug-explore
-description: Investigate a bug and generate a fix brief in one step, without writing code.
+description: Grill the user relentlessly about a bug while investigating its evidence; generate a fix brief only after shared understanding, without writing code.
 user-invocable: true
 ---
 
@@ -371,24 +376,24 @@ Investigate a bug and leave behind a ready-to-fix brief.
 
 Rules
 
-1. If a Grill Me compatible skill is available in the current environment, use it for bug exploration.
-2. If no Grill Me compatible skill is available, ask focused questions and drive the investigation yourself.
-3. Do not write code.
-4. Do not suggest fixes before enough evidence exists.
-5. Identify root cause candidates.
-6. Request evidence whenever possible.
-7. Separate:
+1. Grill the bug using the Grilling section below.
+2. Investigate the bug and gather reproducible evidence. Do not write code or suggest fixes before enough evidence exists.
+3. Identify root cause candidates.
+4. Separate:
 
    * observed behavior
    * expected behavior
    * assumptions
 
-8. Before writing the brief, inspect .ai/decisions/decisions.md if it exists and has entries. Pull in only decisions that materially constrain the observed behavior, expected behavior, or likely root cause.
-9. Once the bug is sufficiently understood, generate a brief and save it to:
+5. Before writing the brief, inspect .ai/decisions/decisions.md if it exists and has entries. Pull in only decisions that materially constrain the observed behavior, expected behavior, or likely root cause.
+6. For this workflow, "act on it" means creating the brief.
+7. Generate a brief and save it to:
 
 .ai/bugs/active/YYYY-MM-DD-bug-name.md
 
-10. Show the saved brief and stop.
+8. Show the saved brief and stop.
+
+${GRILLING_GUIDANCE}
 
 ${DECISIONS_READ_GUIDANCE}
 
@@ -803,49 +808,6 @@ function skillFilePath(path, cwd, skillRoot, skillName) {
   return path.join(cwd, skillRoot, skillName, 'SKILL.md');
 }
 
-function hasGrillMeHint(value) {
-  const normalized = value.toLowerCase();
-  return GRILL_ME_HINTS.some((hint) => normalized.includes(hint));
-}
-
-function detectLocalGrillMeSkill(fs, path, cwd, skillRoot) {
-  const root = path.join(cwd, skillRoot);
-  if (!fs.existsSync(root)) {
-    return null;
-  }
-
-  for (const entry of fs.readdirSync(root, { withFileTypes: true })) {
-    if (!entry.isDirectory()) {
-      continue;
-    }
-
-    if (MANAGED_SKILL_NAMES.includes(entry.name)) {
-      continue;
-    }
-
-    if (hasGrillMeHint(entry.name)) {
-      return entry.name;
-    }
-
-    const skillPath = path.join(root, entry.name, 'SKILL.md');
-    if (!fs.existsSync(skillPath)) {
-      continue;
-    }
-
-    const content = fs.readFileSync(skillPath, 'utf-8');
-    const metadata = content
-      .split('---')
-      .slice(1, 2)
-      .join('\n');
-
-    if (hasGrillMeHint(metadata)) {
-      return entry.name;
-    }
-  }
-
-  return null;
-}
-
 function logCheck(log, ok, label, detail) {
   if (ok) {
     log.chalk.green(`  OK   ${label}${detail ? ` - ${detail}` : ''}`);
@@ -1056,22 +1018,6 @@ export function doctor(cwd, { fs, path, log }) {
     }
   }
 
-  const grillMeFindings = [
-    [CLAUDE_SKILLS_DIR, detectLocalGrillMeSkill(fs, path, cwd, CLAUDE_SKILLS_DIR)],
-    [CODEX_SKILLS_DIR, detectLocalGrillMeSkill(fs, path, cwd, CODEX_SKILLS_DIR)],
-  ];
-
-  for (const [skillRoot, skillName] of grillMeFindings) {
-    if (skillName) {
-      logCheck(log, true, `${skillRoot} Grill Me companion`, `detected ${skillName}`);
-      continue;
-    }
-
-    console.log(chalk.yellow(
-      `  WARN ${skillRoot} Grill Me companion - not detected locally; task-fast, task-explore, and bug-explore will use built-in clarification fallback`
-    ));
-  }
-
   const gitignorePath = path.join(cwd, '.gitignore');
   const gitignore = fs.existsSync(gitignorePath)
     ? fs.readFileSync(gitignorePath, 'utf-8')