learnship 2.3.4 → 2.3.6

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "learnship",
   "description": "Agentic engineering done right — 57 structured workflows, 17 specialist agent personas, persistent memory across sessions, integrated learning partner, and impeccable UI design system. Works with Claude Code, Windsurf, Cursor, Gemini CLI, OpenCode, and Codex.",
-  "version": "2.3.4",
+  "version": "2.3.6",
   "author": {
     "name": "Favio Vazquez",
     "email": "favio.vazquezp@gmail.com"

package/.cursor-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "learnship",
   "displayName": "learnship",
   "description": "Agentic engineering done right — 57 structured workflows, 17 specialist agent personas, persistent memory across sessions, integrated learning partner, and impeccable UI design system.",
-  "version": "2.3.4",
+  "version": "2.3.6",
   "logo": "assets/logo.png",
   "author": {
     "name": "Favio Vazquez",

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "learnship",
-  "version": "2.3.4",
+  "version": "2.3.6",
   "description": "Agentic engineering done right — 57 structured workflows, 17 specialist agent personas, persistent memory across sessions, integrated learning partner, and impeccable UI design system.",
   "author": "Favio Vazquez",
   "homepage": "https://faviovazquez.github.io/learnship/",

package/learnship/references/git-integration.md

@@ -226,14 +226,14 @@ Each plan produces 2-4 commits (tasks + metadata). Clear, granular, bisectable.
 ## Why Per-Task Commits?
 
 **Context engineering for AI:**
-- Git history becomes primary context source for future Claude sessions
+- Git history becomes primary context source for future agent sessions
 - `git log --grep="{phase}-{plan}"` shows all work for a plan
 - `git diff <hash>^..<hash>` shows exact changes per task
 - Less reliance on parsing SUMMARY.md = more context for actual work
 
 **Failure recovery:**
 - Task 1 committed ✅, Task 2 failed ❌
-- Claude in next session: sees task 1 complete, can retry task 2
+- Agent in next session: sees task 1 complete, can retry task 2
 - Can `git reset --hard` to last successful task
 
 **Debugging:**
@@ -242,8 +242,8 @@ Each plan produces 2-4 commits (tasks + metadata). Clear, granular, bisectable.
 - Each commit is independently revertable
 
 **Observability:**
-- Solo developer + Claude workflow benefits from granular attribution
+- Solo developer + agent workflow benefits from granular attribution
 - Atomic commits are git best practice
-- "Commit noise" irrelevant when consumer is Claude, not humans
+- "Commit noise" irrelevant when consumer is the agent, not humans
 
 </commit_strategy_rationale>

package/learnship/references/questioning.md

@@ -155,7 +155,7 @@ Loop until "Create PROJECT.md" selected.
 - **Rushing** — Minimizing questions to get to "the work"
 - **Shallow acceptance** — Taking vague answers without probing
 - **Premature constraints** — Asking about tech stack before understanding the idea
-- **User skills** — NEVER ask about user's technical experience. Claude builds.
+- **User skills** — NEVER ask about user's technical experience. The agent builds.
 
 </anti_patterns>
 

package/learnship/references/verification-patterns.md

@@ -599,7 +599,7 @@ Some things can't be verified programmatically. Flag these for human testing:
 ## Pre-Checkpoint Automation
 
 Key principles for automation-first verification:
-- Claude sets up verification environment BEFORE presenting checkpoints
+- The agent sets up verification environment BEFORE presenting checkpoints
 - Users never run CLI commands (visit URLs only)
 - Server lifecycle: start before checkpoint, handle port conflicts, keep running for duration
 - CLI installation: auto-install where safe, checkpoint for user choice otherwise

package/learnship/templates/context.md

@@ -28,7 +28,7 @@ Implementation decisions captured during `discuss-phase [N]`. This file is the p
 ### [Area 3 that was discussed]
 - **D-04:** [Specific decision made]
 
-### Claude's Discretion
+### Agent's Discretion
 [Areas where user explicitly said "you decide" — the agent has flexibility here during planning/implementation]
 
 </decisions>
@@ -122,7 +122,7 @@ Display posts from followed users in a scrollable feed. Users can view posts and
 - Friendly illustration + "Follow people to see posts here"
 - Suggest 3-5 accounts to follow based on interests
 
-### Claude's Discretion
+### Agent's Discretion
 - Loading skeleton design
 - Exact spacing and typography
 - Error state handling
@@ -185,7 +185,7 @@ CLI command to backup database to local file or S3. Supports full and incrementa
 - --no-retry flag to fail fast
 - Partial backups are deleted on failure (no corrupt files)
 
-### Claude's Discretion
+### Agent's Discretion
 - Exact progress bar implementation
 - Compression algorithm choice
 - Temp file handling

package/learnship/templates/discussion-log.md

@@ -35,9 +35,9 @@ created: [date]
 
 ---
 
-## Claude's Discretion
+## Agent's Discretion
 
-[Areas delegated to Claude's judgment — list what was deferred and why]
+[Areas delegated to agent's judgment — list what was deferred and why]
 
 ## Deferred Ideas
 

package/learnship/workflows/discuss-phase.md

@@ -20,7 +20,7 @@ Extract implementation decisions that downstream planning needs. Analyze the pha
 
 2. **Planner** — Reads CONTEXT.md to know WHAT decisions are locked
    - "Pull-to-refresh on mobile" → planner includes that in task specs
-   - "Claude's Discretion: loading skeleton" → planner can decide approach
+   - "Agent's Discretion: loading skeleton" → planner can decide approach
 
 **Your job:** Capture decisions clearly enough that downstream agents can act on them without asking the user again.
 
@@ -305,7 +305,7 @@ Write `.planning/phases/[padded_phase]-[phase_slug]/[padded_phase]-CONTEXT.md`:
 ### [Category discussed]
 - [Decision captured]
 
-### Claude's Discretion
+### Agent's Discretion
 [Areas where user said "you decide"]
 
 </decisions>
@@ -365,7 +365,7 @@ Also write a discussion log for audit purposes using `@./templates/discussion-lo
 Write `.planning/phases/[padded_phase]-[phase_slug]/[padded_phase]-DISCUSSION-LOG.md` with:
 - All options considered for each area (not just the selected one)
 - The user's verbatim choice and rationale
-- Areas delegated to Claude's discretion
+- Areas delegated to agent's discretion
 - Deferred ideas
 
 This file is for human audit trails only — it is NOT referenced by downstream agents.

package/learnship/workflows/new-project.md

@@ -696,9 +696,19 @@ Task(
     </quality_gate>
 
     <output>
-    Write to: .planning/research/STACK.md
     Required sections: ## Recommended Stack, ## Alternatives Considered, ## What NOT to Use, ## Versions
     </output>
+
+    **WRITE ACTION REQUIRED — You MUST use your file-write tool to write STACK.md to disk. Do NOT output the content to the conversation. Do NOT treat this as done until the file physically exists on disk.**
+
+    Write the research content to `.planning/research/STACK.md` using your write tool now.
+
+    Then verify:
+    ```
+    node -e "const fs=require('fs');const f='.planning/research/STACK.md';if(!fs.existsSync(f)){console.log('STACK_MISSING');process.exit(1);}console.log('STACK_OK — '+fs.readFileSync(f,'utf8').length+' chars');"
+    ```
+
+    If `STACK_MISSING`: write the file and re-run until `STACK_OK`.
   "
 )
 
@@ -744,9 +754,19 @@ Task(
     </quality_gate>
 
     <output>
-    Write to: .planning/research/FEATURES.md
     Required sections: ## Table Stakes, ## Differentiators, ## Anti-Features
     </output>
+
+    **WRITE ACTION REQUIRED — You MUST use your file-write tool to write FEATURES.md to disk. Do NOT output the content to the conversation. Do NOT treat this as done until the file physically exists on disk.**
+
+    Write the research content to `.planning/research/FEATURES.md` using your write tool now.
+
+    Then verify:
+    ```
+    node -e "const fs=require('fs');const f='.planning/research/FEATURES.md';if(!fs.existsSync(f)){console.log('FEATURES_MISSING');process.exit(1);}console.log('FEATURES_OK — '+fs.readFileSync(f,'utf8').length+' chars');"
+    ```
+
+    If `FEATURES_MISSING`: write the file and re-run until `FEATURES_OK`.
   "
 )
 
@@ -792,9 +812,19 @@ Task(
     </quality_gate>
 
     <output>
-    Write to: .planning/research/ARCHITECTURE.md
     Required sections: ## Component Boundaries, ## Data Flow, ## Build Order, ## Integration Points
     </output>
+
+    **WRITE ACTION REQUIRED — You MUST use your file-write tool to write ARCHITECTURE.md to disk. Do NOT output the content to the conversation. Do NOT treat this as done until the file physically exists on disk.**
+
+    Write the research content to `.planning/research/ARCHITECTURE.md` using your write tool now.
+
+    Then verify:
+    ```
+    node -e "const fs=require('fs');const f='.planning/research/ARCHITECTURE.md';if(!fs.existsSync(f)){console.log('ARCH_MISSING');process.exit(1);}console.log('ARCH_OK — '+fs.readFileSync(f,'utf8').length+' chars');"
+    ```
+
+    If `ARCH_MISSING`: write the file and re-run until `ARCH_OK`.
   "
 )
 
@@ -840,9 +870,19 @@ Task(
     </quality_gate>
 
     <output>
-    Write to: .planning/research/PITFALLS.md
     Required sections: ## Common Mistakes, ## Warning Signs, ## Prevention Strategies
     </output>
+
+    **WRITE ACTION REQUIRED — You MUST use your file-write tool to write PITFALLS.md to disk. Do NOT output the content to the conversation. Do NOT treat this as done until the file physically exists on disk.**
+
+    Write the research content to `.planning/research/PITFALLS.md` using your write tool now.
+
+    Then verify:
+    ```
+    node -e "const fs=require('fs');const f='.planning/research/PITFALLS.md';if(!fs.existsSync(f)){console.log('PITFALLS_MISSING');process.exit(1);}console.log('PITFALLS_OK — '+fs.readFileSync(f,'utf8').length+' chars');"
+    ```
+
+    If `PITFALLS_MISSING`: write the file and re-run until `PITFALLS_OK`.
   "
 )
 ```
@@ -880,11 +920,22 @@ Task(
     </downstream_consumer>
 
     <output>
-    Write to: .planning/research/SUMMARY.md
     Required sections: ## Executive Summary, ## Recommended Stack, ## Table Stakes Features, ## Key Architecture Decisions, ## Top Pitfalls, ## Implications for Roadmap, ## Confidence Assessment, ## Gaps
     </output>
 
+    **WRITE ACTION REQUIRED — You MUST use your file-write tool to write SUMMARY.md to disk. Do NOT output the content to the conversation. Do NOT treat this as done until the file physically exists on disk.**
+
+    Write the synthesized content to `.planning/research/SUMMARY.md` using your write tool now.
+
+    Then verify it was written:
+    ```
+    node -e "const fs=require('fs');const f='.planning/research/SUMMARY.md';if(!fs.existsSync(f)){console.log('SUMMARY_MISSING');process.exit(1);}const c=fs.readFileSync(f,'utf8');const secs=['Executive Summary','Recommended Stack','Top Pitfalls','Implications for Roadmap'];const missing=secs.filter(s=>!c.includes(s));if(missing.length){console.log('SUMMARY_INCOMPLETE — missing: '+missing.join(', '));process.exit(1);}console.log('SUMMARY_OK — '+c.length+' chars');"
+    ```
+
+    If `SUMMARY_MISSING` or `SUMMARY_INCOMPLETE`: write the file and re-run until `SUMMARY_OK`.
+
     <quality_gate>
+    - [ ] File physically written to .planning/research/SUMMARY.md (verified by node -e above)
     - [ ] Synthesized, not concatenated — findings are integrated
     - [ ] Opinionated — clear recommendations emerge
     - [ ] Actionable — roadmapper can structure phases from implications

package/learnship/workflows/plan-phase.md

@@ -139,9 +139,19 @@ Task(
     </files_to_read>
 
     <output>
-    Write to: .planning/phases/[padded_phase]-[phase_slug]/[padded_phase]-RESEARCH.md
     Required sections: ## Don't Hand-Roll, ## Common Pitfalls, ## Existing Patterns in This Codebase, ## Recommended Approach
     </output>
+
+    **WRITE ACTION REQUIRED — You MUST use your file-write tool to write [padded_phase]-RESEARCH.md to disk. Do NOT output the content to the conversation. Do NOT treat this as done until the file physically exists on disk.**
+
+    Write the research content to `.planning/phases/[padded_phase]-[phase_slug]/[padded_phase]-RESEARCH.md` using your write tool now.
+
+    Then verify:
+    ```
+    node -e "const fs=require('fs');const files=fs.readdirSync('.planning/phases/').flatMap(d=>fs.readdirSync('.planning/phases/'+d).filter(f=>f.endsWith('-RESEARCH.md')).map(f=>'.planning/phases/'+d+'/'+f));if(!files.length){console.log('RESEARCH_MISSING');process.exit(1);}console.log('RESEARCH_OK — '+files[files.length-1]);"
+    ```
+
+    If `RESEARCH_MISSING`: write the file and re-run until `RESEARCH_OK`.
   "
 )
 ```
@@ -225,9 +235,19 @@ Task(
     </files_to_read>
 
     <output>
-    Write to: [phase_dir]/[padded_phase]-01-PLAN.md, [padded_phase]-02-PLAN.md, etc.
     Each plan must have: YAML frontmatter (wave, depends_on, files_modified) + tasks in XML + must_haves section
     </output>
+
+    **WRITE ACTION REQUIRED — You MUST use your file-write tool to write each PLAN.md to disk. Do NOT output plans to the conversation. Do NOT treat this as done until files physically exist on disk.**
+
+    Write each plan to `[phase_dir]/[padded_phase]-NN-PLAN.md` using your write tool now. Write all plans before reporting done.
+
+    Then verify:
+    ```
+    node -e "const fs=require('fs');const plans=fs.readdirSync('.').filter(f=>f.endsWith('-PLAN.md'));if(!plans.length){console.log('PLANS_MISSING');process.exit(1);}console.log('PLANS_OK — '+plans.length+' plan(s): '+plans.join(', '));"
+    ```
+
+    Run that command from inside [phase_dir]. If `PLANS_MISSING`: write the files and re-run until `PLANS_OK`.
   "
 )
 ```

package/learnship/workflows/quick.md

@@ -118,7 +118,7 @@ Write `CONTEXT.md` to the task directory:
 ### [Area discussed]
 - [Decision captured]
 
-### Claude's Discretion
+### Agent's Discretion
 [Areas not discussed or "you decide" answers]
 
 </decisions>

package/learnship/workflows/research-phase.md

@@ -109,9 +109,19 @@ Task(
     </files_to_read>
 
     <output>
-    Write to: .planning/phases/[padded_phase]-[slug]/[padded_phase]-RESEARCH.md
     Required sections: ## Don't Hand-Roll, ## Common Pitfalls, ## Existing Patterns in This Codebase, ## Recommended Approach
     </output>
+
+    **WRITE ACTION REQUIRED — You MUST use your file-write tool to write [padded_phase]-RESEARCH.md to disk. Do NOT output the content to the conversation. Do NOT treat this as done until the file physically exists on disk.**
+
+    Write the research content to `.planning/phases/[padded_phase]-[slug]/[padded_phase]-RESEARCH.md` using your write tool now.
+
+    Then verify:
+    ```
+    node -e "const fs=require('fs');const files=fs.readdirSync('.planning/phases/').flatMap(d=>fs.readdirSync('.planning/phases/'+d).filter(f=>f.endsWith('-RESEARCH.md')).map(f=>'.planning/phases/'+d+'/'+f));if(!files.length){console.log('RESEARCH_MISSING');process.exit(1);}console.log('RESEARCH_OK — '+files[files.length-1]);"
+    ```
+
+    If `RESEARCH_MISSING`: write the file and re-run until `RESEARCH_OK`.
   "
 )
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "learnship",
-  "version": "2.3.4",
+  "version": "2.3.6",
   "description": "Learn as you build. Build with intent. — A multi-platform agentic engineering system for Windsurf, Claude Code, Cursor, OpenCode, Gemini CLI, and Codex: 57 spec-driven workflows, 17 specialist agent personas, integrated learning, and production-grade design.",
   "keywords": [
     "agentic",