@dzhechkov/keysarium 1.0.0 → 1.1.0

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.
Files changed (35) hide show
  1. package/README.md +36 -20
  2. package/package.json +1 -1
  3. package/src/cli.js +5 -5
  4. package/src/commands/doctor.js +13 -13
  5. package/src/commands/init.js +2 -2
  6. package/src/commands/list.js +3 -3
  7. package/src/commands/remove.js +2 -2
  8. package/src/commands/update.js +2 -2
  9. package/templates/.claude/commands/brain-export.md +121 -0
  10. package/templates/.claude/commands/brain-import.md +115 -0
  11. package/templates/.claude/rules/checkpoint-protocol.md +46 -0
  12. package/templates/.claude/rules/feedback-loops.md +113 -0
  13. package/templates/.claude/rules/model-routing.md +65 -0
  14. package/templates/.claude/rules/trust-tiers.md +36 -0
  15. package/templates/.claude/shards/phase-0-discovery.shard.md +45 -0
  16. package/templates/.claude/shards/phase-1-explore.shard.md +32 -0
  17. package/templates/.claude/shards/phase-2-research.shard.md +42 -0
  18. package/templates/.claude/shards/phase-25-cjm.shard.md +47 -0
  19. package/templates/.claude/shards/phase-3-solve.shard.md +47 -0
  20. package/templates/.claude/shards/phase-4-architecture.shard.md +41 -0
  21. package/templates/.claude/shards/phase-5-presentation.shard.md +56 -0
  22. package/templates/.claude/skills/explore/SKILL.md +7 -4
  23. package/templates/.claude/skills/frontend-design/SKILL.md +3 -0
  24. package/templates/.claude/skills/goap-research-ed25519/SKILL.md +3 -0
  25. package/templates/.claude/skills/presentation-storyteller/SKILL.md +5 -2
  26. package/templates/.claude/skills/problem-solver-enhanced/SKILL.md +3 -0
  27. package/templates/.claude/skills/reverse-engineering-unicorn/SKILL.md +3 -0
  28. package/templates/CLAUDE.md +55 -3
  29. package/templates/docs/improvement-directions.md +641 -0
  30. package/templates/docs/skills-bto/01-deployment-guide.md +33 -33
  31. package/templates/docs/skills-bto/02-admin-guide.md +13 -13
  32. package/templates/docs/skills-bto/03-user-guide.md +1 -1
  33. package/templates/docs/skills-bto/04-infrastructure-requirements.md +4 -4
  34. package/templates/docs/skills-bto/05-architecture.md +4 -4
  35. package/templates/docs/skills-bto/06-user-flows.md +1 -1
