learnship 2.0.6 → 2.0.8

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "learnship",
   "description": "Agentic engineering done right — 49 structured workflows, 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.0.6",
+  "version": "2.0.8",
   "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 — 49 structured workflows, persistent memory across sessions, integrated learning partner, and impeccable UI design system.",
-  "version": "2.0.6",
+  "version": "2.0.8",
   "logo": "assets/logo.png",
   "author": {
     "name": "Favio Vazquez",

package/gemini-extension.json

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

package/learnship/templates/agents.md

@@ -204,7 +204,16 @@ When a new decision is made during a session, capture it with `/decision-log`.
 
 ### Solutions Store
 
-Compounded solutions live in `.planning/solutions/` — organized by category (build-errors, runtime-errors, best-practices, etc.) with YAML frontmatter for searchability. After fixing a bug or completing a notable feature, run `/compound` to capture the solution while context is fresh. The `/plan-phase` workflow automatically searches these before planning.
+Compounded solutions live in `.planning/solutions/` — organized by category (build-errors, runtime-errors, best-practices, etc.) with YAML frontmatter for searchability. The `/plan-phase` workflow automatically searches these before planning.
+
+**Run `/compound` after any of these events — do not skip:**
+- Fixing a bug (especially root-cause discoveries)
+- Completing a phase (`execute-phase` → `verify-work` → `/compound`)
+- Shipping a feature (`/ship` → `/compound`)
+- Any aha moment or pattern discovery during development
+- Resolving a debugging session (`/debug` → `/compound`)
+
+Context fades fast. If a solution was worth finding, it's worth capturing.
 
 ---
 

package/learnship/workflows/audit-milestone.md

@@ -154,6 +154,8 @@ Status: [PASSED ✓ | GAPS FOUND ⚠️]
 Milestone [VERSION] is ready to ship.
 
 ▶ Next: complete-milestone
+
+💡 Run `/sync-docs` first to check for stale documentation before release.
 ```
 
 **If GAPS FOUND:**
@@ -164,6 +166,8 @@ Milestone [VERSION] is ready to ship.
 
 ▶ Next: plan-milestone-gaps — create fix phases for all gaps
     OR: complete-milestone — ship anyway (mark gaps as known issues)
+
+💡 Run `/sync-docs` to check for stale documentation alongside the gap fixes.
 ```
 
 ---

package/learnship/workflows/discuss-phase.md

@@ -224,6 +224,9 @@ Created: .planning/phases/[padded_phase]-[slug]/[padded_phase]-CONTEXT.md
 ---
 
 ▶ Next Up: plan-phase [X]
+
+💡 Ambitious scope? `/challenge` — stress-test the approach before planning
+💡 Made important decisions? `/compound` — capture them while context is fresh
 ```
 
 ---

package/learnship/workflows/execute-phase.md

@@ -329,6 +329,14 @@ If `AGENTS.md` exists at the project root, update the `## Current Phase` block t
 
 Also append any newly created key files or modules to the `## Project Structure` tree if significant new directories were created during this phase.
 
+**Post-update verification (cross-platform):**
+
+```bash
+node -e "const fs=require('fs');if(!fs.existsSync('AGENTS.md')){process.exit(0);}const f=fs.readFileSync('AGENTS.md','utf8');const required=['Soul','Principles','Request Routing Protocol','Platform Context','Current Phase','Project Structure','Tech Stack','Skills','Regressions'];const missing=required.filter(s=>!f.includes('## '+s));if(missing.length){console.log('AGENTS.md sections lost during update:\\n'+missing.map(s=>'  ## '+s).join('\\n'));process.exit(1);}console.log('AGENTS.md sections intact');"
+```
+
+> If verification fails, restore the missing sections from `@./templates/agents.md` before committing.
+
 ```bash
 git add AGENTS.md
 git commit -m "docs: update AGENTS.md — phase [X] complete"

package/learnship/workflows/ls.md

@@ -30,6 +30,8 @@ spec-driven phases, context-engineered plans, atomic execution,
 and a learning partner woven into every phase transition.
 
 ▶ To start: /new-project
+▶ Not sure what to build? `@agentic-learning brainstorm [idea]` — think through it first
+▶ Have an existing codebase? /ideate — scan for improvement opportunities
 ▶ For a quick one-off task: /quick "description"
 ▶ To see all commands: /help
 ```

package/learnship/workflows/new-project.md

@@ -243,6 +243,13 @@ Based on all previous answers, ask a third follow-up that clarifies scope, edge
 
 **Gate check — before proceeding to Step 4:**
 
+> 🛑 **HARD GATE — count your messages.** Before continuing, verify:
+> 1. You sent exactly **4 separate question messages** (Exchanges 1–4)
+> 2. You received exactly **4 separate user answers** (`ANSWER_1` through `ANSWER_4`)
+> 3. Each answer came from a **different user message** (not extracted from one long reply)
+>
+> If any count is wrong, go back and complete the missing exchanges. Do NOT proceed with fewer than 4 exchanges under any circumstances — even if the user's first answer was extremely detailed.
+
 Verify internally: do you have `ANSWER_1`, `ANSWER_2`, `ANSWER_3`, and `ANSWER_4` recorded? If any is missing, go back and ask it. Only after all four answers are in hand may you ask:
 
 "I think I have a solid picture of what you're building. Ready for me to write PROJECT.md, or is there more you want to cover first?"
@@ -291,14 +298,46 @@ Ask: **"Before I write the requirements — do you want me to research the domai
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
-Run 4 research passes sequentially. Each writes a file to `.planning/research/`:
+Run 4 research passes sequentially. Each writes a file to `.planning/research/` with **mandatory sections** as specified below. Do not write freeform prose — each file must contain the required `##` headers.
+
+1. **STACK.md** — Standard tech stack for this domain
+   - Required sections: `## Recommended Stack`, `## Alternatives Considered`, `## What NOT to Use` (with reasons), `## Versions`
+2. **FEATURES.md** — What features exist in this domain
+   - Required sections: `## Table Stakes` (must-haves), `## Differentiators` (nice-to-haves), `## Anti-Features` (what to avoid)
+3. **ARCHITECTURE.md** — How systems in this domain are typically structured
+   - Required sections: `## Component Boundaries`, `## Data Flow`, `## Build Order` (suggested sequence), `## Integration Points`
+4. **PITFALLS.md** — Common mistakes and prevention strategies
+   - Required sections: `## Common Mistakes`, `## Warning Signs`, `## Prevention Strategies`
+
+After all four complete, synthesize into `.planning/research/SUMMARY.md`:
+   - Required sections: `## Recommended Stack`, `## Table Stakes Features`, `## Key Architecture Decisions`, `## Top Pitfalls`
 
-1. **STACK.md** — Standard tech stack for this domain (specific libraries, versions, what NOT to use and why)
-2. **FEATURES.md** — What features exist in this domain: table stakes vs. differentiators vs. anti-features
-3. **ARCHITECTURE.md** — How systems in this domain are typically structured, component boundaries, data flow, suggested build order
-4. **PITFALLS.md** — Common mistakes, warning signs, prevention strategies
+**Post-research verification (cross-platform):**
+
+```bash
+node -e "
+const fs=require('fs'),path=require('path');
+const dir='.planning/research/';
+const checks={
+  'STACK.md':['Recommended Stack','What NOT to Use'],
+  'FEATURES.md':['Table Stakes','Differentiators'],
+  'ARCHITECTURE.md':['Component Boundaries','Data Flow'],
+  'PITFALLS.md':['Common Mistakes','Prevention Strategies'],
+  'SUMMARY.md':['Recommended Stack','Top Pitfalls']
+};
+const missing=[];
+for(const[file,sections]of Object.entries(checks)){
+  const fp=path.join(dir,file);
+  if(!fs.existsSync(fp)){missing.push(file+' MISSING');continue;}
+  const c=fs.readFileSync(fp,'utf8');
+  for(const s of sections){if(!c.includes('## '+s))missing.push(file+': missing ## '+s);}
+}
+if(missing.length){console.log('RESEARCH INCOMPLETE:\\n'+missing.join('\\n'));process.exit(1);}
+console.log('RESEARCH VERIFIED OK');
+"
+```
 
-After all four complete, synthesize into `.planning/research/SUMMARY.md` covering: recommended stack, table stakes features, key architecture decisions, top pitfalls to avoid.
+> 🛑 If verification fails, fix the missing files or sections before proceeding. Do not skip research verification.
 
 Display key findings:
 ```
@@ -438,6 +477,7 @@ Populate the `## Project Structure` tree with real directories and one-line desc
 - [ ] File starts with `# AGENTS.md — [Project Name]`
 - [ ] `## Soul — Who We Are Together` exists with Voice & Character and Relationship Model
 - [ ] `## Principles — How We Operate` exists with all 10 numbered principles
+- [ ] `## Request Routing Protocol` exists with decision tree
 - [ ] `## Platform Context` exists with the 7-step phase loop
 - [ ] `## Current Phase` exists with milestone, phase, status, and date
 - [ ] `## Project Structure` exists with a directory tree
@@ -445,6 +485,14 @@ Populate the `## Project Structure` tree with real directories and one-line desc
 - [ ] `## Skills — Operational Knowledge` exists with CHANGELOG Discipline and Decisions Register
 - [ ] `## Regressions — What Broke and What We Learned` exists at the end
 
+**Automated verification (cross-platform — run this, do not skip):**
+
+```bash
+node -e "const fs=require('fs');if(!fs.existsSync('AGENTS.md')){console.log('AGENTS.md NOT FOUND');process.exit(1);}const f=fs.readFileSync('AGENTS.md','utf8');const required=['Soul','Principles','Request Routing Protocol','Platform Context','Current Phase','Project Structure','Tech Stack','Skills','Regressions'];const missing=required.filter(s=>!f.includes('## '+s));if(missing.length){console.log('AGENTS.md INCOMPLETE — missing sections:\\n'+missing.map(s=>'  ## '+s).join('\\n'));process.exit(1);}console.log('AGENTS.md VERIFIED OK — all '+required.length+' mandatory sections present');"
+```
+
+> 🛑 If verification fails, fix the missing sections before committing. Do NOT proceed to Step 9 with an incomplete AGENTS.md. Re-read `@./templates/agents.md` and add the missing sections.
+
 **If `commit_mode` is `auto`:**
 ```bash
 git add AGENTS.md && git commit -m "docs: add AGENTS.md with project context"

package/learnship/workflows/next.md

@@ -19,10 +19,14 @@ node -e "const fs=require('fs'); console.log(fs.existsSync('.planning/PROJECT.md
 **If MISSING:**
 
 ```
-No project found. Starting /new-project...
+No project found.
+
+▶ Starting: /new-project — initialize a new project
+▶ Not sure what to build? `@agentic-learning brainstorm [idea]` — think through it first
+▶ Have an existing codebase? /ideate — scan for improvement opportunities
 ```
 
-Immediately run the `new-project` workflow. Stop here.
+Ask the user which option they'd like. If they choose `/new-project` or don't specify, run the `new-project` workflow. Stop here.
 
 ---
 

package/learnship/workflows/quick.md

@@ -238,6 +238,9 @@ Summary: .planning/quick/[NEXT_NUM]-[SLUG]/[NEXT_NUM]-SUMMARY.md
 [If --full: Verification: [status]]
 Commit: [hash]
 
+💡 Solved something notable? `/compound` — capture the solution while context is fresh
+💡 Ready to push? `/ship` — test → commit → push → PR
+
 Ready for next task: quick
 ```
 

package/package.json

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