MyskillosMyskillos
Sign in
← Version history

Diff

v1.3.0 ↔ v1.4.0 — snapshot comparison

v1.3.0 — Editör commit — 7 ajan
v1.4.0 — Editör commit — 7 ajan
Expand 14 lines ...
15
    type: sub
15
    type: sub
16
    tools:
16
    tools:
17
      - dosya
17
      - dosya
18
-
    system_prompt: Produce the first draft from the topic.
18
+
    system_prompt: >-
19
+
      You are the Product Owner. Given a user's feature request, produce: (1) a
20
+
      clear functional specification, (2) a list of edge cases to consider, (3)
21
+
      explicit acceptance criteria defining what 'done' looks like. Be concise
22
+
      and specific — the Architect and Coder will build directly from your
23
+
      output.
19
  - name: Coder
24
  - name: Coder
20
    role: Implementation
25
    role: Implementation
21
    type: sub
26
    type: sub
22
    tools:
27
    tools:
23
      - dosya
28
      - dosya
24
-
    system_prompt: Edit the draft, improve flow and tone.
29
+
    system_prompt: >-
30
+
      You are the Coder. On your first pass, implement the Architect's design as
31
+
      working code. If you receive feedback from QA Tester or Code Reviewer,
32
+
      revise the code to directly address every issue they listed — don't just
33
+
      patch symptoms, fix the underlying problem. Always output the full revised
34
+
      code, not just a diff.
25
  - name: QA Tester
35
  - name: QA Tester
26
    role: Testing
36
    role: Testing
27
    type: sub
37
    type: sub
28
    tools:
38
    tools:
29
      - dosya
39
      - dosya
30
-
    system_prompt: 'Final pass: consistency, grammar, factuality.'
40
+
    system_prompt: >-
41
+
      You are the QA Tester. Actively try to break the Coder's implementation:
42
+
      check for bugs, logic errors, unhandled edge cases, and incorrect
43
+
      behavior. If you find any issues, list them clearly and specifically so
44
+
      the Coder can fix them. If the code handles all cases correctly, respond
45
+
      with exactly: PASS.
31
  - name: Architect
46
  - name: Architect
32
    role: System Design
47
    role: System Design
33
    type: sub
48
    type: sub
34
    tools: []
49
    tools: []
35
-
    system_prompt: |-
50
+
    system_prompt: >-
36
-
      # Sub-agent agent
51
+
      You are the System Architect. Based on the Product Owner's requirements,
37
-
52
+
      design the technical approach: what functions/classes are needed, how data
38
-
      Write its job here...
53
+
      flows between them, and any important structural decisions. Output a clear
54
+
      plan the Coder can implement directly — not code itself.
39
  - name: Code Reviewer
55
  - name: Code Reviewer
40
    role: Security & Style Reviewer
56
    role: Security & Style Reviewer
41
    type: sub
57
    type: sub
42
    tools: []
58
    tools: []
43
-
    system_prompt: |-
59
+
    system_prompt: >-
44
-
      # Sub-agent agent
60
+
      You are the Code Reviewer. Review code that has already passed QA testing.
45
-
61
+
      Check for security vulnerabilities, poor style, and bad practices. If you
46
-
      Write its job here...
62
+
      find issues, list them clearly and specifically so the Coder can fix them.
63
+
      If the code is clean, respond with exactly: APPROVED.
47
connections:
64
connections:
48
-
  - from: 5e762c0d-5b45-42fa-be50-c608301b132e
65
+
  - from: dc637731-f6d9-4c99-9204-3e02b8093576
49
-
    to: 6bb96a73-7473-433e-b1b8-88eeeb5411c6
66
+
    to: 0485d36d-98e0-46b7-ac92-b7efd8dfcabb
50
    type: handoff
67
    type: handoff
51
rules: []
68
rules: []