@agentworkforce/workload-router 0.4.1 → 0.5.1
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/CHANGELOG.md +12 -0
- package/README.md +9 -107
- package/dist/generated/personas.d.ts +263 -0
- package/dist/generated/personas.d.ts.map +1 -1
- package/dist/generated/personas.js +215 -0
- package/dist/generated/personas.js.map +1 -1
- package/dist/index.d.ts +14 -229
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +25 -481
- package/dist/index.js.map +1 -1
- package/dist/index.test.js +53 -193
- package/dist/index.test.js.map +1 -1
- package/package.json +1 -4
- package/routing-profiles/default.json +29 -88
- package/routing-profiles/schema.json +16 -2
|
@@ -3,93 +3,34 @@
|
|
|
3
3
|
"id": "balanced-default",
|
|
4
4
|
"description": "Default routing policy balancing depth/latency and cost while keeping a fixed quality bar.",
|
|
5
5
|
"intents": {
|
|
6
|
-
"implement-frontend": {
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
},
|
|
10
|
-
"
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
},
|
|
14
|
-
"
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
},
|
|
18
|
-
"
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
},
|
|
22
|
-
"
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
},
|
|
26
|
-
"
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
},
|
|
30
|
-
"
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
},
|
|
34
|
-
"
|
|
35
|
-
"tier": "best-value",
|
|
36
|
-
"rationale": "Completion checks need disciplined evidence review, but usually not the most expensive model."
|
|
37
|
-
},
|
|
38
|
-
"test-strategy": {
|
|
39
|
-
"tier": "best-value",
|
|
40
|
-
"rationale": "Test planning benefits from strong reasoning, but usually does not require the slowest or most expensive tier."
|
|
41
|
-
},
|
|
42
|
-
"tdd-enforcement": {
|
|
43
|
-
"tier": "best-value",
|
|
44
|
-
"rationale": "TDD coaching needs reliable process enforcement and concise feedback more than maximum-depth output."
|
|
45
|
-
},
|
|
46
|
-
"flake-investigation": {
|
|
47
|
-
"tier": "best",
|
|
48
|
-
"rationale": "Intermittent failures are expensive and subtle; prioritize deeper reasoning for reproduction and root-cause analysis."
|
|
49
|
-
},
|
|
50
|
-
"opencode-workflow-correctness": {
|
|
51
|
-
"tier": "best",
|
|
52
|
-
"rationale": "Cross-layer opencode workflow failures are expensive to misdiagnose; default to the deepest tier for end-to-end reproduction and root-cause analysis."
|
|
53
|
-
},
|
|
54
|
-
"npm-provenance": {
|
|
55
|
-
"tier": "best-value",
|
|
56
|
-
"rationale": "Publishing setup is mostly mechanical workflow configuration; best-value is sufficient when guided by the prpm/npm-trusted-publishing skill."
|
|
57
|
-
},
|
|
58
|
-
"cloud-sandbox-infra": {
|
|
59
|
-
"tier": "best",
|
|
60
|
-
"rationale": "Cloud infrastructure changes (sandbox provisioning, credential handling, session durability) have high blast radius; prioritize deeper reasoning and thorough verification."
|
|
61
|
-
},
|
|
62
|
-
"sage-slack-egress-migration": {
|
|
63
|
-
"tier": "best-value",
|
|
64
|
-
"rationale": "Slack egress migration work is mostly mechanical integration plumbing, so best-value is the default tradeoff."
|
|
65
|
-
},
|
|
66
|
-
"sage-proactive-rewire": {
|
|
67
|
-
"tier": "best-value",
|
|
68
|
-
"rationale": "Proactive rewiring is configuration-heavy coordination work that usually does not need the highest-cost tier by default."
|
|
69
|
-
},
|
|
70
|
-
"cloud-slack-proxy-guard": {
|
|
71
|
-
"tier": "best-value",
|
|
72
|
-
"rationale": "Proxy guard updates are typically policy and wiring checks, so best-value is a sensible default tier."
|
|
73
|
-
},
|
|
74
|
-
"sage-cloud-e2e-conduction": {
|
|
75
|
-
"tier": "best-value",
|
|
76
|
-
"rationale": "End-to-end conduction is orchestration-heavy work where strong reasoning is useful without requiring the top tier by default."
|
|
77
|
-
},
|
|
78
|
-
"capability-discovery": {
|
|
79
|
-
"tier": "best-value",
|
|
80
|
-
"rationale": "Searching skill.sh and prpm.dev for existing skills, agents, and hooks is lightweight research; the balanced default is sufficient when guided by the skill.sh/find-skills and @prpm/self-improving skills."
|
|
81
|
-
},
|
|
82
|
-
"posthog": {
|
|
83
|
-
"tier": "best-value",
|
|
84
|
-
"rationale": "PostHog queries are interactive analytics lookups; best-value is sufficient and keeps latency low when chatting with the MCP server."
|
|
85
|
-
},
|
|
86
|
-
"persona-authoring": {
|
|
87
|
-
"tier": "best",
|
|
88
|
-
"rationale": "New personas must satisfy a fixed conventions checklist (five wiring files, model-agnostic prompts, tier-isolation) before they typecheck; missing any step ships a broken routing entry, so depth over speed is the right default."
|
|
89
|
-
},
|
|
90
|
-
"slop-audit": {
|
|
91
|
-
"tier": "best",
|
|
92
|
-
"rationale": "Slop auditing reads across a diff or subtree and classifies findings into a multi-category taxonomy; missed slop ships unchanged, so depth over speed is the right default."
|
|
93
|
-
}
|
|
6
|
+
"implement-frontend": {"tier": "best-value", "rationale": "Most frontend tasks are iterative and benefit from strong quality-per-dollar defaults."},
|
|
7
|
+
"review": {"tier": "best-value", "rationale": "Code review usually needs careful reasoning without always requiring max-cost models."},
|
|
8
|
+
"architecture-plan": {"tier": "best", "rationale": "Architecture decisions are high leverage; prioritize depth and stronger reasoning."},
|
|
9
|
+
"requirements-analysis": {"tier": "best-value", "rationale": "Most scope clarification work benefits from careful synthesis without needing the slowest tier by default."},
|
|
10
|
+
"debugging": {"tier": "best", "rationale": "Root-cause debugging is expensive when wrong; default to deeper reasoning and stronger verification."},
|
|
11
|
+
"security-review": {"tier": "best", "rationale": "Security review has asymmetric downside; favor deeper analysis on default policy."},
|
|
12
|
+
"documentation": {"tier": "best-value", "rationale": "Most docs work benefits from solid code-grounded synthesis without always needing the top tier."},
|
|
13
|
+
"verification": {"tier": "best-value", "rationale": "Completion checks need disciplined evidence review, but usually not the most expensive model."},
|
|
14
|
+
"test-strategy": {"tier": "best-value", "rationale": "Test planning benefits from strong reasoning, but usually does not require the slowest or most expensive tier."},
|
|
15
|
+
"tdd-enforcement": {"tier": "best-value", "rationale": "TDD coaching needs reliable process enforcement and concise feedback more than maximum-depth output."},
|
|
16
|
+
"flake-investigation": {"tier": "best", "rationale": "Intermittent failures are expensive and subtle; prioritize deeper reasoning for reproduction and root-cause analysis."},
|
|
17
|
+
"opencode-workflow-correctness": {"tier": "best", "rationale": "Cross-layer opencode workflow failures are expensive to misdiagnose; default to the deepest tier for end-to-end reproduction and root-cause analysis."},
|
|
18
|
+
"npm-provenance": {"tier": "best-value", "rationale": "Publishing setup is mostly mechanical workflow configuration; best-value is sufficient when guided by the prpm/npm-trusted-publishing skill."},
|
|
19
|
+
"cloud-sandbox-infra": {"tier": "best", "rationale": "Cloud infrastructure changes (sandbox provisioning, credential handling, session durability) have high blast radius; prioritize deeper reasoning and thorough verification."},
|
|
20
|
+
"sage-slack-egress-migration": {"tier": "best-value", "rationale": "Slack egress migration work is mostly mechanical integration plumbing, so best-value is the default tradeoff."},
|
|
21
|
+
"sage-proactive-rewire": {"tier": "best-value", "rationale": "Proactive rewiring is configuration-heavy coordination work that usually does not need the highest-cost tier by default."},
|
|
22
|
+
"cloud-slack-proxy-guard": {"tier": "best-value", "rationale": "Proxy guard updates are typically policy and wiring checks, so best-value is a sensible default tier."},
|
|
23
|
+
"sage-cloud-e2e-conduction": {"tier": "best-value", "rationale": "End-to-end conduction is orchestration-heavy work where strong reasoning is useful without requiring the top tier by default."},
|
|
24
|
+
"capability-discovery": {"tier": "best-value", "rationale": "Searching skill.sh and prpm.dev for existing skills, agents, and hooks is lightweight research; the balanced default is sufficient when guided by the skill.sh/find-skills and @prpm/self-improving skills."},
|
|
25
|
+
"npm-package-compat": {"tier": "best-value", "rationale": "Package.json audits are mostly mechanical checks against known rules; best-value provides sufficient reasoning for catching misconfigurations."},
|
|
26
|
+
"posthog": {"tier": "best-value", "rationale": "PostHog queries are interactive analytics lookups; best-value is sufficient and keeps latency low when chatting with the MCP server."},
|
|
27
|
+
"persona-authoring": {"tier": "best", "rationale": "New personas must satisfy a fixed conventions checklist (five wiring files, model-agnostic prompts, tier-isolation) before they typecheck; missing any step ships a broken routing entry, so depth over speed is the right default."},
|
|
28
|
+
"slop-audit": {"tier": "best", "rationale": "Slop auditing reads across a diff or subtree and classifies findings into a multi-category taxonomy; missed slop ships unchanged, so depth over speed is the right default."},
|
|
29
|
+
"api-contract-review": {"tier": "best", "rationale": "Contract review catches silent breaking changes between deployed services; missing a discriminant collision or enum widening ships incidents, so depth over speed is the right default."},
|
|
30
|
+
"local-stack-orchestration": {"tier": "best-value", "rationale": "Compose authoring is mostly mechanical wiring once the topology is known; best-value is sufficient when guided by explicit healthcheck and pinning rules."},
|
|
31
|
+
"e2e-validation": {"tier": "best", "rationale": "End-to-end validation is the last line of defense before merge; missing a hop-level divergence ships broken behavior, so depth over speed is the right default."},
|
|
32
|
+
"write-integration-tests": {"tier": "best-value", "rationale": "Integration test authoring follows a fixed template (real substitute, wire-shape assertions, failure modes); best-value reasoning is sufficient when guided by the template."},
|
|
33
|
+
"agent-relay-workflow": {"tier": "best-value", "rationale": "new agent-relay-workflow capability requiring balanced reasoning and tooling"},
|
|
34
|
+
"relay-orchestrator": {"tier": "best-value", "rationale": "Relay orchestrator coordinates agent spawning with balanced reasoning and fast path for first-turn orchestration."}
|
|
94
35
|
}
|
|
95
36
|
}
|
|
@@ -10,7 +10,7 @@
|
|
|
10
10
|
"intents": {
|
|
11
11
|
"type": "object",
|
|
12
12
|
"additionalProperties": false,
|
|
13
|
-
"required": ["implement-frontend", "review", "architecture-plan", "requirements-analysis", "debugging", "security-review", "documentation", "verification", "test-strategy", "tdd-enforcement", "flake-investigation", "opencode-workflow-correctness", "npm-provenance", "cloud-sandbox-infra"],
|
|
13
|
+
"required": ["implement-frontend", "review", "architecture-plan", "requirements-analysis", "debugging", "security-review", "documentation", "verification", "test-strategy", "tdd-enforcement", "flake-investigation", "opencode-workflow-correctness", "npm-provenance", "cloud-sandbox-infra", "sage-slack-egress-migration", "sage-proactive-rewire", "cloud-slack-proxy-guard", "sage-cloud-e2e-conduction", "capability-discovery", "npm-package-compat", "posthog", "persona-authoring", "agent-relay-workflow", "slop-audit", "api-contract-review", "local-stack-orchestration", "e2e-validation", "write-integration-tests"],
|
|
14
14
|
"properties": {
|
|
15
15
|
"implement-frontend": { "$ref": "#/definitions/rule" },
|
|
16
16
|
"review": { "$ref": "#/definitions/rule" },
|
|
@@ -25,7 +25,21 @@
|
|
|
25
25
|
"flake-investigation": { "$ref": "#/definitions/rule" },
|
|
26
26
|
"opencode-workflow-correctness": { "$ref": "#/definitions/rule" },
|
|
27
27
|
"npm-provenance": { "$ref": "#/definitions/rule" },
|
|
28
|
-
"cloud-sandbox-infra": { "$ref": "#/definitions/rule" }
|
|
28
|
+
"cloud-sandbox-infra": { "$ref": "#/definitions/rule" },
|
|
29
|
+
"sage-slack-egress-migration": { "$ref": "#/definitions/rule" },
|
|
30
|
+
"sage-proactive-rewire": { "$ref": "#/definitions/rule" },
|
|
31
|
+
"cloud-slack-proxy-guard": { "$ref": "#/definitions/rule" },
|
|
32
|
+
"sage-cloud-e2e-conduction": { "$ref": "#/definitions/rule" },
|
|
33
|
+
"capability-discovery": { "$ref": "#/definitions/rule" },
|
|
34
|
+
"npm-package-compat": { "$ref": "#/definitions/rule" },
|
|
35
|
+
"posthog": { "$ref": "#/definitions/rule" },
|
|
36
|
+
"persona-authoring": { "$ref": "#/definitions/rule" },
|
|
37
|
+
"agent-relay-workflow": { "$ref": "#/definitions/rule" },
|
|
38
|
+
"slop-audit": { "$ref": "#/definitions/rule" },
|
|
39
|
+
"api-contract-review": { "$ref": "#/definitions/rule" },
|
|
40
|
+
"local-stack-orchestration": { "$ref": "#/definitions/rule" },
|
|
41
|
+
"e2e-validation": { "$ref": "#/definitions/rule" },
|
|
42
|
+
"write-integration-tests": { "$ref": "#/definitions/rule" }
|
|
29
43
|
}
|
|
30
44
|
}
|
|
31
45
|
},
|