cc-dev-template 0.1.75 → 0.1.77

package/bin/install.js

@@ -255,8 +255,8 @@ if (fs.existsSync(mergeSettingsPath)) {
     { file: 'read-guard-hook.json', name: 'Context guard for large reads' },
     { file: 'task-output-guard-hook.json', name: 'TaskOutput context guard' },
     { file: 'statusline-config.json', name: 'Custom status line' },
-    // Spinner verbs - choose one (Helldivers or Factorio)
-    { file: 'spinner-verbs-helldivers.json', name: 'Helldivers spinner verbs' }
+    // Spinner verbs - choose one (Star Trek or Factorio)
+    { file: 'spinner-verbs-startrek.json', name: 'Star Trek spinner verbs' }
     // { file: 'spinner-verbs-factorio.json', name: 'Factorio spinner verbs' }
   ];
 
@@ -312,7 +312,8 @@ const deprecatedFiles = [
   path.join(CLAUDE_DIR, 'scripts', 'bash-precheck-hook.json'),
   path.join(CLAUDE_DIR, 'hooks', 'bash-overflow-guard.sh'),
   path.join(CLAUDE_DIR, 'scripts', 'bash-overflow-hook.json'),
-  path.join(CLAUDE_DIR, 'scripts', 'env-config.json')
+  path.join(CLAUDE_DIR, 'scripts', 'env-config.json'),
+  path.join(CLAUDE_DIR, 'scripts', 'spinner-verbs-helldivers.json')
 ];
 
 deprecatedFiles.forEach(file => {
@@ -401,6 +402,13 @@ if (fs.existsSync(settingsFile)) {
       settingsModified = true;
     }
 
+    // Enable MCP tool search (loads MCP tools on-demand instead of in context)
+    if (settings.env.ENABLE_TOOL_SEARCH !== 'true') {
+      settings.env.ENABLE_TOOL_SEARCH = 'true';
+      console.log('✓ Set ENABLE_TOOL_SEARCH=true');
+      settingsModified = true;
+    }
+
     if (settingsModified) {
       fs.writeFileSync(settingsFile, JSON.stringify(settings, null, 2));
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cc-dev-template",
-  "version": "0.1.75",
+  "version": "0.1.77",
   "description": "Structured AI-assisted development framework for Claude Code",
   "bin": {
     "cc-dev-template": "./bin/install.js"

package/src/scripts/spinner-verbs-startrek.json

@@ -0,0 +1,47 @@
+{
+  "spinnerVerbs": {
+    "mode": "replace",
+    "verbs": [
+      "Engaging warp drive",
+      "Hailing frequencies open",
+      "Scanning for lifeforms",
+      "Routing through deflector dish",
+      "Calibrating phasers",
+      "Modulating shield harmonics",
+      "Consulting the computer",
+      "Running diagnostic",
+      "Reversing polarity",
+      "Diverting auxiliary power",
+      "Locking on target",
+      "Compensating for interference",
+      "Rerouting power",
+      "Establishing uplink",
+      "Analyzing subspace anomaly",
+      "Initializing transporter",
+      "Plotting course",
+      "Processing sensor data",
+      "Accessing Starfleet database",
+      "Raising shields",
+      "Optimizing ratios",
+      "Expanding the factory",
+      "Researching technology",
+      "Balancing belts",
+      "Routing logistics",
+      "Smelting ore",
+      "Automating production",
+      "Deploying blueprints",
+      "Scaling throughput",
+      "Refining petroleum",
+      "Extending rail network",
+      "Calculating ratios",
+      "Processing resources",
+      "Assembling components",
+      "Constructing outpost",
+      "Launching rockets",
+      "Clearing biters",
+      "Inserting inserters",
+      "Growing the factory",
+      "The factory must grow"
+    ]
+  }
+}

package/src/skills/agent-browser/SKILL.md

@@ -204,3 +204,13 @@ agent-browser find testid "submit-btn" click
 ./templates/authenticated-session.sh https://app.example.com/login
 ./templates/capture-workflow.sh https://example.com ./output
 ```
+
+## Reflect After Use
+
+After completing the browser automation task, reflect on your experience.
+
+Were any commands, flags, patterns, or workarounds in this reference incorrect or missing? Did you discover a command syntax, a workaround for a specific site, or a pattern that should be documented here?
+
+If yes, update the relevant section of this skill file. Only add tribal knowledge — commands and patterns a fresh Claude instance would not know about agent-browser specifically. Keep within size targets.
+
+Tell the user what you updated, or confirm no updates were needed.

package/src/skills/claude-md/references/audit.md

@@ -61,3 +61,13 @@ Changes made:
 Remaining concerns:
 - [any issues needing human decision]
 ```
+
+## Reflect
+
+Before ending, reflect on your experience using this skill.
+
+Were any CLAUDE.md principles, structural guidelines, or audit criteria in this skill wrong or incomplete? Did you discover a CLAUDE.md pattern or anti-pattern that should be documented for next time?
+
+If yes, update the specific file in the claude-md skill directory. Only add tribal knowledge — insights a fresh Claude instance would not already know. Keep files within size targets.
+
+Tell the user what you updated, or confirm no updates were needed.

package/src/skills/claude-md/references/create.md

@@ -70,3 +70,13 @@ Verify:
 4. Written as orientation, not documentation?
 
 If all yes, you're done.
+
+## Reflect
+
+Before ending, reflect on your experience using this skill.
+
+Were any CLAUDE.md principles, structural guidelines, or audit criteria in this skill wrong or incomplete? Did you discover a CLAUDE.md pattern or anti-pattern that should be documented for next time?
+
+If yes, update the specific file in the claude-md skill directory. Only add tribal knowledge — insights a fresh Claude instance would not already know. Keep files within size targets.
+
+Tell the user what you updated, or confirm no updates were needed.

package/src/skills/claude-md/references/modify.md

@@ -50,3 +50,13 @@ If the content would make the file exceed ~100 lines, consider:
 ## Step 5: Confirm
 
 Tell the user what was added and where. If creating a new CLAUDE.md file, explain why that location was chosen.
+
+## Reflect
+
+Before ending, reflect on your experience using this skill.
+
+Were any CLAUDE.md principles, structural guidelines, or audit criteria in this skill wrong or incomplete? Did you discover a CLAUDE.md pattern or anti-pattern that should be documented for next time?
+
+If yes, update the specific file in the claude-md skill directory. Only add tribal knowledge — insights a fresh Claude instance would not already know. Keep files within size targets.
+
+Tell the user what you updated, or confirm no updates were needed.

package/src/skills/creating-agent-skills/references/create-step-2-design.md

@@ -157,6 +157,14 @@ List out the steps. Each step becomes one markdown file in `references/`. For ea
 - What signals the step is complete (the chain condition)
 - What the next step is
 
+### Include a Reflection Step
+
+Every skill must end with a reflection section. This is not a separate chained step file — it is a section appended to the skill's existing final step (or the end of SKILL.md for informational skills). Plan for 10-20 lines.
+
+The reflection section is where the agent looks back on its experience using the skill and, if the instructions were wrong, incomplete, or suboptimal, updates the skill files. This creates a self-learning loop — skills improve through use.
+
+For forked-context skills (`context: fork`), use a "Skill Observations" section in the output format instead, since the sub-agent should not edit skill files from an isolated context.
+
 ## Confirm With the User
 
 Present the design:

package/src/skills/creating-agent-skills/references/create-step-3-write.md

@@ -159,6 +159,24 @@ If the skill involves tool calls, external services, or operations that can fail
 
 For critical validations, bundle a script rather than relying on language instructions. Code is deterministic; language interpretation is not.
 
+### Reflection Step
+
+Every skill's final step (or the end of single-file skills) must include a reflection section. This creates a self-learning loop: the agent assesses its experience and updates the skill for next time.
+
+Place the reflection after the work completion section (after "Completion", "Report Results", or equivalent). Structure it as:
+
+1. **Trigger**: "Before ending, reflect on your experience using this skill."
+2. **Assessment**: "Were any instructions wrong, incomplete, or misleading? Did you have to figure something out that the skill should have told you? Did any commands, paths, or patterns fail and require correction?"
+3. **Action**: "If yes, update the specific skill file where the issue lives. Apply the tribal knowledge test: only add what a fresh Claude instance would not already know."
+4. **Guardrails**: "Keep changes minimal. Fix what was wrong, add what was missing. Do not bloat the file beyond its size target or record situation-specific details that would not generalize."
+5. **Report**: "Tell the user what you changed and why, or confirm that no updates were needed."
+
+Tailor the assessment questions to the skill's domain — what "went wrong" means for a prompting skill is different from what it means for a browser automation skill.
+
+For forked-context skills (`context: fork`), add a "Skill Observations" optional section to the output format instead. The sub-agent notes any issues with its own instructions; the parent context decides whether to act.
+
+Keep the reflection section under 20 lines. Use imperative voice like all skill content.
+
 ### MCP Tool References
 
 When a skill uses MCP tools, use fully qualified names:

package/src/skills/creating-agent-skills/references/create-step-4-review.md

@@ -44,6 +44,8 @@ Go through each file and verify:
 - Name matches the directory name?
 - Description uses third person with quoted trigger phrases?
 - All referenced files exist? (no broken links)
+- Reflection step present in the final step file (or end of SKILL.md for informational skills)?
+- For forked-context skills: "Skill Observations" section in the output format?
 
 ## Run Validation
 

package/src/skills/creating-agent-skills/references/create-step-5-install.md

@@ -61,3 +61,13 @@ Summarize what was created:
 - Install location
 - Trigger phrases
 - File structure (list all files)
+
+## Reflect
+
+Before ending, reflect on your experience creating this skill.
+
+Were any instructions in the creating-agent-skills skill wrong, incomplete, or misleading? Did you discover techniques, gotchas, or patterns that should be encoded for next time? Did any steps send you down a wrong path or leave out critical guidance?
+
+If yes, identify the specific file in the creating-agent-skills skill where the issue lives and update it. Apply the tribal knowledge test: only add what a fresh Claude instance would not already know. Keep the file within its size target.
+
+Tell the user what you updated, or confirm no skill updates were needed.

package/src/skills/creating-agent-skills/references/fix-step-1-diagnose.md

@@ -72,6 +72,11 @@ Evaluate each file against these criteria:
 - All referenced files exist?
 - Any unreferenced files in `references/` that should be connected?
 
+### Self-Learning
+- Does the skill have a reflection step in its final step file (or at the end of SKILL.md for informational skills)?
+- For forked-context skills (`context: fork`): does the output format include a "Skill Observations" section?
+- If missing, flag it — every skill needs a self-learning loop.
+
 ## Summarize Findings
 
 Present the diagnosis to the user:
@@ -90,6 +95,7 @@ Based on your diagnosis, determine which type of fix is needed:
 - Removing meta-descriptions
 - Fixing broken file references
 - Small description improvements
+- Adding a missing reflection step
 
 **Structural changes** — anything that changes the skill's architecture:
 - Converting between informational and procedural types

package/src/skills/creating-agent-skills/references/fix-step-2-apply.md

@@ -94,6 +94,8 @@ Does this justify its token cost? If Claude already knows it — remove it. If i
 
 **Fix description:** Rewrite to third person, add quoted trigger phrases, focus on WHEN not HOW.
 
+**Add reflection step:** Append a reflection section to the skill's final step file (or end of SKILL.md for informational skills). See `references/create-step-3-write.md` "Reflection Step" section for the writing guidance. For forked-context skills, add a "Skill Observations" section to the output format instead.
+
 ## Apply the Changes
 
 Make all planned modifications now.

package/src/skills/creating-agent-skills/references/fix-step-3-validate.md

@@ -52,3 +52,13 @@ Summarize what was fixed:
 - Which files changed
 - What was wrong and how it was resolved
 - Confirm with the user that the skill now behaves as expected
+
+## Reflect
+
+Before ending, reflect on your experience fixing this skill.
+
+Were any diagnostic criteria, fix patterns, or writing principles in the creating-agent-skills skill wrong, incomplete, or misleading? Did you discover something during diagnosis or repair that should be encoded for next time?
+
+If yes, identify the specific file in the creating-agent-skills skill where the issue lives and update it. Apply the tribal knowledge test: only add what a fresh Claude instance would not already know. Keep the file within its size target.
+
+Tell the user what you updated, or confirm no skill updates were needed.

package/src/skills/creating-sub-agents/references/create-step-5-install.md

@@ -74,3 +74,13 @@ Summarize what was created:
 - Model
 - Memory scope (if any)
 - Skills preloaded (if any)
+
+## Reflect
+
+Before ending, reflect on your experience creating this sub-agent.
+
+Were any instructions in the creating-sub-agents skill wrong, incomplete, or misleading? Did you discover techniques, gotchas, or patterns that should be encoded for next time? Did any steps send you down a wrong path or leave out critical guidance?
+
+If yes, identify the specific file in the creating-sub-agents skill where the issue lives and update it. Apply the tribal knowledge test: only add what a fresh Claude instance would not already know. Keep the file within its size target.
+
+Tell the user what you updated, or confirm no skill updates were needed.

package/src/skills/creating-sub-agents/references/fix-step-3-validate.md

@@ -50,3 +50,13 @@ Summarize what was fixed:
 - Which aspects changed (frontmatter, prompt, hooks)
 - What was wrong and how it was resolved
 - Confirm with the user that the sub-agent now behaves as expected
+
+## Reflect
+
+Before ending, reflect on your experience fixing this sub-agent.
+
+Were any diagnostic criteria, fix patterns, or writing principles in the creating-sub-agents skill wrong, incomplete, or misleading? Did you discover something during diagnosis or repair that should be encoded for next time?
+
+If yes, identify the specific file in the creating-sub-agents skill where the issue lives and update it. Apply the tribal knowledge test: only add what a fresh Claude instance would not already know. Keep the file within its size target.
+
+Tell the user what you updated, or confirm no skill updates were needed.

package/src/skills/execute-spec/references/workflow.md

@@ -72,3 +72,13 @@ Read `phase-4-triage.md` for details.
 - **Minimal returns** - Agents return status only, details in task files
 - **Task file is source of truth** - Implementation Notes and Review Notes track all history
 - **Parallelism** - Use `run_in_background: true` where possible
+
+## Reflect
+
+Before ending, reflect on your experience using this skill.
+
+Were any orchestration patterns, dispatch instructions, or triage procedures in this skill wrong or incomplete? Did the implementer/validator loop reveal a pattern that should be encoded for next time?
+
+If yes, update the specific file in the execute-spec skill directory. Only add tribal knowledge. Keep files within size targets.
+
+Tell the user what you updated, or confirm no updates were needed.

package/src/skills/initialize-project/SKILL.md

@@ -31,3 +31,13 @@ Report what was created:
 - `CLAUDE.md` - created or unchanged
 
 End with: "Run `/prime` to start a session."
+
+## Reflect
+
+Before ending, reflect on your experience using this skill.
+
+Were any template paths, placeholder formats, or initialization steps in this skill wrong or incomplete? Did you discover a project scaffolding pattern that should be encoded for next time?
+
+If yes, update this skill file. Only add tribal knowledge — details a fresh Claude instance would not already know. Keep within size targets.
+
+Tell the user what you updated, or confirm no updates were needed.

package/src/skills/project-setup/references/step-5-verify.md

@@ -68,3 +68,13 @@ Tell the user:
 - Whether the project is ready to use
 
 If everything passed, the setup is complete.
+
+## Reflect
+
+Before ending, reflect on your experience using this skill.
+
+Were any Makefile patterns, hook configurations, or verification steps in this skill wrong or incomplete? Did you discover a project setup convention that should be encoded for next time?
+
+If yes, update the specific file in the project-setup skill directory. Only add tribal knowledge. Keep files within size targets.
+
+Tell the user what you updated, or confirm no updates were needed.

package/src/skills/prompting/references/create.md

@@ -57,3 +57,13 @@ Present the draft prompt to the user.
 Ask: "Does this capture what you need? Any adjustments?"
 
 Incorporate feedback until the user is satisfied.
+
+## Reflect
+
+Before ending, reflect on your experience using this skill.
+
+Were any prompting principles, review criteria, or writing guidance in this skill wrong or incomplete? Did you apply a technique that worked well but is not captured here? Did any guidance lead to a weaker prompt that needed correction?
+
+If yes, update the specific file in the prompting skill directory. Only add tribal knowledge — patterns or insights a fresh Claude instance would not already know about prompt engineering. Keep the file within its size target.
+
+Tell the user what you updated, or confirm no updates were needed.

package/src/skills/prompting/references/review.md

@@ -76,3 +76,13 @@ Format the review as:
 Ask: "Would you like me to adjust anything in the improved version?"
 
 Incorporate feedback and present updated version until the user is satisfied.
+
+## Reflect
+
+Before ending, reflect on your experience using this skill.
+
+Were any prompting principles, review criteria, or writing guidance in this skill wrong or incomplete? Did you apply a technique that worked well but is not captured here? Did any guidance lead to a weaker prompt that needed correction?
+
+If yes, update the specific file in the prompting skill directory. Only add tribal knowledge — patterns or insights a fresh Claude instance would not already know about prompt engineering. Keep the file within its size target.
+
+Tell the user what you updated, or confirm no updates were needed.

package/src/skills/research/references/step-2-conduct-research.md

@@ -61,3 +61,13 @@ After writing the document:
 1. Confirm the research is complete
 2. Summarize the key takeaways
 3. Return to the invoking context (spec-interview or user)
+
+## Reflect
+
+Before ending, reflect on your experience using this skill.
+
+Were any research strategies, output format requirements, or source evaluation criteria in this skill wrong or incomplete? Did you discover a research approach or information synthesis technique that should be encoded for next time?
+
+If yes, update the specific file in the research skill directory. Only add tribal knowledge — insights a fresh Claude instance would not already know about conducting research. Keep files within size targets.
+
+Tell the user what you updated, or confirm no updates were needed.

package/src/skills/spec-interview/references/step-7-finalize.md

@@ -55,4 +55,14 @@ Once user confirms no more review passes needed:
    - After all teammates confirm shutdown, use TeamDelete to clean up team resources
    - The `{spec_dir}/working/` directory remains on disk as reference for implementation
 
+## Reflect
+
+Before ending, reflect on your experience conducting this spec interview.
+
+Were any interview steps, team coordination patterns, or checkpoint instructions in this skill wrong or incomplete? Did you discover a question sequence, team interaction pattern, or spec structure that worked better than what the skill prescribed?
+
+If yes, identify the specific file in the spec-interview skill where the issue lives and update it. Only add tribal knowledge — insights a fresh Claude instance would not already know about conducting spec interviews. Keep the file within its size target.
+
+Tell the user what you updated, or confirm no skill updates were needed.
+
 If yes to task breakdown, invoke `spec-to-tasks` and specify which spec to break down.

package/src/skills/spec-review/SKILL.md

@@ -81,6 +81,9 @@ Return the review as:
 ### Blocking Dependencies
 - [Dependency]: [What's needed before implementation can start]
 
+### Skill Observations (optional)
+If any checklist items, evaluation criteria, or output format instructions in this skill were wrong, incomplete, or misleading during this review, note them here. Leave empty if no issues were found.
+
 ### Recommendation
 [Specific questions to ask the user, or "Spec is implementation-ready"]
 ```

package/src/skills/spec-sanity-check/SKILL.md

@@ -71,6 +71,9 @@ Return findings as:
 ### Potential Pitfalls
 - [Pitfall]: [How to avoid]
 
+### Skill Observations (optional)
+If any evaluation questions, check categories, or output format instructions in this skill were wrong, incomplete, or misleading during this review, note them here. Leave empty if no issues were found.
+
 ### Recommendation
 [Either "Plan is sound" or specific concerns to address]
 ```

package/src/skills/spec-to-tasks/references/step-4-review.md

@@ -41,6 +41,10 @@ After addressing critical issues, present:
 
 If the user wants changes, update the task files and re-run the review.
 
+## Skill Observations
+
+If any task generation patterns, step instructions, or template formats in this skill were wrong, incomplete, or misleading during this run, include a note in your final output to the user. This helps the parent context decide whether to update the skill.
+
 ## Complete
 
 Once the user approves the task breakdown, the skill is complete. The tasks are ready for implementation.

package/src/skills/task-review/references/checklist.md

@@ -147,6 +147,9 @@ Return findings as a structured list:
 
 ## Notes
 - [T004] Could merge with T005 since they share the same files
+
+## Skill Observations (optional)
+If any checklist items, severity criteria, or review patterns in this skill were wrong, incomplete, or misleading during this review, note them here. Leave empty if no issues were found.
 ```
 
 If no issues found, state: "Task breakdown looks good. All criteria covered, dependencies valid, verification methods concrete."

package/src/scripts/spinner-verbs-helldivers.json

@@ -1,27 +0,0 @@
-{
-  "spinnerVerbs": {
-    "mode": "replace",
-    "verbs": [
-      "Spreading democracy",
-      "Liberating",
-      "Deploying stratagems",
-      "Calling in reinforcements",
-      "Eliminating hostiles",
-      "Securing perimeter",
-      "Extracting intel",
-      "Suppressing resistance",
-      "Dispensing freedom",
-      "Neutralizing threats",
-      "Conducting reconnaissance",
-      "Mobilizing forces",
-      "Purging enemies",
-      "Defending liberty",
-      "Executing orbital strike",
-      "Requesting extraction",
-      "Fortifying position",
-      "Engaging targets",
-      "Invoking Super Earth",
-      "Upholding managed democracy"
-    ]
-  }
-}