learnship 1.9.0 → 1.9.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "learnship",
3
3
  "description": "Agentic engineering done right — 42 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.",
4
- "version": "1.9.0",
4
+ "version": "1.9.1",
5
5
  "author": {
6
6
  "name": "Favio Vazquez",
7
7
  "email": "favio.vazquez@gmail.com"
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "learnship",
3
3
  "description": "Agentic engineering done right — 42 structured workflows, persistent memory across sessions, integrated learning partner, and impeccable UI design system.",
4
- "version": "1.9.0",
4
+ "version": "1.9.1",
5
5
  "author": {
6
6
  "name": "Favio Vazquez",
7
7
  "email": "favio.vazquez@gmail.com"
package/bin/install.js CHANGED
File without changes
package/bin/learnship.js CHANGED
File without changes
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "learnship",
3
- "version": "1.9.0",
3
+ "version": "1.9.1",
4
4
  "description": "Agentic engineering done right — 42 structured workflows, persistent memory across sessions, integrated learning partner, and impeccable UI design system.",
5
5
  "author": "Favio Vazquez",
6
6
  "homepage": "https://faviovazquez.github.io/learnship/",
@@ -164,12 +164,16 @@ Synthesize all gathered context into `.planning/PROJECT.md` using `@./templates/
164
164
  git add .planning/PROJECT.md && git commit -m "docs: initialize project"
165
165
  ```
166
166
 
167
+ > **⚠ STOP — do not proceed to Step 5 until you have asked the research question below and received the user's answer.**
168
+
167
169
  ## Step 5: Research Decision
168
170
 
169
171
  Ask: "Research the domain ecosystem before defining requirements?"
170
172
  - **Research first** (recommended) — Discover standard stacks, expected features, architecture patterns
171
173
  - **Skip research** — I know this domain well, go straight to requirements
172
174
 
175
+ > **⚠ STOP — wait for the user's choice before continuing.**
176
+
173
177
  **If Research first:**
174
178
 
175
179
  ```
@@ -202,6 +206,8 @@ Files: .planning/research/
202
206
 
203
207
  ## Step 6: Define Requirements
204
208
 
209
+ > **⚠ STOP — do not write REQUIREMENTS.md until you have presented feature categories to the user and received their v1 selections. This is an interactive step.**
210
+
205
211
  ```
206
212
  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
207
213
  learnship ► DEFINING REQUIREMENTS
@@ -224,6 +230,8 @@ Create `.planning/REQUIREMENTS.md` with v1 requirements (with REQ-IDs like `AUTH
224
230
 
225
231
  Present the full list for confirmation. If user wants adjustments, iterate.
226
232
 
233
+ > **⚠ STOP — wait for the user to confirm the requirements list before writing REQUIREMENTS.md or continuing.**
234
+
227
235
  **If `commit_mode` is `auto`:**
228
236
  ```bash
229
237
  git add .planning/REQUIREMENTS.md && git commit -m "docs: define v1 requirements"
@@ -266,6 +274,8 @@ Ask for approval:
266
274
  - **Adjust phases** → get feedback, revise, re-present
267
275
  - **Review full file** → show raw ROADMAP.md, then re-ask
268
276
 
277
+ > **⚠ STOP — do not proceed to Step 8 until the user has explicitly approved the roadmap.**
278
+
269
279
  **If `commit_mode` is `auto`:**
270
280
  ```bash
271
281
  git add .planning/ROADMAP.md .planning/STATE.md .planning/REQUIREMENTS.md && git commit -m "docs: create roadmap ([N] phases)"
@@ -273,6 +283,8 @@ git add .planning/ROADMAP.md .planning/STATE.md .planning/REQUIREMENTS.md && git
273
283
 
274
284
  ## Step 8: Generate AGENTS.md
275
285
 
286
+ > **🔴 MANDATORY — This step must always be completed. Do not skip it, do not defer it, do not move to Step 9 without writing AGENTS.md to the project root. AGENTS.md is the persistent memory file that every future session depends on.**
287
+
276
288
  Copy `@./templates/agents.md` to the project root as `AGENTS.md`.
277
289
 
278
290
  Fill in the placeholder sections using information gathered in this session:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "learnship",
3
- "version": "1.9.0",
3
+ "version": "1.9.1",
4
4
  "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.",
5
5
  "keywords": [
6
6
  "agentic",
@@ -50,7 +50,7 @@
50
50
  "license": "MIT",
51
51
  "author": "Favio Vazquez",
52
52
  "bin": {
53
- "learnship": "./bin/install.js"
53
+ "learnship": "./bin/learnship.js"
54
54
  },
55
55
  "scripts": {
56
56
  "start": "node bin/learnship.js",