@@ -0,0 +1,113 @@
1
+ # Cross-Phase Feedback Loops
2
+
3
+ ## Purpose
4
+
5
+ Formalize how data flows between phases in the Keysarium pipeline.
6
+ Each loop has a name, direction, data payload, and namespace for persistence.
7
+
8
+ ## Named Feedback Loops
9
+
10
+ ### Loop 1: CJM → Solve (Critical)
11
+
12
+ | Property | Value |
13
+ |----------|-------|
14
+ | Direction | Phase 2.5 → Phase 3 |
15
+ | Variable | `{CHOSEN_CJM}` |
16
+ | Payload | Selected CJM variant (A/B/C/D), pain points, conversion metrics |
17
+ | Consumers | Phase 3 (User Flow), Phase 5 (Slide 5) |
18
+ | Persistence | `researches/<slug>/.feedback/cjm-selection.json` |
19
+
20
+ **Contract:** Phase 3 MUST NOT start without `{CHOSEN_CJM}` being set.
21
+
22
+ ### Loop 2: Research → Presentation
23
+
24
+ | Property | Value |
25
+ |----------|-------|
26
+ | Direction | Phase 2 → Phase 5 |
27
+ | Payload | Key findings, verified sources, statistics |
28
+ | Source file | `02_research_findings.md` |
29
+ | Consumers | Phase 5 (all slides referencing data) |
30
+ | Usage | Presentation claims must trace back to research findings |
31
+
32
+ **Contract:** Every data claim in presentation must have a source in `02_research_findings.md`.
33
+
34
+ ### Loop 3: Discovery → All Phases (Context)
35
+
36
+ | Property | Value |
37
+ |----------|-------|
38
+ | Direction | Phase 0 → Phases 1-5 |
39
+ | Payload | Domain detection, JTBD segments, competitive landscape, business case |
40
+ | Source file | `00_product_discovery.md` |
41
+ | Key fields | `{DOMAIN}`, `{PRIMARY_USER}`, `{AHA_MOMENT}` |
42
+
43
+ **Contract:** Domain-specific rules activate based on Phase 0 detection.
44
+
45
+ ### Loop 4: Solve → Architecture
46
+
47
+ | Property | Value |
48
+ |----------|-------|
49
+ | Direction | Phase 3 → Phase 4 |
50
+ | Payload | Chosen solution strategy, AI pipeline spec, HITL design, MVP scope |
51
+ | Source file | `03_solution_strategy.md` |
52
+ | Key fields | `{SOLUTION_CONCEPT}`, `{AI_PIPELINE}`, `{HITL_POLICY}` |
53
+
54
+ **Contract:** Architecture must implement the solution designed in Phase 3.
55
+
56
+ ### Loop 5: BTO Judges → Optimizer
57
+
58
+ | Property | Value |
59
+ |----------|-------|
60
+ | Direction | BTO Layer 2 → BTO Optimize |
61
+ | Payload | Per-dimension scores, judge feedback, weak dimensions |
62
+ | Source | Layer 2 evaluation reports |
63
+ | Key fields | `{BASELINE_SCORE}`, `{WEAK_DIMENSIONS}`, `{JUDGE_FEEDBACK}` |
64
+
65
+ **Contract:** Optimizer mutations target weak dimensions identified by judges.
66
+
67
+ ### Loop 6: History → Discovery (Cross-Case)
68
+
69
+ | Property | Value |
70
+ |----------|-------|
71
+ | Direction | Past cases → Phase 0 of new case |
72
+ | Payload | Domain patterns, common pitfalls, successful strategies |
73
+ | Source | `TOOLKIT_HARVEST.md`, brain export files |
74
+ | Persistence | `keysarium-brain.json` |
75
+
76
+ **Contract:** If brain file exists, Phase 0 loads historical patterns before starting.
77
+
78
+ ## Feedback Loop Protocol
79
+
80
+ ### At Phase Start
81
+ 1. Check upstream promises are met
82
+ 2. Load required source files
83
+ 3. Extract key variables from upstream outputs
84
+ 4. Apply domain-specific rules from Loop 3
85
+
86
+ ### At Phase End
87
+ 1. Emit phase promise tag
88
+ 2. Write key outputs for downstream consumers
89
+ 3. Validate contract fulfillment
90
+
91
+ ## Variable Registry
92
+
93
+ All cross-phase variables in one place:
94
+
95
+ | Variable | Set In | Used In | Type |
96
+ |----------|--------|---------|------|
97
+ | `{DOMAIN}` | Phase 0 | All phases | string (banking/retail/enterprise/healthcare) |
98
+ | `{PRIMARY_USER}` | Phase 0 | Phase 2.5, 3, 5 | string |
99
+ | `{AHA_MOMENT}` | Phase 0 | Phase 2.5, 5 | string |
100
+ | `{CHOSEN_CJM}` | Phase 2.5 | Phase 3, 5 | string (A/B/C/D) |
101
+ | `{SOLUTION_CONCEPT}` | Phase 3 | Phase 4, 5 | string |
102
+ | `{AI_PIPELINE}` | Phase 3 | Phase 4 | structured |
103
+ | `{HITL_POLICY}` | Phase 3 | Phase 4, 5 | structured |
104
+ | `{BASELINE_SCORE}` | BTO L2 | BTO Optimize | float |
105
+ | `{WEAK_DIMENSIONS}` | BTO L2 | BTO Optimize | list[string] |
106
+
107
+ ## Modular Reuse Note
108
+
109
+ This feedback loop system is domain-agnostic. The same pattern applies to any multi-phase pipeline:
110
+ 1. Define named loops with direction and payload
111
+ 2. Set contracts (what must exist before proceeding)
112
+ 3. Register variables in a central registry
113
+ 4. Validate contracts at phase boundaries
@@ -0,0 +1,65 @@
1
+ # Model Routing Enforcement
2
+
3
+ ## 3-Tier Model Routing
4
+
5
+ All agent spawning MUST follow the model routing table below.
6
+ Using a higher-cost model than necessary wastes budget.
7
+ Using a lower-cost model than required degrades quality.
8
+
9
+ ## Routing Table
10
+
11
+ | Tier | Model | Latency | When to Use |
12
+ |------|-------|---------|-------------|
13
+ | Tier 1 | haiku | ~500ms | File formatting, simple transforms, Layer 0 checks, Layer 1 quick eval, BTO variant fast-ranking |
14
+ | Tier 2 | sonnet | ~2s | Research synthesis, analysis, BTO Layer 2 judge panel, mutation workers, meta-judge escalation |
15
+ | Tier 3 | opus (default) | ~5s | Creative CJM design, presentation storytelling, BTO crossover synthesis, complex problem solving |
16
+
17
+ ## Per-Task Assignment
18
+
19
+ ### Keysarium Pipeline
20
+
21
+ | Task | Model | Rationale |
22
+ |------|-------|-----------|
23
+ | Phase 0 parallel agents (JTBD, Competitors) | sonnet | Research synthesis |
24
+ | Phase 1 exploration | opus | Creative clarification |
25
+ | Phase 2 parallel agents (Analogues, Tech, Regulations) | sonnet | Research analysis |
26
+ | Phase 2.5 CJM variant generation | opus | Creative design work |
27
+ | Phase 2.5 trend research agents | sonnet | Research synthesis |
28
+ | Phase 3 solution design | opus | Complex problem solving |
29
+ | Phase 4 architecture | opus | System design |
30
+ | Phase 5 presentation storytelling | opus | Creative storytelling |
31
+ | Phase 5 speaker script agents | sonnet | Structured generation |
32
+ | Phase 5 Q&A preparation | sonnet | Analytical work |
33
+ | File formatting, slug generation | haiku | Simple transforms |
34
+
35
+ ### BTO Pipeline
36
+
37
+ | Task | Model | Rationale |
38
+ |------|-------|-----------|
39
+ | Layer 0 structural checks | haiku | Pattern matching only |
40
+ | Layer 1 semantic baseline | haiku | Fast coherence scan |
41
+ | Layer 2 Domain Expert judge | sonnet | Domain knowledge + nuanced scoring |
42
+ | Layer 2 Critic judge | sonnet | Adversarial analysis |
43
+ | Layer 2 Completeness Auditor judge | sonnet | Structured coverage check |
44
+ | Meta-judge (disagreement resolution) | sonnet | Arbitration |
45
+ | Optimization variant fast-eval (Round 1, 2) | haiku | Volume scoring |
46
+ | Optimization Round 3 full panel | sonnet | Final quality assessment |
47
+ | Optimization crossover / creative synthesis | opus | Novel combination of candidates |
48
+
49
+ ## Enforcement Rules
50
+
51
+ 1. **NEVER** use opus for Layer 0 or Layer 1 evaluation — this is wasteful
52
+ 2. **NEVER** use haiku for Layer 2 judge panel — quality will be insufficient
53
+ 3. **NEVER** use haiku for creative work (CJM design, storytelling) — output will be shallow
54
+ 4. When spawning agents with the Agent tool, ALWAYS specify the `model` parameter
55
+ 5. If model is not specified, the agent inherits the parent model (opus by default)
56
+ 6. For cost optimization, prefer haiku for any task that is primarily pattern-matching or formatting
57
+
58
+ ## Cost Impact
59
+
60
+ Approximate cost ratios (per 1K output tokens):
61
+ - haiku: 1x (baseline)
62
+ - sonnet: 15x
63
+ - opus: 75x
64
+
65
+ Using haiku instead of opus for Layer 0-1 saves ~98% on those evaluation steps.
@@ -0,0 +1,36 @@
1
+ # Trust Tier System
2
+
3
+ ## Tier Definitions
4
+
5
+ | Tier | Label | Requirements | Promotion Path |
6
+ |------|-------|-------------|----------------|
7
+ | Tier 3 | Verified | Eval test suites with deterministic validation | — (highest) |
8
+ | Tier 2 | Validated | Passed /bto-test with Layer 2 score ≥ 7.0 | Run /bto-test, score ≥ 8.5 on Layer 2 |
9
+ | Tier 1 | Structured | SKILL.md + references/ or modules/ | Run /bto-test, score ≥ 7.0 on Layer 2 |
10
+ | Tier 0 | Advisory | Basic SKILL.md only | Add references/, examples/, structured output |
11
+
12
+ ## Current Skill Tiers
13
+
14
+ | Skill | Tier | Label | Evidence |
15
+ |-------|------|-------|----------|
16
+ | explore | 1 | Structured | SKILL.md + references/ |
17
+ | frontend-design | 0 | Advisory | SKILL.md only, no references |
18
+ | goap-research-ed25519 | 1 | Structured | SKILL.md + references/ + scripts/ |
19
+ | problem-solver-enhanced | 1 | Structured | Comprehensive SKILL.md with TRIZ framework |
20
+ | presentation-storyteller | 1 | Structured | SKILL.md + references/ |
21
+ | reverse-engineering-unicorn | 1 | Structured | SKILL.md + modules/ + references/ + examples/ |
22
+ | bto | 1 | Structured | SKILL.md + modules/ + references/ + examples/ |
23
+
24
+ ## Tier Enforcement
25
+
26
+ - Tier 0 skills: Flag with warning when loaded in production pipeline
27
+ - Tier 1 skills: Standard usage, recommend /bto-test for promotion
28
+ - Tier 2 skills: Full confidence, include BTO score in metadata
29
+ - Tier 3 skills: Highest confidence, deterministic validation available
30
+
31
+ ## Promotion Protocol
32
+
33
+ 1. Run `/bto-test .claude/skills/<name>/`
34
+ 2. If Layer 2 score ≥ 7.0 → promote to Tier 2, record score in SKILL.md
35
+ 3. If Layer 2 score ≥ 8.5 + deterministic eval tests exist → promote to Tier 3
36
+ 4. Record promotion date and score in SKILL.md frontmatter
@@ -0,0 +1,45 @@
1
+ # Phase 0: Discovery — Governance Shard
2
+
3
+ ## Time Budget
4
+ 15% of total timeline
5
+
6
+ ## Skill
7
+ Load: `.claude/skills/reverse-engineering-unicorn/SKILL.md` (modules M2-M5)
8
+
9
+ ## Mandatory Outputs
10
+ - `00_product_discovery.md`
11
+
12
+ ## Content Requirements
13
+ - As-Is process mapping
14
+ - JTBD segments (minimum 3)
15
+ - Voice of Customer synthesis
16
+ - Aha Moment identification
17
+ - Why AI / Why Now justification
18
+ - Competitive landscape (minimum 3 competitors)
19
+ - Business Case with ROI projections
20
+ - Adoption Strategy
21
+
22
+ ## Agent Swarm
23
+ - Agent 1 (sonnet): JTBD + Voice of Customer + Aha Moment
24
+ - Agent 2 (sonnet): Competitor Analysis + Business Case + Why AI Why Now
25
+ - Synthesize results into single document
26
+
27
+ ## Domain Detection
28
+ Detect domain from case description and apply domain-specific rules:
29
+ - Banking: on-premise LLM, ФЗ-152, ЦБ, ФСТЭК
30
+ - Retail: latency < 200ms, A/B testing
31
+ - Enterprise: Change Management, Legacy integration
32
+ - Healthcare: HITL mandatory, ФЗ-323
33
+
34
+ ## Quality Gates
35
+ - Zero unverified competitor names
36
+ - ROI must include concrete numbers (FTE/hours/currency)
37
+ - JTBD format: "When [situation], I want to [motivation], so I can [outcome]"
38
+
39
+ ## Promise
40
+ On completion: `<promise>DISCOVERY_COMPLETE</promise>`
41
+
42
+ ## Anti-Patterns to Check
43
+ - "Just add GPT" without specific model/pipeline → BLOCK
44
+ - No metrics/KPIs → BLOCK
45
+ - Vague claims without numbers → FLAG
@@ -0,0 +1,32 @@
1
+ # Phase 1: Explore — Governance Shard
2
+
3
+ ## Time Budget
4
+ 5% of total timeline
5
+
6
+ ## Skill
7
+ Load: `.claude/skills/explore/SKILL.md`
8
+
9
+ ## Prerequisites
10
+ - Phase 0 complete: `<promise>DISCOVERY_COMPLETE</promise>`
11
+ - File exists: `00_product_discovery.md`
12
+
13
+ ## Mandatory Outputs
14
+ - `01_case_brief.md`
15
+
16
+ ## Content Requirements
17
+ - 5 Whys root cause analysis
18
+ - Data landscape analysis
19
+ - Constraints Map: hard / soft / hidden
20
+ - Success Criteria (measurable)
21
+ - Key Question (single, focused)
22
+
23
+ ## Model Routing
24
+ - Default model (opus) for creative clarification
25
+
26
+ ## Quality Gates
27
+ - Constraints must be categorized (hard/soft/hidden)
28
+ - Success criteria must be quantifiable
29
+ - Key Question must be single and actionable
30
+
31
+ ## Promise
32
+ On completion: `<promise>CASE_EXPLORED</promise>`
@@ -0,0 +1,42 @@
1
+ # Phase 2: Research — Governance Shard
2
+
3
+ ## Time Budget
4
+ 15% of total timeline
5
+
6
+ ## Skill
7
+ Load: `.claude/skills/goap-research-ed25519/SKILL.md`
8
+
9
+ ## Prerequisites
10
+ - Phase 1 complete: `<promise>CASE_EXPLORED</promise>`
11
+ - Files exist: `00_product_discovery.md`, `01_case_brief.md`
12
+
13
+ ## Mandatory Outputs
14
+ - `02_research_findings.md`
15
+
16
+ ## PARANOID Mode — ACTIVE
17
+ - Every factual claim MUST have a verifiable source
18
+ - Zero tolerance for hallucinated citations
19
+ - Confidence threshold: 0.99 minimum
20
+ - Unverifiable claims: mark as [UNVERIFIED] and flag
21
+ - Citation format: `[Claim] — Source: [URL or publication], [Date]`
22
+
23
+ ## Agent Swarm (3 parallel, model: sonnet)
24
+ - Agent 1: Analogues + Benchmarks
25
+ - Agent 2: Technologies + Anti-patterns
26
+ - Agent 3: Regulations + Market Data
27
+ - Synthesize results into single document
28
+
29
+ ## Quality Gates
30
+ - ALL claims have sources
31
+ - No unverified statistics or percentages
32
+ - Competitor names verified to exist
33
+ - Technology recommendations are for real, available products
34
+ - Regulatory references cite actual laws/standards
35
+
36
+ ## Promise
37
+ On completion: `<promise>RESEARCH_PARANOID_PASSED</promise>`
38
+
39
+ ## Anti-Patterns to Check
40
+ - Bare claims without attribution → BLOCK
41
+ - Generic "studies show" without specific study → BLOCK
42
+ - Hallucinated product names → BLOCK
@@ -0,0 +1,47 @@
1
+ # Phase 2.5: CJM Prototype — Governance Shard
2
+
3
+ ## MANDATORY — THIS PHASE CANNOT BE SKIPPED
4
+
5
+ ## Time Budget
6
+ 10% of total timeline
7
+
8
+ ## Skills
9
+ - Primary: `.claude/skills/reverse-engineering-unicorn/SKILL.md` (module M2.5)
10
+ - UI Design: `.claude/skills/frontend-design/SKILL.md`
11
+ - Trend Research: `.claude/skills/goap-research-ed25519/SKILL.md` (for Variant D)
12
+
13
+ ## Prerequisites
14
+ - Phase 2 complete: `<promise>RESEARCH_PARANOID_PASSED</promise>`
15
+ - Files exist: `00_product_discovery.md`, `01_case_brief.md`, `02_research_findings.md`
16
+
17
+ ## Mandatory Outputs
18
+ - `02.5_trend_brief.md` (Variant D trend research)
19
+ - `prototype/cjm-prototype.jsx` (4-variant interactive prototype)
20
+
21
+ ## Process
22
+ 1. Extract: primary_user, segments, aha_moment, solution_concept from Phases 0-2
23
+ 2. Define 3 CJM variants (A/B/C) with different approaches
24
+ 3. Research 5 trend categories for Variant D (PARANOID mode)
25
+ 4. Generate React .jsx prototype with all 4 variants
26
+ 5. User selects winning variant → sets `{CHOSEN_CJM}`
27
+
28
+ ## Agent Swarm (3 parallel)
29
+ - Agent 1 (opus): CJM Variant A design
30
+ - Agent 2 (opus): CJM Variants B + C design
31
+ - Agent 3 (sonnet): Trend Research for Variant D (PARANOID mode, 5 categories)
32
+
33
+ ## Critical Variable
34
+ `{CHOSEN_CJM}` — MUST be set by user selection. Passed to Phases 3-5.
35
+
36
+ ## Quality Gates
37
+ - Minimum 3 CJM variants (A/B/C) + 1 trend variant (D)
38
+ - Prototype must be valid React JSX
39
+ - Trend research in PARANOID mode (verified sources)
40
+ - User MUST explicitly select a variant
41
+
42
+ ## Promise
43
+ On completion: `<promise>CJM_VALIDATED</promise>`
44
+
45
+ ## Invariant
46
+ If any attempt is made to skip this phase → BLOCK immediately.
47
+ "Skipping CJM" is listed as a FORBIDDEN anti-pattern.
@@ -0,0 +1,47 @@
1
+ # Phase 3: Solve — Governance Shard
2
+
3
+ ## Time Budget
4
+ 15% of total timeline
5
+
6
+ ## Skill
7
+ Load: `.claude/skills/problem-solver-enhanced/SKILL.md` (TRIZ + Game Theory)
8
+
9
+ ## Prerequisites
10
+ - Phase 2.5 complete: `<promise>CJM_VALIDATED</promise>`
11
+ - `{CHOSEN_CJM}` is set
12
+ - Files exist: `00_` through `02.5_`
13
+
14
+ ## Mandatory Outputs
15
+ - `03_solution_strategy.md`
16
+ - `diagrams/process-as-is.mermaid`
17
+ - `diagrams/process-to-be.mermaid`
18
+
19
+ ## Content Requirements
20
+ - SCQA (Situation-Complication-Question-Answer) for pitch
21
+ - Concept + Elevator Pitch + Key Innovation
22
+ - Process Design: As-Is → To-Be (using `{CHOSEN_CJM}`)
23
+ - User Flow from `{CHOSEN_CJM}`
24
+ - AI Pipeline specification
25
+ - Human-in-the-Loop design with escalation policy
26
+ - Success Metrics with baseline values
27
+ - Risks & Mitigation matrix
28
+ - Roadmap: PoC → MVP → Scale
29
+
30
+ ## Agent Swarm (2 parallel)
31
+ - Agent 1 (opus): SCQA + Concept + Process Design + User Flow + AI Pipeline
32
+ - Agent 2 (sonnet): Mermaid Diagrams + HITL + Metrics + Roadmap
33
+
34
+ ## Quality Gates
35
+ - SCQA must be concise and compelling
36
+ - Metrics must include baseline AND target values
37
+ - HITL escalation policy is MANDATORY (no AI-only decisions)
38
+ - Mermaid diagrams must be valid syntax
39
+ - `{CHOSEN_CJM}` must appear in User Flow section
40
+
41
+ ## Promise
42
+ On completion: `<promise>SOLUTION_DESIGNED</promise>`
43
+
44
+ ## Anti-Patterns to Check
45
+ - No HITL → BLOCK
46
+ - Vague "improve efficiency" without numbers → BLOCK
47
+ - Over-engineering (> 10 components in MVP) → FLAG
@@ -0,0 +1,41 @@
1
+ # Phase 4: Architecture — Governance Shard
2
+
3
+ ## Time Budget
4
+ 15% of total timeline
5
+
6
+ ## Skill
7
+ Built-in templates (no external skill)
8
+
9
+ ## Prerequisites
10
+ - Phase 3 complete: `<promise>SOLUTION_DESIGNED</promise>`
11
+ - Files exist: `00_` through `03_`
12
+
13
+ ## Mandatory Outputs
14
+ - `04_architecture.md`
15
+ - `diagrams/architecture-c4.mermaid` (C4 Context diagram)
16
+ - `diagrams/sequence-main-flow.mermaid` (Sequence diagram)
17
+
18
+ ## Content Requirements
19
+ - C4 architectural diagram
20
+ - Components table: tech + purpose + justification
21
+ - AI Models & Pipeline: task, type, concrete model name
22
+ - Data Architecture: sources, ETL, storage, Vector DB
23
+ - Integrations: system + protocol
24
+ - Security & Compliance: controls, RBAC, audit, regulations
25
+ - Scalability: latency target, throughput, scaling strategy
26
+ - MVP Scope definition
27
+
28
+ ## Domain-Specific Rules
29
+ - Banking: on-premise LLM (GigaChat/YandexGPT/open-source), ФЗ-152, ЦБ, ФСТЭК
30
+ - Retail: latency < 200ms, A/B testing infrastructure
31
+ - Enterprise: Change Management plan, Legacy integration, SLA definition
32
+ - Healthcare: HITL for ALL clinical decisions, ФЗ-323
33
+
34
+ ## Quality Gates
35
+ - Minimum 2 Mermaid diagrams (C4 + sequence)
36
+ - All model names must be real, available products
37
+ - Security section must reference applicable regulations
38
+ - MVP scope must be achievable (not over-engineered)
39
+
40
+ ## Promise
41
+ On completion: `<promise>ARCHITECTURE_DEFINED</promise>`
@@ -0,0 +1,56 @@
1
+ # Phase 5: Presentation — Governance Shard
2
+
3
+ ## Time Budget
4
+ 20% of total timeline (largest allocation)
5
+
6
+ ## Skill
7
+ Load: `.claude/skills/presentation-storyteller/SKILL.md`
8
+
9
+ ## Prerequisites
10
+ - Phase 4 complete: `<promise>ARCHITECTURE_DEFINED</promise>`
11
+ - `{CHOSEN_CJM}` is set (for Slide 5)
12
+ - Files exist: `00_` through `04_`
13
+
14
+ ## Mandatory Outputs (ALL 4 files required)
15
+ - `05_presentation_content.md` (10-12 slides with storytelling)
16
+ - `06_speaker_script.md` (per-slide: HOOK, CONTENT, BRIDGE, TONE, KEY MESSAGE)
17
+ - `07_qa_preparation.md` (7+ typical jury questions + answers)
18
+ - `08_executive_summary.md` (1 page for jury) ⭐ MANDATORY
19
+
20
+ ## 08_executive_summary.md is NON-NEGOTIABLE
21
+ Missing Executive Summary is a FORBIDDEN anti-pattern. BLOCK if not created.
22
+
23
+ ## Slide Structure (10-12 slides)
24
+ 1. Title + Team + Case
25
+ 2. Problem (SCQA, cost of inaction)
26
+ 3. Key Question + Elevator Pitch
27
+ 4. Concept (high-level, AI role)
28
+ 5. User Flow / To-Be (`{CHOSEN_CJM}`)
29
+ 6. AI Under the Hood (models, RAG/Agent, HITL)
30
+ 7. Data Architecture
31
+ 8. Security & Compliance
32
+ 9. Metrics & ROI (As-Is → Target)
33
+ 10. Roadmap (PoC → MVP → Scale)
34
+ 11. Team + CTA
35
+ 12. Q&A
36
+
37
+ ## Agent Swarm (3 parallel)
38
+ - Agent 1 (opus): Presentation content (05) — storytelling
39
+ - Agent 2 (sonnet): Speaker script (06)
40
+ - Agent 3 (sonnet): Q&A + Executive Summary (07 + 08)
41
+
42
+ ## Quality Gates
43
+ - No slide reading (text-heavy slides) → FLAG
44
+ - Every slide must have a visual anchor suggestion
45
+ - Speaker script must tell a connected story across slides
46
+ - Q&A must include tough/adversarial questions
47
+ - Executive Summary must fit on 1 page
48
+
49
+ ## Promise
50
+ On completion: `<promise>PRESENTATION_READY</promise>`
51
+
52
+ ## Anti-Patterns to Check
53
+ - Text-heavy slides → FLAG
54
+ - No storytelling arc → FLAG
55
+ - Missing Executive Summary → BLOCK
56
+ - Generic phrases without numbers → FLAG
@@ -3,11 +3,14 @@ name: explore
3
3
  description: >
