arkaos 2.59.0 → 2.61.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.
package/VERSION CHANGED
@@ -1 +1 @@
1
- 2.59.0
1
+ 2.61.0
@@ -0,0 +1,147 @@
1
+ id: community-model
2
+ name: Community Business Model
3
+ description: Community business model design — purpose + ideal member + value prop + SPACES role + platform fit + monetisation + growth loop
4
+ department: community
5
+ tier: enterprise
6
+ command: "/community model"
7
+ requires_branch: false
8
+ requires_spec: false
9
+ quality_gate_required: true
10
+
11
+ phases:
12
+ - id: brief
13
+ name: Community Brief
14
+ description: Define niche, founder context, current audience size, success metric, runway
15
+ agents:
16
+ - agent_id: community-strategist-beatriz
17
+ role: Frame niche, founder context, current audience, runway, success metric
18
+ gate:
19
+ type: user_approval
20
+ description: User confirms niche and context
21
+
22
+ - id: purpose-definition
23
+ name: Purpose & Identity
24
+ description: Define the community's purpose using the Onlyness frame — only community where X for Y who want Z
25
+ agents:
26
+ - agent_id: community-strategist-beatriz
27
+ role: Onlyness frame + community identity statement
28
+ - agent_id: brand-strategist-mateus
29
+ role: Differentiation from adjacent communities
30
+ parallel: true
31
+ gate:
32
+ type: user_approval
33
+ description: User approves purpose and identity
34
+
35
+ - id: ideal-member-profile
36
+ name: Ideal Member Profile
37
+ description: Define the IMP (Ideal Member Profile) with firmographics + practitioner level + transformation context
38
+ agents:
39
+ - agent_id: community-strategist-beatriz
40
+ role: IMP definition with belonging triggers + dropout triggers
41
+ gate:
42
+ type: user_approval
43
+ description: User approves IMP
44
+ outputs:
45
+ - type: document
46
+ format: markdown
47
+ obsidian_path: "WizardingCode/Communities/IMP/"
48
+ description: Ideal Member Profile with belonging + dropout triggers
49
+
50
+ - id: spaces-classification
51
+ name: SPACES Classification
52
+ description: Classify the community across the SPACES framework — Support / Product / Action / Content / Engagement / Success
53
+ agents:
54
+ - agent_id: community-strategist-beatriz
55
+ role: SPACES classification with primary + secondary purpose
56
+ gate:
57
+ type: user_approval
58
+ description: User approves SPACES role
59
+
60
+ - id: value-prop
61
+ name: Value Proposition (Member-Side + Operator-Side)
62
+ description: Two value props — what the member gets, what the operator gets, why both compound
63
+ agents:
64
+ - agent_id: community-strategist-beatriz
65
+ role: Two-sided value prop with compounding logic
66
+ - agent_id: copy-director-eduardo
67
+ role: Value prop copy for both audiences
68
+ parallel: true
69
+ gate:
70
+ type: user_approval
71
+ description: User approves value props
72
+
73
+ - id: platform-fit
74
+ name: Platform Fit
75
+ description: Pick platform based on IMP × SPACES × moderation needs — Discord / Slack / Circle / Mighty / native / open-source
76
+ agents:
77
+ - agent_id: community-strategist-beatriz
78
+ role: Platform selection matrix with fit per dimension
79
+ gate:
80
+ type: user_approval
81
+ description: User approves platform choice
82
+
83
+ - id: monetisation
84
+ name: Monetisation Model
85
+ description: Free / freemium / paid / cohort / sponsorship — with unit economics check
86
+ agents:
87
+ - agent_id: community-strategist-beatriz
88
+ role: Monetisation model with conversion + LTV math
89
+ - agent_id: cfo-helena
90
+ role: Unit economics validation
91
+ parallel: true
92
+ gate:
93
+ type: user_approval
94
+ description: User approves monetisation model
95
+
96
+ - id: growth-loop
97
+ name: Community Growth Loop
98
+ description: Define the loop — member contributes → status / reach → outsiders notice → join → contribute. Plus K-factor / NRG target.
99
+ agents:
100
+ - agent_id: community-strategist-beatriz
101
+ role: Growth loop spec with mechanism + metric per step
102
+ - agent_id: marketing-director-luna
103
+ role: Loop compounding factor + coordination with other depts (content, paid)
104
+ parallel: true
105
+ gate:
106
+ type: user_approval
107
+ description: User approves growth loop
108
+
109
+ - id: self-critique
110
+ name: Self-Critique
111
+ description: Stress-test — does IMP × SPACES × platform align? Does monetisation match member value? Is the loop compounding-positive?
112
+ agents:
113
+ - agent_id: community-strategist-beatriz
114
+ role: Coherence check across all blocks
115
+ gate:
116
+ type: auto
117
+
118
+ - id: quality-gate
119
+ name: Quality Gate
120
+ model_override: opus
121
+ description: Mandatory quality review
122
+ agents:
123
+ - agent_id: cqo-marta
124
+ role: Orchestrate quality review
125
+ - agent_id: copy-director-eduardo
126
+ role: Value prop prose, member-side / operator-side language, no clichés
127
+ parallel: true
128
+ - agent_id: tech-director-francisca
129
+ role: Platform technical feasibility, monetisation tech stack, instrumentation
130
+ parallel: true
131
+ gate:
132
+ type: quality_gate
133
+ required_verdict: APPROVED
134
+
135
+ - id: delivery
136
+ name: Community Model Package Delivery
137
+ description: Compile the community model package — purpose + IMP + SPACES + value props + platform + monetisation + growth loop
138
+ agents:
139
+ - agent_id: community-strategist-beatriz
140
+ role: Full community model package + 1-page executive summary
141
+ gate:
142
+ type: auto
143
+ outputs:
144
+ - type: document
145
+ format: markdown
146
+ obsidian_path: "WizardingCode/Communities/Models/"
147
+ description: Complete community model — purpose + IMP + SPACES + two-sided value prop + platform + monetisation + growth loop + exec summary
@@ -0,0 +1,140 @@
1
+ id: saas-growth
2
+ name: SaaS Growth Plan
3
+ description: Stage-specific growth plan (seed / Series A / scale) with stage-appropriate metrics, channels, team allocation
4
+ department: saas
5
+ tier: enterprise
6
+ command: "/saas growth"
7
+ requires_branch: false
8
+ requires_spec: false
9
+ quality_gate_required: true
10
+
11
+ phases:
12
+ - id: brief
13
+ name: Growth Brief
14
+ description: Define current stage, ARR, growth rate, runway, target stage end-state
15
+ agents:
16
+ - agent_id: saas-strategist-tiago
17
+ role: Frame current stage, ARR, growth rate, runway, end-state
18
+ gate:
19
+ type: user_approval
20
+ description: User confirms stage context and target
21
+
22
+ - id: stage-diagnosis
23
+ name: Stage Diagnosis
24
+ description: Diagnose where the SaaS actually is (vs claims) — seed (PMF search), Series A (PMF + scale prep), scale (efficient growth)
25
+ agents:
26
+ - agent_id: saas-strategist-tiago
27
+ role: Stage diagnosis with evidence (PMF signals, expansion math, sales motion maturity)
28
+ - agent_id: strategy-director-tomas
29
+ role: Strategic context — category position, competitive intensity
30
+ parallel: true
31
+ gate:
32
+ type: user_approval
33
+ description: User approves stage diagnosis
34
+ outputs:
35
+ - type: document
36
+ format: markdown
37
+ obsidian_path: "WizardingCode/SaaS/Growth/Diagnosis/"
38
+ description: Stage diagnosis with PMF evidence and stage-shift criteria
39
+
40
+ - id: stage-metrics
41
+ name: Stage-Appropriate Metrics
42
+ description: Define the 3-5 metrics that matter at THIS stage (different per stage)
43
+ agents:
44
+ - agent_id: saas-strategist-tiago
45
+ role: Stage-specific metric set with target per metric
46
+ - agent_id: cfo-helena
47
+ role: Financial metric integration (Magic Number, Net Burn Multiple, CAC payback)
48
+ parallel: true
49
+ gate:
50
+ type: user_approval
51
+ description: User approves metric set
52
+
53
+ - id: motion-channel-fit
54
+ name: Motion × Channel Fit (Stage-Adjusted)
55
+ description: Pick GTM motion + channels appropriate to stage (seed = focused, A = scaled-up, scale = portfolio)
56
+ agents:
57
+ - agent_id: saas-strategist-tiago
58
+ role: Motion + channel selection with stage rationale
59
+ - agent_id: marketing-director-luna
60
+ role: Channel-feasibility validation
61
+ parallel: true
62
+ gate:
63
+ type: user_approval
64
+ description: User approves motion + channels
65
+
66
+ - id: team-allocation
67
+ name: Team Allocation
68
+ description: How team headcount maps to the growth plan — first hires per stage, when to hire what
69
+ agents:
70
+ - agent_id: saas-strategist-tiago
71
+ role: Team allocation with hire-when-X triggers
72
+ - agent_id: coo-sofia
73
+ role: Org design — when to add second-line management
74
+ parallel: true
75
+ gate:
76
+ type: user_approval
77
+ description: User approves team allocation
78
+
79
+ - id: budget-runway
80
+ name: Budget × Runway
81
+ description: 12-month budget split across hire / paid / tools / experiments with runway impact
82
+ agents:
83
+ - agent_id: saas-strategist-tiago
84
+ role: Budget allocation with monthly burn
85
+ - agent_id: cfo-helena
86
+ role: Runway impact + worst-case scenario
87
+ parallel: true
88
+ gate:
89
+ type: user_approval
90
+ description: User approves budget × runway plan
91
+
92
+ - id: experiment-portfolio
93
+ name: 90-Day Experiment Portfolio
94
+ description: 3-5 prioritised experiments — hypothesis, success criteria, kill-switch date
95
+ agents:
96
+ - agent_id: saas-strategist-tiago
97
+ role: Experiment portfolio with hypothesis + MDE + kill date per experiment
98
+ gate:
99
+ type: user_approval
100
+ description: User approves experiment portfolio
101
+
102
+ - id: self-critique
103
+ name: Self-Critique
104
+ description: Stress-test the plan — does stage diagnosis support motion choice? Does budget × runway × team math close?
105
+ agents:
106
+ - agent_id: saas-strategist-tiago
107
+ role: Coherence check across stage / motion / team / budget / experiments
108
+ gate:
109
+ type: auto
110
+
111
+ - id: quality-gate
112
+ name: Quality Gate
113
+ model_override: opus
114
+ description: Mandatory quality review
115
+ agents:
116
+ - agent_id: cqo-marta
117
+ role: Orchestrate quality review
118
+ - agent_id: copy-director-eduardo
119
+ role: Plan prose, stage diagnosis defensibility, no clichés
120
+ parallel: true
121
+ - agent_id: tech-director-francisca
122
+ role: Metric math, budget math, instrumentation feasibility
123
+ parallel: true
124
+ gate:
125
+ type: quality_gate
126
+ required_verdict: APPROVED
127
+
128
+ - id: delivery
129
+ name: Growth Plan Delivery
130
+ description: Compile the growth plan + executive summary + monthly checkpoint cadence
131
+ agents:
132
+ - agent_id: saas-strategist-tiago
133
+ role: Full growth plan + executive summary + monthly checkpoint schedule
134
+ gate:
135
+ type: auto
136
+ outputs:
137
+ - type: document
138
+ format: markdown
139
+ obsidian_path: "WizardingCode/SaaS/Growth/"
140
+ description: Complete growth plan — stage diagnosis + metrics + motion + team + budget + experiments + monthly checkpoints
@@ -0,0 +1,145 @@
1
+ id: saas-launch
2
+ name: SaaS Launch Checklist & Execution
3
+ description: SaaS launch checklist + execution plan — pre-launch / launch / post-launch with stage-appropriate distribution
4
+ department: saas
5
+ tier: enterprise
6
+ command: "/saas launch"
7
+ requires_branch: false
8
+ requires_spec: false
9
+ quality_gate_required: true
10
+
11
+ phases:
12
+ - id: brief
13
+ name: Launch Brief
14
+ description: Define product, current beta state, target audience, success metric, launch type (public / private / soft / hard)
15
+ agents:
16
+ - agent_id: saas-strategist-tiago
17
+ role: Frame product, beta state, audience, success metric, launch type
18
+ gate:
19
+ type: user_approval
20
+ description: User confirms launch brief
21
+
22
+ - id: readiness-audit
23
+ name: Launch Readiness Audit
24
+ description: Product readiness checklist — feature-complete, performance, billing, support, tracking, legal
25
+ agents:
26
+ - agent_id: saas-strategist-tiago
27
+ role: Readiness audit with pass/waiver per criterion
28
+ - agent_id: tech-director-francisca
29
+ role: Technical readiness (performance, billing, infra, security)
30
+ parallel: true
31
+ gate:
32
+ type: user_approval
33
+ description: User approves launch readiness (zero blockers or explicit waivers)
34
+ outputs:
35
+ - type: document
36
+ format: markdown
37
+ obsidian_path: "WizardingCode/SaaS/Launches/Readiness/"
38
+ description: Readiness audit with checklist per dimension
39
+
40
+ - id: positioning-message
41
+ name: Positioning & Core Message
42
+ description: Confirm positioning (re-using GTM positioning if exists) + 3-tier message hierarchy
43
+ agents:
44
+ - agent_id: saas-strategist-tiago
45
+ role: Core message hierarchy (tagline / headline / value props)
46
+ - agent_id: brand-strategist-mateus
47
+ role: Onlyness validation + brand consistency check
48
+ parallel: true
49
+ gate:
50
+ type: user_approval
51
+ description: User approves message hierarchy
52
+
53
+ - id: launch-assets
54
+ name: Launch Assets Inventory
55
+ description: Asset inventory — landing page + email + social + product hunt + press kit + demo video + docs
56
+ agents:
57
+ - agent_id: saas-strategist-tiago
58
+ role: Asset inventory with delivery dates
59
+ - agent_id: conversion-strategist-ines
60
+ role: Landing page conversion spec
61
+ parallel: true
62
+ - agent_id: copy-director-eduardo
63
+ role: Copy briefs for all launch assets
64
+ parallel: true
65
+ gate:
66
+ type: user_approval
67
+ description: User approves asset list and delivery dates
68
+
69
+ - id: channel-sequence
70
+ name: Channel Sequence
71
+ description: Day-by-day channel activation — community → list → social → press → paid
72
+ agents:
73
+ - agent_id: saas-strategist-tiago
74
+ role: Channel sequence with day-by-day priorities
75
+ - agent_id: marketing-director-luna
76
+ role: Channel-specific tactics + paid ramp plan
77
+ parallel: true
78
+ gate:
79
+ type: user_approval
80
+ description: User approves channel sequence
81
+
82
+ - id: launch-day-runbook
83
+ name: Launch Day Runbook
84
+ description: Hour-by-hour launch day — owners, action items, escalation paths, decision gates
85
+ agents:
86
+ - agent_id: saas-strategist-tiago
87
+ role: Hour-by-hour runbook with named owners + decision gates
88
+ gate:
89
+ type: user_approval
90
+ description: User approves launch day runbook
91
+ outputs:
92
+ - type: document
93
+ format: markdown
94
+ obsidian_path: "WizardingCode/SaaS/Launches/Runbooks/"
95
+ description: Hour-by-hour launch day runbook
96
+
97
+ - id: post-launch-plan
98
+ name: Post-Launch Plan
99
+ description: Week-1 / Month-1 follow-up sequence — retention focus, support scaling, iteration based on real usage
100
+ agents:
101
+ - agent_id: saas-strategist-tiago
102
+ role: Week-1 + Month-1 post-launch plan with retention focus
103
+ gate:
104
+ type: user_approval
105
+ description: User approves post-launch plan
106
+
107
+ - id: self-critique
108
+ name: Self-Critique
109
+ description: Stress-test the launch — are readiness waivers acceptable? Does channel sequence match audience reality? Are decision gates actionable?
110
+ agents:
111
+ - agent_id: saas-strategist-tiago
112
+ role: Launch coherence + readiness defensibility check
113
+ gate:
114
+ type: auto
115
+
116
+ - id: quality-gate
117
+ name: Quality Gate
118
+ model_override: opus
119
+ description: Mandatory quality review
120
+ agents:
121
+ - agent_id: cqo-marta
122
+ role: Orchestrate quality review
123
+ - agent_id: copy-director-eduardo
124
+ role: All launch copy + message hierarchy + no over-promise
125
+ parallel: true
126
+ - agent_id: tech-director-francisca
127
+ role: Readiness audit accuracy + tracking + scalability
128
+ parallel: true
129
+ gate:
130
+ type: quality_gate
131
+ required_verdict: APPROVED
132
+
133
+ - id: delivery
134
+ name: Launch Package Delivery
135
+ description: Compile launch package — readiness + assets + channel sequence + runbook + post-launch plan
136
+ agents:
137
+ - agent_id: saas-strategist-tiago
138
+ role: Full launch package + 1-page executive summary
139
+ gate:
140
+ type: auto
141
+ outputs:
142
+ - type: document
143
+ format: markdown
144
+ obsidian_path: "WizardingCode/SaaS/Launches/"
145
+ description: Complete launch package — readiness + positioning + assets + channel sequence + launch day runbook + post-launch plan + exec summary
@@ -0,0 +1,139 @@
1
+ id: saas-plg
2
+ name: Product-Led Growth Setup
3
+ description: Product-Led Growth setup — freemium or trial model selection, activation event design, monetisation trigger, expansion mechanics
4
+ department: saas
5
+ tier: enterprise
6
+ command: "/saas plg"
7
+ requires_branch: false
8
+ requires_spec: false
9
+ quality_gate_required: true
10
+
11
+ phases:
12
+ - id: brief
13
+ name: PLG Brief
14
+ description: Define product, current ICP, current activation pattern, current monetisation
15
+ agents:
16
+ - agent_id: saas-strategist-tiago
17
+ role: Frame product fit-for-PLG, current activation, current monetisation, runway
18
+ gate:
19
+ type: user_approval
20
+ description: User confirms PLG context and fit assessment
21
+
22
+ - id: model-selection
23
+ name: Model Selection (Freemium vs Trial)
24
+ description: Pick freemium vs free-trial vs reverse-trial based on product DNA + ICP + CAC math
25
+ agents:
26
+ - agent_id: saas-strategist-tiago
27
+ role: Model selection with explicit trade-off table
28
+ - agent_id: cfo-helena
29
+ role: Unit economics check per model (LTV/CAC, payback)
30
+ parallel: true
31
+ gate:
32
+ type: user_approval
33
+ description: User approves PLG model
34
+ outputs:
35
+ - type: document
36
+ format: markdown
37
+ obsidian_path: "WizardingCode/SaaS/PLG/Model/"
38
+ description: Model selection rationale + economics
39
+
40
+ - id: activation-event
41
+ name: Activation Event Design
42
+ description: Define the activation event — the moment user gets first measurable value (Aha moment)
43
+ agents:
44
+ - agent_id: saas-strategist-tiago
45
+ role: Activation event definition with measurable success criteria
46
+ - agent_id: product-director-carolina
47
+ role: User journey to activation, time-to-first-value target
48
+ parallel: true
49
+ gate:
50
+ type: user_approval
51
+ description: User approves activation event definition
52
+
53
+ - id: onboarding-design
54
+ name: Onboarding Design
55
+ description: Onboarding flow optimised for activation — checklist, empty states, value signposts
56
+ agents:
57
+ - agent_id: saas-strategist-tiago
58
+ role: Onboarding flow with friction-vs-completion trade-off explicit
59
+ - agent_id: ux-designer-sofia-d
60
+ role: UX patterns with completion target per step
61
+ parallel: true
62
+ gate:
63
+ type: user_approval
64
+ description: User approves onboarding flow
65
+
66
+ - id: monetisation-trigger
67
+ name: Monetisation Trigger
68
+ description: When and how the user hits the paywall — usage limits, feature gates, team upgrades
69
+ agents:
70
+ - agent_id: saas-strategist-tiago
71
+ role: Monetisation trigger design — value-based, not arbitrary
72
+ - agent_id: cfo-helena
73
+ role: Trigger-to-conversion math
74
+ parallel: true
75
+ gate:
76
+ type: user_approval
77
+ description: User approves monetisation trigger
78
+
79
+ - id: expansion-mechanics
80
+ name: Expansion Mechanics
81
+ description: How accounts expand within the product — multi-seat, usage growth, feature upsell, NRR > 110% target
82
+ agents:
83
+ - agent_id: saas-strategist-tiago
84
+ role: Expansion levers with NRR > 110% math
85
+ gate:
86
+ type: user_approval
87
+ description: User approves expansion mechanics
88
+
89
+ - id: instrumentation
90
+ name: Instrumentation
91
+ description: Tracking events for activation, monetisation triggers, expansion — full funnel telemetry
92
+ agents:
93
+ - agent_id: saas-strategist-tiago
94
+ role: Event schema with per-funnel-step tracking
95
+ - agent_id: tech-director-francisca
96
+ role: Implementation feasibility
97
+ parallel: true
98
+ gate:
99
+ type: auto
100
+
101
+ - id: self-critique
102
+ name: Self-Critique
103
+ description: Stress-test — does activation event predict retention? Does monetisation trigger feel earned? Does expansion math close?
104
+ agents:
105
+ - agent_id: saas-strategist-tiago
106
+ role: PLG coherence check
107
+ gate:
108
+ type: auto
109
+
110
+ - id: quality-gate
111
+ name: Quality Gate
112
+ model_override: opus
113
+ description: Mandatory quality review
114
+ agents:
115
+ - agent_id: cqo-marta
116
+ role: Orchestrate quality review
117
+ - agent_id: copy-director-eduardo
118
+ role: Onboarding copy, paywall framing, no aggressive monetisation prose
119
+ parallel: true
120
+ - agent_id: tech-director-francisca
121
+ role: Instrumentation correctness, event schema integrity
122
+ parallel: true
123
+ gate:
124
+ type: quality_gate
125
+ required_verdict: APPROVED
126
+
127
+ - id: delivery
128
+ name: PLG Package Delivery
129
+ description: Compile the PLG package — model + activation + onboarding + monetisation + expansion + instrumentation
130
+ agents:
131
+ - agent_id: saas-strategist-tiago
132
+ role: Full PLG package + 1-page executive summary
133
+ gate:
134
+ type: auto
135
+ outputs:
136
+ - type: document
137
+ format: markdown
138
+ obsidian_path: "WizardingCode/SaaS/PLG/"
139
+ description: Complete PLG package — model + activation + onboarding + monetisation + expansion + instrumentation + exec summary
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "arkaos",
3
- "version": "2.59.0",
3
+ "version": "2.61.0",
4
4
  "description": "The Operating System for AI Agent Teams",
5
5
  "type": "module",
6
6
  "bin": {
package/pyproject.toml CHANGED
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "arkaos-core"
3
- version = "2.59.0"
3
+ version = "2.61.0"
4
4
  description = "Core engine for ArkaOS — The Operating System for AI Agent Teams"
5
5
  readme = "README.md"
6
6
  license = {text = "MIT"}