learnship 2.0.9 → 2.0.10
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 — 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.",
|
|
4
|
-
"version": "2.0.
|
|
4
|
+
"version": "2.0.10",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Favio Vazquez",
|
|
7
7
|
"email": "favio.vazquezp@gmail.com"
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"name": "learnship",
|
|
3
3
|
"displayName": "learnship",
|
|
4
4
|
"description": "Agentic engineering done right — 49 structured workflows, persistent memory across sessions, integrated learning partner, and impeccable UI design system.",
|
|
5
|
-
"version": "2.0.
|
|
5
|
+
"version": "2.0.10",
|
|
6
6
|
"logo": "assets/logo.png",
|
|
7
7
|
"author": {
|
|
8
8
|
"name": "Favio Vazquez",
|
package/SKILL.md
CHANGED
|
@@ -110,11 +110,13 @@ Does .planning/PROJECT.md exist?
|
|
|
110
110
|
|
|
111
111
|
When running `/new-project`, these are non-negotiable hard gates. Violating any of them produces a broken project:
|
|
112
112
|
|
|
113
|
-
1. **Research =
|
|
113
|
+
1. **Research decision = always ask the user.** After PROJECT.md is confirmed, you MUST ask: "Do you want me to research the domain ecosystem first?" and WAIT for a reply. You are FORBIDDEN from deciding this yourself — even if the tech stack is defined in PROJECT.md, the domain seems trivial, or the user gave detailed answers. Never say "no research needed" or "skipping research" on your own.
|
|
114
114
|
|
|
115
|
-
2. **
|
|
115
|
+
2. **Research = 5 separate files.** If the user chooses research, you MUST create exactly 5 files in `.planning/research/`: `STACK.md`, `FEATURES.md`, `ARCHITECTURE.md`, `PITFALLS.md`, `SUMMARY.md`. Do NOT write a single monolithic research file. After writing all 5, run the `node -e` verification command from the workflow. If it fails, fix the files before proceeding.
|
|
116
116
|
|
|
117
|
-
3. **
|
|
117
|
+
3. **AGENTS.md = copy from template.** Read `@./templates/agents.md` BEFORE writing AGENTS.md. Sections marked "copy VERBATIM" must be copied word-for-word — do not rewrite, summarize, or rephrase them. After writing, run the `node -e` verification command. If it fails, fix AGENTS.md before proceeding.
|
|
118
|
+
|
|
119
|
+
4. **Done = STOP.** After displaying the Step 9 done banner, **STOP completely**. Do NOT automatically start `/discuss-phase 1`. Do NOT say "Let me start Phase 1" or "Now starting Phase 1." Wait for the user to type their next command.
|
|
118
120
|
|
|
119
121
|
## Key Behaviors
|
|
120
122
|
|
|
@@ -45,7 +45,7 @@ When the user runs `/new-project`, execute these **9 mandatory steps in order**.
|
|
|
45
45
|
|
|
46
46
|
1. **Exchange 1 answer does NOT skip Exchanges 2–4.** No matter how detailed the user's answer to "What do you want to build?" — it is raw material for follow-ups, not a replacement. You MUST still ask Exchanges 2, 3, and 4.
|
|
47
47
|
|
|
48
|
-
2. **
|
|
48
|
+
2. **Research decision = always ask the user.** After PROJECT.md is confirmed, ask: "Do you want me to research the domain ecosystem first?" and WAIT for the user's reply. You are FORBIDDEN from deciding this yourself — even if the tech stack is defined in PROJECT.md, the domain seems trivial, or the user gave detailed answers. Never say "no research needed" or "skipping research" on your own.
|
|
49
49
|
|
|
50
50
|
3. **Research = 5 separate files.** If the user chooses research, create exactly 5 files in `.planning/research/`: `STACK.md`, `FEATURES.md`, `ARCHITECTURE.md`, `PITFALLS.md`, `SUMMARY.md`. Do NOT write a single monolithic research file. Run the `node -e` verification command from the workflow — it must print `RESEARCH VERIFIED OK` before proceeding.
|
|
51
51
|
|
package/gemini-extension.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "learnship",
|
|
3
|
-
"version": "2.0.
|
|
3
|
+
"version": "2.0.10",
|
|
4
4
|
"description": "Agentic engineering done right — 49 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/",
|
|
@@ -282,13 +282,47 @@ git add .planning/PROJECT.md && git commit -m "docs: initialize project"
|
|
|
282
282
|
|
|
283
283
|
## Step 5: Research Decision
|
|
284
284
|
|
|
285
|
-
> **🔴 MANDATORY USER CHOICE — You must ask this question and wait for a reply. You are NOT allowed to decide this yourself
|
|
285
|
+
> **🔴 MANDATORY USER CHOICE — You must ask this question and wait for a reply. You are NOT allowed to decide this yourself.**
|
|
286
286
|
|
|
287
|
-
|
|
288
|
-
- **Research first** (recommended) — Discover standard stacks, expected features, architecture patterns
|
|
289
|
-
- **Skip research** — I know this domain well, go straight to requirements
|
|
287
|
+
Display this question to the user exactly as written:
|
|
290
288
|
|
|
291
|
-
|
|
289
|
+
```
|
|
290
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
291
|
+
learnship ► RESEARCH DECISION
|
|
292
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
293
|
+
|
|
294
|
+
Before I write the requirements — do you want me to
|
|
295
|
+
research the domain ecosystem first?
|
|
296
|
+
|
|
297
|
+
1. Research first (recommended)
|
|
298
|
+
→ Discover standard stacks, expected features,
|
|
299
|
+
architecture patterns, common pitfalls
|
|
300
|
+
|
|
301
|
+
2. Skip research
|
|
302
|
+
→ Go straight to requirements
|
|
303
|
+
|
|
304
|
+
Reply 1 or 2.
|
|
305
|
+
```
|
|
306
|
+
|
|
307
|
+
> � **HARD GATE — This is a user decision. You MUST wait for the user to reply.**
|
|
308
|
+
>
|
|
309
|
+
> **You are FORBIDDEN from deciding this yourself.** It does not matter if:
|
|
310
|
+
> - The tech stack is already defined in PROJECT.md
|
|
311
|
+
> - The domain seems trivial or well-understood
|
|
312
|
+
> - You already know the ecosystem
|
|
313
|
+
> - The user gave detailed answers in Deep Questioning
|
|
314
|
+
> - The project seems simple
|
|
315
|
+
>
|
|
316
|
+
> **None of these are valid reasons to skip the question.** The user ALWAYS gets asked. The user ALWAYS decides.
|
|
317
|
+
>
|
|
318
|
+
> **Forbidden responses (do NOT say anything like these):**
|
|
319
|
+
> - "The tech stack is already well-defined in PROJECT.md. No research needed."
|
|
320
|
+
> - "Since you've already described the stack, I'll skip research."
|
|
321
|
+
> - "Moving straight to requirements/roadmap."
|
|
322
|
+
> - "Research isn't necessary for this project."
|
|
323
|
+
> - Any sentence that contains "no research needed" or "skip research" that you wrote yourself (not the user).
|
|
324
|
+
>
|
|
325
|
+
> **The ONLY acceptable next action is: display the question above and wait.** Do not write REQUIREMENTS.md. Do not write ROADMAP.md. Do not proceed to Step 6. Wait for the user's reply.
|
|
292
326
|
|
|
293
327
|
**If Research first:**
|
|
294
328
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "learnship",
|
|
3
|
-
"version": "2.0.
|
|
3
|
+
"version": "2.0.10",
|
|
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",
|