@punks/cli 2.0.0-beta.3 → 2.0.0-beta.4

package/dist/index.js

@@ -52435,7 +52435,7 @@ var toolCatalog = [
 
 // package.json
 var name = "@punks/cli";
-var version = "2.0.0-beta.3";
+var version = "2.0.0-beta.4";
 // src/baseline/bundled.ts
 var bundledBaseline = {
   summary: {
@@ -54086,6 +54086,7 @@ var formatAgentHandoffSummary = (result) => [
   result.monorepo ? "  2. Repo is in monorepo mode. Generate final prompt files for root, docs, and each relevant app/package scope." : "  2. Repo is in single-repo mode. Stitch scoped guidance into one root prompt, plus docs guidance when present.",
   "  3. Read `.devpunks/required-tools.json` and verify `skills`, `portless`, `opensrc`, and `agent-browser` are actually available when listed. If any are missing, install/fix that first.",
   "  4. Keep the final prompt house style tight: `## ... Guidance`, `Primary skills here`, one short scope-boundary paragraph, optional `opensrc` guidance only when needed, then the docs-update rule.",
+  "  4a. Never put phase skills in scoped `AGENTS.md` primary-skill lines. Keep `requirements-phase`, `delivery-phase`, `debugging-phase`, `review-phase`, `resolve-debt-phase`, and `docs-ingest-phase` as global orchestration entrypoints only.",
   "  5. Treat every authored root/docs/workspace `AGENTS.md` file as the neutral scoped prompt source and create a sibling `CLAUDE.md` symlink mirror beside each one.",
   "  6. Keep `.agents/AGENTS.md` as the shared global prompt source behind the scoped prompt tree; `.claude/CLAUDE.md` should mirror that neutral file.",
   "  7. Keep `.agents/hooks/` as the neutral hook source, `.agents/skills/` as the main skill directory, and `.agents/scripts/sync-subagents.mjs` as the harness sync entrypoint. Only `.claude/skills` should mirror `.agents/skills`.",
@@ -54475,7 +54476,17 @@ import {
 import path8 from "path";
 
 // src/content/prompts.ts
-var renderPrimarySkills = (skills) => skills.map((skill) => `\`${skill}\``).join(", ");
+var phaseSkillIds = [
+  "debugging-phase",
+  "delivery-phase",
+  "docs-ingest-phase",
+  "requirements-phase",
+  "resolve-debt-phase",
+  "review-phase"
+];
+var phaseSkillSet = new Set(phaseSkillIds);
+var scopedPrimarySkills = (skills) => skills.filter((skill) => !phaseSkillSet.has(skill));
+var renderPrimarySkills = (skills) => (scopedPrimarySkills(skills).length === 0 ? ["simplify"] : scopedPrimarySkills(skills)).map((skill) => `\`${skill}\``).join(", ");
 var titleFromSegment = (value6) => value6.split(/[-_]/u).filter((segment) => segment.length > 0).map((segment) => segment[0].toUpperCase() + segment.slice(1)).join(" ");
 var sharedAgentsPromptTemplate = readDataFile("AGENTS.md");
 var rootPromptTemplate = `## Root Guidance
@@ -54502,10 +54513,10 @@ Use \`portless\` for local development URLs instead of baking raw \`localhost:<p
 If work here changes setup, workflow, AI scaffold surfaces, or other non-obvious behavior, update \`docs/README.md\` and the relevant runbook in \`docs/runbooks/\` in the same task.`;
 var docsPromptTemplate = `## Docs Guidance
 
-Primary skills here: \`docs-ingest-phase\`, \`simplify\`.
+Primary skills here: \`simplify\`.
 
 \`docs/\` is the repo's durable, human-facing knowledge base for implemented reality.
-Use \`docs-ingest-phase\` before adding, editing, moving, or deleting docs, and when code changes may require updates to \`docs/README.md\`, a domain doc, a runbook, or an ADR.
+Phase skills such as \`docs-ingest-phase\` are global orchestration entrypoints, not scoped primary skills. Invoke them from the parent goal/handoff flow when needed; do not list them in scoped \`AGENTS.md\` primary-skill lines.
 
 Keep agent workflow in prompt files, not in the docs themselves.`;
 var includesPack = (packs, packId) => packs.includes(packId);
@@ -54641,6 +54652,7 @@ var renderPromptSpecMarkdown = (spec) => [
   "",
   "- Start with one `## <Scope> Guidance` heading.",
   "- Put one `Primary skills here: ...` line near the top.",
+  "- Never put phase skills in scoped `AGENTS.md` primary-skill lines. Keep `requirements-phase`, `delivery-phase`, `debugging-phase`, `review-phase`, `resolve-debt-phase`, and `docs-ingest-phase` as global orchestration entrypoints only.",
   "- Follow with one short paragraph defining the scope boundary: what belongs here vs elsewhere.",
   "- Treat every authored `AGENTS.md` file as the neutral source of truth and create a sibling `CLAUDE.md` symlink mirror that points to it.",
   "- Add `opensrc` / source-inspection guidance only when this scope actually needs it.",
@@ -54666,9 +54678,10 @@ var renderPromptSpecMarkdown = (spec) => [
   "- Keep the final prompt concise, imperative, and scope-first.",
   "- Match the existing repo house style used by the detected workspace prompt files.",
   "- Preserve this order: heading, `Primary skills here`, scope boundary, optional `opensrc`, docs update rule.",
+  "- Keep phase skills out of every scoped `AGENTS.md`; invoke phases from the parent goal/handoff flow instead.",
   "- Route broader monorepo concerns back to the root prompt instead of repeating them in every scope.",
   "- If a seed prompt exists in the source repo, preserve repo-specific constraints while reconciling them with the detected pack set.",
-  "- Keep docs-ingest-phase workflow in prompt files, not in generated docs pages."
+  "- Keep docs ingest workflow in prompt files, not in generated docs pages."
 ].join(`
 `);
 var renderAgentHandoffMarkdown = ({
@@ -54717,6 +54730,7 @@ var renderAgentHandoffMarkdown = ({
   "2. Use the prompt spec files to author final prompt files. Do not treat the spec files as final prompt bodies.",
   "3. Match the existing prompt house style from this repo: one `## ... Guidance` heading, `Primary skills here`, one short scope paragraph, optional `opensrc` guidance only when needed, then the docs-update rule.",
   "3a. Read the required tools manifest and confirm `skills`, `portless`, `opensrc`, and `agent-browser` are actually available before deeper repo work.",
+  "3b. Never put phase skills in scoped `AGENTS.md` primary-skill lines. Keep `requirements-phase`, `delivery-phase`, `debugging-phase`, `review-phase`, `resolve-debt-phase`, and `docs-ingest-phase` as global orchestration entrypoints invoked from the parent goal/handoff flow.",
   monorepo ? "4. Because this repo is in monorepo mode, create scoped prompt files for the root, docs scope when present, and each relevant app/package scope." : "4. Because this repo is in single-repo mode, stitch scope guidance into a single root prompt plus docs guidance when present.",
   "5. Author every root/docs/workspace `AGENTS.md` file as the neutral prompt source of truth and create a sibling `CLAUDE.md` symlink mirror beside each one instead of maintaining duplicated prompt bodies.",
   "6. Keep `.agents/AGENTS.md` as the shared global guidance source behind the scoped prompt tree; `.claude/CLAUDE.md` should stay a symlink mirror of that neutral file.",
@@ -55140,7 +55154,7 @@ var primarySkillsForWorkspace = ({
     baseline
   });
   const skills = workspacePacks.flatMap((packId) => skillsForPack(packId, baseline));
-  return uniqueSorted(skills);
+  return uniqueSorted(relativeWorkspacePath === ".agents" ? skills : scopedPrimarySkills(skills));
 };
 var buildPromptSpec = ({
   scanDirectory,
@@ -56031,12 +56045,11 @@ This file defines how any agent operates within \`${wikiRoot}/\`. Read it before
 
 ## Skill Routing
 
-Primary skills here: \`create-spec\`, \`create-plan\`, \`implement-spec\`, \`docs-ingest-phase\`, \`simplify\`.
+Primary skills here: \`create-spec\`, \`create-plan\`, \`implement-spec\`, \`simplify\`.
 
-- Use \`docs-ingest-phase\` to ingest a spec folder into the wiki domain layer and create missing domain scaffolding when needed.
+- Phase skills such as \`docs-ingest-phase\` are global orchestration entrypoints, not scoped primary skills. Invoke them from the parent goal/handoff flow when needed; do not list them in scoped \`AGENTS.md\` primary-skill lines.
 - Use \`create-plan\` to turn an approved spec into an execution-ready \`PLAN.md\`.
 - Use \`implement-spec\` to execute an approved spec folder. Choose the execution mode inside the skill: \`sequential\` or \`parallel\`.
-- \`docs-ingest-phase\` owns the full ingest pipeline. It creates or updates the domain map/contract when needed, then writes flow pages first, then concept pages.
 - Do not hand-write \`domains/<domain>/flows/\` or \`domains/<domain>/concepts/\` pages when that ingest workflow applies.
 - \`SPEC.md\` and \`IMPLEMENTATION-NOTES.md\` remain the source material, but the ingest orchestrator may update their frontmatter/link bookkeeping (\`ingested\`, \`last_ingested\`, backlinks) as part of the pipeline.
 
@@ -57632,7 +57645,8 @@ var runUpdate = ({
     shouldApply ? "Managed scaffold files updated." : "No files were written.",
     `Changed files: ${changes2.length}`,
     `Stale files: ${staleFiles.length}`,
-    `Manifests scanned: ${manifestPaths(detection).join(", ") || "\u2205"}`
+    `Manifests scanned: ${manifestPaths(detection).join(", ") || "\u2205"}`,
+    "Guidance: keep phase skills out of scoped `AGENTS.md` primary-skill lines; invoke them from the parent goal/handoff flow."
   ].join(`
 `)));
   if (emitJson) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@punks/cli",
-  "version": "2.0.0-beta.3",
+  "version": "2.0.0-beta.4",
   "description": "Devpunks AI scaffolding CLI",
   "bin": {
     "devpunks": "dist/index.js",