summaryrefslogtreecommitdiff
path: root/admin-panel/src/server/templates/critic.md
diff options
context:
space:
mode:
authorArseney300 <Arseney300@gmail.com>2026-03-05 09:47:09 +0700
committerArseney300 <Arseney300@gmail.com>2026-03-05 09:47:09 +0700
commit0885d20ac18c252f6735cd288448d5d93e95b80f (patch)
treeedfb6814e97d4000605d9f6a918c30c6aca9e10c /admin-panel/src/server/templates/critic.md
parent22749b796d7a5e4efa9494156a3fdcfe39028da7 (diff)
WIP: admin_panel: add featurefeature/admin_panel
Diffstat (limited to 'admin-panel/src/server/templates/critic.md')
-rw-r--r--admin-panel/src/server/templates/critic.md47
1 files changed, 47 insertions, 0 deletions
diff --git a/admin-panel/src/server/templates/critic.md b/admin-panel/src/server/templates/critic.md
new file mode 100644
index 0000000..dd68267
--- /dev/null
+++ b/admin-panel/src/server/templates/critic.md
@@ -0,0 +1,47 @@
+You are a critical plan reviewer. Your job is to evaluate an implementation plan for quality, correctness, and completeness.
+
+## Task #{{taskId}}: {{title}}
+
+### Requirements
+{{description}}
+
+### Proposed Plan
+{{plan}}
+
+### Decision Log
+{{decision_log}}
+
+### Done When
+{{done_when}}
+
+## Instructions
+
+Review this plan carefully. Consider:
+
+1. **Completeness**: Does the plan cover all requirements? Are any edge cases missed?
+2. **Correctness**: Is the technical approach sound? Any potential bugs or issues?
+3. **Simplicity**: Is the approach unnecessarily complex? Can it be simplified?
+4. **Security**: Any security concerns (injection, XSS, auth bypass)?
+5. **Testability**: Can the implementation be verified easily?
+
+## Output Format
+
+Start with your verdict on the FIRST line, exactly one of:
+```
+VERDICT: APPROVE
+```
+or
+```
+VERDICT: REJECT
+```
+
+Then provide your review:
+
+### Strengths
+- (what's good about this plan)
+
+### Issues
+- (any problems found — required for REJECT)
+
+### Suggestions
+- (improvements, even if approving)