4
4
  Adaptive task exploration and clarification skill for transforming vague
5
5
  requests into actionable specifications. Use when a user presents any task,
6
- problem, or goal that requires clarification before execution. Triggers on
7
- ambiguous requests, complex multi-part tasks, "I want to...", "help me with...",
8
- strategic decisions, product ideas, creative briefs, and any situation where
9
- understanding the real need is essential before proposing solutions. Does NOT
6
+ problem, or goal that requires clarification before execution. Triggers on
7
+ ambiguous requests, complex multi-part tasks, "I want to...", "help me with...",
8
+ strategic decisions, product ideas, creative briefs, and any situation where
9
+ understanding the real need is essential before proposing solutions. Does NOT
10
10
  provide solutions until task is fully explored.
11
+ trust_tier: 1
12
+ trust_tier_label: "Structured"
13
+ trust_tier_path: "Run /bto-test to promote to Tier 2"
11
14
  ---
12
15
 
13
16
  # Explore: Adaptive Task Clarification
@@ -2,6 +2,9 @@
2
2
  name: frontend-design
3
3
  description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
4
4
  license: Complete terms in LICENSE.txt
5
+ trust_tier: 0
6
+ trust_tier_label: "Advisory"
7
+ trust_tier_path: "Add references/ directory and run /bto-test to promote to Tier 1"
5
8
  ---
