@boopkit/cli 0.7.0 → 0.8.0

package/dist/capability-versions.json

@@ -8,9 +8,9 @@
   "@boopkit/cap-hello": "0.4.1",
   "@boopkit/cap-noticeboard": "0.4.1",
   "@boopkit/cap-oauth-client": "0.1.1",
-  "@boopkit/cap-oauth-server": "0.3.0",
+  "@boopkit/cap-oauth-server": "0.3.2",
   "@boopkit/cap-product-design": "0.6.11",
-  "@boopkit/cap-project-mgmt": "0.4.12",
+  "@boopkit/cap-project-mgmt": "0.4.13",
   "@boopkit/cap-services": "0.4.3",
   "@boopkit/cap-skills": "0.5.6",
   "@boopkit/cap-testing": "0.5.8",

package/dist/commands/loop.d.ts

@@ -244,6 +244,17 @@ export declare function getMatchingReadyIssues(prefix: string, includeFeatures:
         maxBuffer?: number;
     }) => string;
 }): ReadyIssue[];
+/** A skill folder in a project's skills/ directory. */
+export interface InstalledSkill {
+    name: string;
+    hasProjectFile: boolean;
+}
+/**
+ * The skills installed in a project folder: each folder under skills/ that holds
+ * a SKILL.md. statSync follows symlinks, which matters because boop's own
+ * skills/ entries are symlinks into each capability package's skills/ folder.
+ */
+export declare function readInstalledSkills(projectDir: string): InstalledSkill[];
 /**
  * The instructions every loop session starts from. A session acts on this text
  * literally and reads it whether or not it opens a skill, so step 5 carries the
@@ -251,8 +262,15 @@ export declare function getMatchingReadyIssues(prefix: string, includeFeatures:
  * when the issue asks) and names no command, because the text is the same in
  * every project and the commands are not. For the same reason it names no
  * project.
+ *
+ * Step 3 lists, as paths, the installed skills the issue names: each SKILL.md,
+ * plus the PROJECT.md beside it where there is one. Sessions open a skill they
+ * only see named about one time in seven, but read a path the prompt spells out.
+ * An issue that names no installed skill is pointed at boop-skills-discovery
+ * instead, and without `installed` (or without discovery installed) step 3 keeps
+ * the general "read relevant skills" wording.
  */
-export declare function buildPrompt(issue: IssueInfo): string;
+export declare function buildPrompt(issue: IssueInfo, installed?: InstalledSkill[]): string;
 /**
  * Default per-issue budget cap in USD. The planning phase and each task each get
  * this cap. Single source of truth — imported by cli.ts for its --budget help

package/dist/commands/loop.js

@@ -52,6 +52,7 @@ exports.isIssueInScope = isIssueInScope;
 exports.isClaimableReadyIssue = isClaimableReadyIssue;
 exports.shouldCloseFeatureRoot = shouldCloseFeatureRoot;
 exports.getMatchingReadyIssues = getMatchingReadyIssues;
+exports.readInstalledSkills = readInstalledSkills;
 exports.buildPrompt = buildPrompt;
 exports.shouldRotateSession = shouldRotateSession;
 exports.sessionDidWork = sessionDidWork;
@@ -883,6 +884,65 @@ function isIssueClosed(id) {
         return false;
     }
 }
+/**
+ * The skills installed in a project folder: each folder under skills/ that holds
+ * a SKILL.md. statSync follows symlinks, which matters because boop's own
+ * skills/ entries are symlinks into each capability package's skills/ folder.
+ */
+function readInstalledSkills(projectDir) {
+    const skillsDir = path.join(projectDir, 'skills');
+    let entries;
+    try {
+        entries = fs.readdirSync(skillsDir);
+    }
+    catch {
+        return [];
+    }
+    const skills = [];
+    for (const name of entries) {
+        const dir = path.join(skillsDir, name);
+        try {
+            if (!fs.statSync(dir).isDirectory() || !fs.existsSync(path.join(dir, 'SKILL.md')))
+                continue;
+        }
+        catch {
+            continue;
+        }
+        skills.push({ name, hasProjectFile: fs.existsSync(path.join(dir, 'PROJECT.md')) });
+    }
+    return skills;
+}
+/**
+ * The installed skills an issue description names, by bare name or by path, in
+ * the order each is first mentioned. A name only matches whole, so
+ * boop-testing-testing does not match inside boop-testing-testing-express-web.
+ */
+function namedSkills(description, installed) {
+    const found = [];
+    for (const skill of installed) {
+        const escaped = skill.name.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
+        const match = new RegExp(`(?<![\\w-])${escaped}(?![\\w-])`).exec(description);
+        if (match)
+            found.push({ skill, at: match.index });
+    }
+    return found.sort((a, b) => a.at - b.at).map((f) => f.skill);
+}
+function skillStep(issue, installed) {
+    const general = '3. Read relevant skills from skills/ (list folders, read each SKILL.md) before making changes';
+    if (!installed)
+        return general;
+    const named = namedSkills(issue.description, installed);
+    if (named.length > 0) {
+        const lines = named.map((s) => s.hasProjectFile
+            ? `   - skills/${s.name}/SKILL.md and skills/${s.name}/PROJECT.md`
+            : `   - skills/${s.name}/SKILL.md`);
+        return `3. Before making changes, read each of these in full, unless you have already read it in this session:\n${lines.join('\n')}`;
+    }
+    if (installed.some((s) => s.name === 'boop-skills-discovery')) {
+        return '3. Follow skills/boop-skills-discovery/SKILL.md to choose the skills relevant to this work, and read those skills before making changes';
+    }
+    return general;
+}
 /**
  * The instructions every loop session starts from. A session acts on this text
  * literally and reads it whether or not it opens a skill, so step 5 carries the
@@ -890,8 +950,15 @@ function isIssueClosed(id) {
  * when the issue asks) and names no command, because the text is the same in
  * every project and the commands are not. For the same reason it names no
  * project.
+ *
+ * Step 3 lists, as paths, the installed skills the issue names: each SKILL.md,
+ * plus the PROJECT.md beside it where there is one. Sessions open a skill they
+ * only see named about one time in seven, but read a path the prompt spells out.
+ * An issue that names no installed skill is pointed at boop-skills-discovery
+ * instead, and without `installed` (or without discovery installed) step 3 keeps
+ * the general "read relevant skills" wording.
  */
