synthesis-explore
Synthesis EXPLORE stage for the Diffmode growth-tactics pipeline (fuses the blind-combination draw + emergent-mechanism derivation — formerly two separate synthesis steps — into ONE structural-check-only stage). Reads the per-run growth-factors.json (LIGHT vector DB) + synthesis-constraints.json + founder-input + audience-jtbd + the 3 think-tank reports; draws vector combinations BLIND (IDs only, before any analysis), runs the Stripped Core Action Test + prohibited-combination + must_include checks, then derives the NOVEL MECHANISM that EMERGES from each (Reframing Test, structural-advantage c
npx skills add acogood/diffmode_free --skill synthesis-explore --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Synthesis — Explore (Phase 1 Blind Combinations → Phase 2 Emergent Mechanisms) This is the FIRST synthesis stage. It fuses two jobs that MUST stay ordered: **Phase 1** draws vector combinations BLIND (vector-first, before any tactic exists), and **Phase 2** derives the NOVEL MECHANISM that emerges from each combination. Vector-first thinking is the novelty engine: you commit to combinations BEFORE knowing what tactic they might produce, which is how you escape conventional playbooks. **Output: 15-20 raw vector combinations + 12-18 validated mechanisms. NO TACTIC NAMES. NO EXECUTION STEPS.** (Tactic design is synthesis-build's job.) Vectors and their definitions come from the per-run `growth-factors.json` (the LIGHT DB). Do NOT read `tactics_DB/` (clean-room — moat-critical). The category structure and `{prefix}-NNN-slug` ID format are shared conventions; the specific IDs are whatever this run mined. ## The two phases are WALLED — do them strictly in order **You MUST complete Phase 1 (blind draw + combinations) in FULL before starting Phase 2 (mechanisms).** The output must physically PROVE this ordering: the section `## Blind Draw (IDs only)` must precede `## Vector Combinations`
- The two phases are WALLED — do them strictly in order
- Inputs & Output
- Critical Rules
- Conventional Outcome Detection (BLOCKING)
- Blind Vector Selection (BEFORE ANY ANALYSIS)
- Process
- Stripped Core Action Test (BLOCKING — run for EVERY combination)
- Conventional Detection Gate (BLOCKING)
- Structural Advantage Types (classify each mechanism)
- Execution Prototype (REQUIRED before validation — plain English, no jargon)
- Guerrilla Lens (tag each mechanism — positive novelty, not a gate)
- Mid-Generation Diversity Check (after mechanisms #5, #10, #15)
- Action Deduplication (verb-group — OUTPUT INVALID IF FAILED)
- Validation Checkpoint (before synthesis-build)
What does the synthesis-explore skill do?
Synthesis EXPLORE stage for the Diffmode growth-tactics pipeline (fuses the blind-combination draw + emergent-mechanism derivation — formerly two separate synthesis steps — into ONE structural-check-only stage). Reads the per-run growth-factors.json (LIGHT vector DB) + synthesis-constraints.json + founder-input + audience-jtbd + the 3 think-tank reports; draws vector combinations BLIND (IDs only, before any analysis), runs the Stripped Core Action Test + prohibited-combination + must_include checks, then derives the NOVEL MECHANISM that EMERGES from each (Reframing Test, structural-advantage c
How do I install it?
Run `npx skills add acogood/diffmode_free --skill synthesis-explore --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From acogood/diffmode_free, a repository with 153 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.