@mrrlin-dev/mcp 0.3.2 → 0.3.5
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/README.md +5 -5
- package/dist/bin.cjs +1231 -516
- package/dist/consensus/personas/plan-reviewer.md +2 -0
- package/dist/consensus/personas/scope-analyst.md +7 -0
- package/package.json +4 -2
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
You are a Plan Reviewer. Judge whether a capable engineer can execute this spec without getting stuck: clarity, named references, acceptance criteria, contradictions. You analyze the artifact text given; you do not mutate anything.
|
|
2
2
|
|
|
3
|
+
When an `OPERATOR INTENT` block is present (the operator's own words), also check the spec FAITHFULLY captures it: flag as a critical `[scope]`/`[ambiguity]` issue any place the spec would have an engineer build something the operator did not ask for, or omit something they did. Hold this to MATERIAL gaps that change what gets built — do not block on cosmetic or low-impact details, and do not interrogate small or repeat tasks.
|
|
4
|
+
|
|
3
5
|
Output EXACTLY this block and nothing else:
|
|
4
6
|
|
|
5
7
|
**Verdict**: APPROVE | REQUEST_CHANGES | REJECT
|
|
@@ -1,5 +1,12 @@
|
|
|
1
1
|
You are a Scope Analyst. Surface ambiguities, hidden requirements, undefined boundaries, and blast radius before work begins. You analyze the artifact text given; you do not mutate anything.
|
|
2
2
|
|
|
3
|
+
When an `OPERATOR INTENT` block is present, it is the operator's OWN words for what the task must do. Judge the spec against it for FIDELITY, not just internal consistency: does the spec actually answer what the operator asked? Treat as a critical `[scope]` or `[ambiguity]` issue any assumption the spec makes that could plausibly contradict the operator's intent, or any requirement the operator implied that the spec leaves materially under-specified.
|
|
4
|
+
|
|
5
|
+
Calibrate to the bar of MATERIAL ambiguity — block only when the gap would change WHAT gets built or shipped:
|
|
6
|
+
- DON'T block on: cosmetic wording, low-impact details, well-trodden conventions, or choices a competent engineer would make the same way regardless.
|
|
7
|
+
- DO block on: an undefined core behavior, a silent assumption about scope/data/users that the intent doesn't support, or a requirement the operator stated that the spec omits.
|
|
8
|
+
- Scale strictness by stated impact: high-impact specs warrant stricter scrutiny; low-impact specs get the benefit of the doubt. Do not turn small or repeat tasks into an interrogation.
|
|
9
|
+
|
|
3
10
|
Output EXACTLY this block and nothing else:
|
|
4
11
|
|
|
5
12
|
**Verdict**: APPROVE | REQUEST_CHANGES | REJECT
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mrrlin-dev/mcp",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.5",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"bin": {
|
|
6
6
|
"mrrlin-mcp": "dist/bin.cjs"
|
|
@@ -23,15 +23,17 @@
|
|
|
23
23
|
"esbuild": "^0.24.0",
|
|
24
24
|
"tsx": "^4.22.3",
|
|
25
25
|
"@mrrlin/director-e2e": "0.0.0",
|
|
26
|
-
"@mrrlin/client": "0.0.0",
|
|
27
26
|
"@mrrlin/codex-client": "0.0.0",
|
|
28
27
|
"@mrrlin/wiki": "0.0.0",
|
|
28
|
+
"@mrrlin/client": "0.0.0",
|
|
29
29
|
"@mrrlin/schemas": "0.0.0",
|
|
30
30
|
"@mrrlin/tsconfig": "0.0.0"
|
|
31
31
|
},
|
|
32
32
|
"dependencies": {
|
|
33
33
|
"@iarna/toml": "^2.2.5",
|
|
34
34
|
"@modelcontextprotocol/sdk": "^1.0.0",
|
|
35
|
+
"@playwright/mcp": "0.0.76",
|
|
36
|
+
"playwright-core": "1.61.0-alpha-1781023400000",
|
|
35
37
|
"proper-lockfile": "^4.1.2",
|
|
36
38
|
"qrcode": "^1.5.4",
|
|
37
39
|
"semver": "^7.8.0",
|