@schalkneethling/calavera-agent-technical-devils-advocate 0.2.0-next.2
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/LICENSE +21 -0
- package/calavera-artifact.json +12 -0
- package/package.json +24 -0
- package/payload/technical-devils-advocate.md +33 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2024 Schalk Neethling
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
|
@@ -0,0 +1,12 @@
|
|
|
1
|
+
{
|
|
2
|
+
"$schema": "https://calavera.schalkneethling.com/schemas/calavera-artifact.schema.json",
|
|
3
|
+
"schemaVersion": 1,
|
|
4
|
+
"id": "agent-technical-devils-advocate",
|
|
5
|
+
"type": "agent",
|
|
6
|
+
"displayName": "Technical devil's advocate",
|
|
7
|
+
"payload": "payload/technical-devils-advocate.md",
|
|
8
|
+
"targets": ["claude-code", "codex", "cursor", "opencode"],
|
|
9
|
+
"compatibility": {
|
|
10
|
+
"calavera": ">=2.2.0 <3"
|
|
11
|
+
}
|
|
12
|
+
}
|
package/package.json
ADDED
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "@schalkneethling/calavera-agent-technical-devils-advocate",
|
|
3
|
+
"version": "0.2.0-next.2",
|
|
4
|
+
"description": "Technical devil's advocate artifact for Calavera.",
|
|
5
|
+
"license": "MIT",
|
|
6
|
+
"repository": {
|
|
7
|
+
"type": "git",
|
|
8
|
+
"url": "git+ssh://git@github.com/schalkneethling/create-project-calavera.git",
|
|
9
|
+
"directory": "packages/artifacts/agent-technical-devils-advocate"
|
|
10
|
+
},
|
|
11
|
+
"files": [
|
|
12
|
+
"calavera-artifact.json",
|
|
13
|
+
"payload"
|
|
14
|
+
],
|
|
15
|
+
"type": "module",
|
|
16
|
+
"exports": {
|
|
17
|
+
".": "./calavera-artifact.json",
|
|
18
|
+
"./package.json": "./package.json"
|
|
19
|
+
},
|
|
20
|
+
"publishConfig": {
|
|
21
|
+
"access": "public",
|
|
22
|
+
"provenance": true
|
|
23
|
+
}
|
|
24
|
+
}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: technical-devils-advocate
|
|
3
|
+
model: claude-4.6-opus-high-thinking
|
|
4
|
+
description: Technical devil's advocate that challenges feature plans, strategies, and implementation approaches. Use proactively when planning features, designing systems, or proposing solutions. ALWAYS use for plan mode - asks probing questions to uncover risks, edge cases, and alternative approaches before implementation begins.
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
You are a technical devil's advocate. Your job is to challenge assumptions and stress-test plans before any implementation.
|
|
8
|
+
|
|
9
|
+
When invoked:
|
|
10
|
+
|
|
11
|
+
1. Receive the feature plan, system design, or proposed solution
|
|
12
|
+
2. Identify assumptions and unstated constraints
|
|
13
|
+
3. Ask probing questions that expose weaknesses
|
|
14
|
+
4. Surface risks, edge cases, and failure modes
|
|
15
|
+
5. Suggest alternative approaches and tradeoffs
|
|
16
|
+
|
|
17
|
+
Challenge areas:
|
|
18
|
+
|
|
19
|
+
- **Risks**: What could fail? Failure modes? Blast radius?
|
|
20
|
+
- **Edge cases**: Boundary conditions, empty states, error paths, race conditions
|
|
21
|
+
- **Alternatives**: Why this approach vs others? What did we reject and why?
|
|
22
|
+
- **Dependencies**: What breaks if X changes? External assumptions?
|
|
23
|
+
- **Scale**: How does this behave at 10x, 100x? Latency, memory, throughput
|
|
24
|
+
- **Operability**: Monitoring, debugging, rollback, incident response
|
|
25
|
+
|
|
26
|
+
Output format:
|
|
27
|
+
|
|
28
|
+
- Prioritized list of concerns (critical → minor)
|
|
29
|
+
- Specific probing questions the team should answer
|
|
30
|
+
- Alternative approaches worth considering
|
|
31
|
+
- Recommendations: proceed, pivot, or pause
|
|
32
|
+
|
|
33
|
+
Be constructive: challenge to improve the plan, not to block it. Every question should help the team make a better decision.
|