-function buildPrompt(issue) {
+function buildPrompt(issue, installed) {
     return `You are working on issue ${issue.id} in this project.
 
 ## Issue: ${issue.title}
@@ -903,7 +970,7 @@ ${issue.description}
 ## Instructions
 1. Read AGENTS.md for project orientation
 2. Claim the issue: bd update ${issue.id} --claim
-3. Read relevant skills from skills/ (list folders, read each SKILL.md) before making changes
+${skillStep(issue, installed)}
 4. Implement the changes following TDD-Lite: observe, implement, verify
 5. Run the tests this issue needs, and no more:
    - If the issue description states which tests to run, run exactly those and skip the rest of this step. The issue's scope replaces the default below; do not run both.
@@ -1201,7 +1268,8 @@ async function processIssue(issue, opts) {
         }
     }
     // Initial run
-    const prompt = buildPrompt(issue);
+    // opts.cwd is the worktree the session runs in, so its skills/ is the one the session sees.
+    const prompt = buildPrompt(issue, readInstalledSkills(opts.cwd ?? process.cwd()));
     console.log(`\x1b[32m[bd-loop]\x1b[0m   🚀 Starting Claude session (budget: $${opts.budget}, session: ${sessionId.substring(0, 8)}...)`);
     const initialRun = await runClaude(prompt, {
         budget: opts.budget,

package/docs/loop.md

@@ -29,6 +29,12 @@ Without `--run`, the command shows what it would do without executing anything.
 
 Each Claude session gets a full prompt with issue details and instructions to work autonomously through the complete workflow: claim, implement, test, commit, close, and push.
 
+The prompt tells a session which skills to read before it makes changes.
+The loop matches the names of the skills installed in the session's own `skills/` folder against the issue description, accepting either a bare name such as `boop-testing-testing` or a path such as `skills/boop-testing-testing/SKILL.md`.
+It lists each skill the issue names, once and in the order first mentioned, as the path to its `SKILL.md`, adding the `PROJECT.md` beside it where there is one, and asks the session to read each in full unless it has already read it in this session.
+When the issue names no installed skill, the prompt instead tells the session to follow `skills/boop-skills-discovery/SKILL.md` to choose the relevant skills.
+Spelling out the paths matters: a session starts with every skill's name and description in view but none of their content, and it opens a skill it only sees named about one time in seven.
+
 The prompt does not tell a session to run the whole test suite. If the issue says which tests to run, the session runs those. Otherwise it runs the focused tests for the files it changed plus the project's static check, using the commands the `boop-testing-testing` skill and the `PROJECT.md` beside it give. The full suite runs only when an issue asks for it, which is normally the task that completes the branch, and again when `boop loop --merge` integrates the branch.
 
 ### Planning mode (`--work` + `--flow`)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@boopkit/cli",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "description": "boop: the opinionated bootstrap for founder friendly, AI-first web apps - code plus agent skills, composable from day one.",
   "main": "dist/cli.js",
   "workspaces": [