specsmd 0.0.0-dev.83 → 0.0.0-dev.84

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.
@@ -21,11 +21,14 @@ Generate genuinely diverse, surprising ideas through rapid batches. AI is the cr
21
21
  <llm critical="true">
22
22
  <mandate>NEVER ask setup questions — generate ideas immediately on receiving a topic</mandate>
23
23
  <mandate>NEVER name techniques to the user — use them internally, present only the ideas</mandate>
24
- <mandate>NEVER generate 2+ ideas from the same domain in a batch — enforce anti-bias</mandate>
25
24
  <mandate>ALWAYS use the deep thinking protocol before generating each batch</mandate>
26
25
  <mandate>ALWAYS present ideas as vivid, specific, memorable concepts — not abstract descriptions</mandate>
27
26
  <mandate>NEVER more than 2 questions in a row — always generate something creative first</mandate>
28
- <mandate>CRITICAL ANTI-BIAS: Each batch of 5 ideas MUST draw from 3+ DIFFERENT domains from the 12-sector domain wheel (Technology, Psychology, Business, Nature, Art, Games, Social, Space, Time, Extreme, Inversion, Random). Tag each idea with its domain. If all 5 ideas are about technology/engineering, the batch FAILS — regenerate with cross-domain diversity.</mandate>
27
+ <mandate>ANTI-BIAS MATCH DIVERSITY TO TOPIC TYPE:
28
+ - For OPEN/CREATIVE topics (product ideas, business concepts, experiences): use the domain wheel aggressively — 3+ different domains per batch, cross-domain metaphors welcome
29
+ - For TECHNICAL/ARCHITECTURAL topics (system design, integration decisions, API design): diversity means different PERSPECTIVES and ANGLES on the same technical space — architecture, developer experience, tradeoffs, migration strategy, patterns from other systems. Do NOT force nature/art/games metaphors onto technical decisions. The ideas should feel like they came from 5 different senior engineers, not 5 different departments.
30
+ - When in doubt, match the user's register. If they're talking code, give them code-level ideas.
31
+ </mandate>
29
32
  </llm>
30
33
 
31
34
  <protocols>
@@ -65,12 +68,12 @@ Generate genuinely diverse, surprising ideas through rapid batches. AI is the cr
65
68
  <action>Execute the deep thinking protocol (see shared/protocols/deep-thinking.md)</action>
66
69
  <action>Perform 6-step reasoning chain:</action>
67
70
  <reasoning>
68
- [Think 1 — Domain Check]: Which domains from the domain wheel are underexplored? Select 3+ for this batch.
69
- [Think 2 — Raw Concepts]: Generate raw ideas — one per selected domain. Use a technique internally (SCAMPER, analogy, inversion, etc.).
71
+ [Think 1 — Angle Check]: What topic type is this? For creative/open topics, pick 3+ domain wheel sectors. For technical topics, pick 3+ different perspectives (architecture, DX, tradeoffs, patterns, prior art, migration, cost). Either way, ensure the batch won't feel repetitive.
72
+ [Think 2 — Raw Concepts]: Generate raw ideas — one per selected angle. Use techniques internally (SCAMPER, analogy, inversion, first-principles, etc.) but keep ideas grounded in the user's actual domain.
70
73
  [Think 3 — Novelty Filter]: Are these genuinely new or just repackaged versions of obvious ideas? Replace any that feel generic.
71
74
  [Think 4 — Cross-pollinate]: Can any ideas combine with user's stated favorites? Create unexpected connections.
72
- [Think 5 — Provocation]: If provocation is due (every 15 ideas), inject one deliberately absurd idea. Otherwise, ensure at least one idea challenges assumptions.
73
- [Think 6 — Polish]: Make each idea vivid, specific, and memorable. Not "use gamification" but "a quest system where each completed task unlocks a new tool."
75
+ [Think 5 — Provocation]: If provocation is due (every 15 ideas), inject one deliberately unconventional idea. Otherwise, ensure at least one idea challenges assumptions.
76
+ [Think 6 — Polish]: Make each idea vivid, specific, and memorable. Match the user's register if they're talking about code, give them code-level specificity, not abstract metaphors.
74
77
  </reasoning>
75
78
  </step>
76
79
 
@@ -79,16 +82,13 @@ Generate genuinely diverse, surprising ideas through rapid batches. AI is the cr
79
82
  <format>
80
83
  **S{batch}-{number}** — {vivid idea title}
81
84
  {2-3 sentence description — specific, concrete, imaginative}
82
- *Domain: {domain from the 12-sector wheel}*
83
85
  </format>
84
86
  <action>Number ideas sequentially across batches (S1-1, S1-2... S2-1, S2-2...)</action>
85
- <anti_bias critical="true">
86
- BEFORE presenting the batch, verify:
87
- 1. Count unique domains — MUST be 3 or more different domains
88
- 2. No 2 consecutive ideas from the same domain
89
- 3. If all ideas are from Technology/Engineering, STOP and regenerate with cross-domain diversity
90
- Example of a GOOD batch: Technology, Nature, Games, Psychology, Business (5 different domains)
91
- Example of a BAD batch: Technology, Technology, Technology, Technology, Technology (1 domain — REJECT)
87
+ <anti_bias>
88
+ BEFORE presenting the batch, verify diversity:
89
+ - For creative/open topics: 3+ different domain wheel sectors
90
+ - For technical topics: 3+ different perspectives (e.g., architecture, DX, tradeoffs, patterns, migration)
91
+ - No 2 consecutive ideas making the same argument from the same angle
92
92
  </anti_bias>
93
93
  </step>
94
94
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "specsmd",
3
- "version": "0.0.0-dev.83",
3
+ "version": "0.0.0-dev.84",
4
4
  "description": "Multi-agent orchestration system for AI-native software development. Delivers AI-DLC, Agile, and custom SDLC flows as markdown-based agent systems.",
5
5
  "main": "lib/installer.js",
6
6
  "bin": {