6
9
 
7
10
  This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
@@ -1,6 +1,9 @@
1
1
  ---
2
2
  name: goap-research-ed25519
3
3
  description: Advanced GOAP research system with Ed25519 cryptographic verification for anti-hallucination protection. Combines Goal-Oriented Action Planning with cryptographic signatures to ensure source authenticity, claim verification, and citation chain integrity. Use for high-stakes research requiring verifiable facts, competitive intelligence, legal/medical research, or any context where hallucination prevention is critical. Triggers on "verified research", "trusted sources only", "anti-hallucination", "signed sources", "cryptographic verification".
4
+ trust_tier: 1
5
+ trust_tier_label: "Structured"
6
+ trust_tier_path: "Run /bto-test to promote to Tier 2"
4
7
  ---
5
8
 
6
9
  # GOAP Research Skill with Ed25519 Verification
@@ -6,9 +6,12 @@ description: >
6
6
  в Markdown со ссылками на источники, (3) Подстрочник "Как рассказывать?" со связной
7
7
  историей для каждого слайда. Использует explore (уточнение задачи), goap-research-ed25519
8
8
  (исследование с верификацией), storytelling-фреймворки (AIDA, Hero's Journey, Problem-Solution).
9
- Выходные файлы: presentation-outline.md (план), presentation-full.md (презентация),
10
- sources-index.md (индекс источников). Триггеры: "сделай презентацию", "presentation with
9
+ Выходные файлы: presentation-outline.md (план), presentation-full.md (презентация),
10
+ sources-index.md (индекс источников). Триггеры: "сделай презентацию", "presentation with
11
11
  storytelling", "презентация со скриптами", "sales deck", "pitch deck", "продающая презентация".
12
+ trust_tier: 1
13
+ trust_tier_label: "Structured"
14
+ trust_tier_path: "Run /bto-test to promote to Tier 2"
12
15
  ---
13
16
 
14
17
  # Presentation Storyteller: Sales Decks with Verified Sources
@@ -1,6 +1,9 @@
1
1
  ---
2
2
  name: problem-solver-enhanced
3
3
  description: Elite problem-solving system combining first principles thinking, game theory, root cause analysis, systematic frameworks AND TRIZ inventive principles for solving complex challenges. Use when facing complex challenges with unclear solutions, strategic decisions with multiple stakeholders, problems requiring breakthrough (not incremental) solutions, trade-offs that seem impossible to resolve, competitive scenarios requiring game-theoretic analysis, system design problems, or any situation requiring both analytical rigor and inventive thinking beyond surface-level solutions.
4
+ trust_tier: 1
5
+ trust_tier_label: "Structured"
6
+ trust_tier_path: "Run /bto-test to promote to Tier 2"
4
7
  ---
5
8
 
6
9
  # Elite Problem Solver (Enhanced with TRIZ)
@@ -1,6 +1,9 @@
1
1
  ---
2
2
  name: reverse-engineering-unicorn
3
3
  description: Reverse engineer any company into a launch playbook with clickable CJM prototype. Triggers on "проанализируй компанию", "reverse engineer", "разбери бизнес-модель", "playbook запуска".
4
+ trust_tier: 1
5
+ trust_tier_label: "Structured"
6
+ trust_tier_path: "Run /bto-test to promote to Tier 2"
4
7
  ---
5
8
 
6
9
  # Reverse Engineering Unicorn v2