kin: KIN-DOCS-004-backend_dev

agents/prompts/architect.md

@@ -15,6 +15,7 @@ You receive:
 
 **Normal mode** (default):
 
+0. If PREVIOUS STEP OUTPUT contains a `context_packet` field — read it FIRST before opening any files or analyzing any other context. It contains the essential handoff: architecture decisions, critical file paths, constraints, and unknowns from the prior agent.
 1. Read `DESIGN.md`, `core/models.py`, `core/db.py`, `agents/runner.py`, and any MODULES files relevant to the task
 2. Understand the current architecture — what already exists and what needs to change
 3. Design the solution: data model, interfaces, component interactions

agents/prompts/backend_dev.md

@@ -12,6 +12,7 @@ You receive:
 
 ## Working Mode
 
+0. If PREVIOUS STEP OUTPUT contains a `context_packet` field — read it FIRST before opening any files or analyzing any other context. It contains the essential handoff: architecture decisions, critical file paths, constraints, and unknowns from the prior agent.
 1. Read all relevant backend files before making any changes
 2. Review `PREVIOUS STEP OUTPUT` if it contains an architect spec — follow it precisely
 3. Implement the feature or fix as described in the task brief

agents/prompts/department_head.md

@@ -28,6 +28,7 @@ You receive:
 - Handoff notes clarity — the next department must be able to start without asking questions
 - Previous department handoff — build on their work, don't repeat it
 - Sub-pipeline length — keep it SHORT, 1-4 steps maximum
+- Produce a `context_packet` with exactly 5 fields: `architecture_notes` (string — key arch decisions made), `key_files` (array of file paths critical for the next agent), `constraints` (array of hard technical/business limits discovered), `unknowns` (array of open risks or unresolved questions), `handoff_for` (string — role name of the first worker in sub_pipeline). In the brief for the FIRST worker in sub_pipeline, include this sentence verbatim: «IMPORTANT: Read the `context_packet` field in PREVIOUS STEP OUTPUT FIRST, before any other section or file.»
 
 **Department-specific guidance:**
 
@@ -46,6 +47,7 @@ You receive:
 - Each worker brief is self-contained — no "see above" references
 - Artifacts list is complete and specific
 - Handoff notes are actionable for the next department
+- `context_packet` is present with all 5 required fields; `handoff_for` is non-empty and matches the role in `sub_pipeline[0]`; first worker brief contains explicit instruction to read `context_packet` first
 
 ## Return Format
 
@@ -72,7 +74,14 @@ Return ONLY valid JSON (no markdown, no explanation):
     "schemas": [],
     "notes": "Added feature with full test coverage. All tests pass."
   },
-  "handoff_notes": "Backend implementation complete. Tests passing. Frontend needs to call POST /api/feature with {field: value} body."
+  "handoff_notes": "Backend implementation complete. Tests passing. Frontend needs to call POST /api/feature with {field: value} body.",
+  "context_packet": {
+    "architecture_notes": "Used existing models.py pattern, no ORM, raw sqlite3",
+    "key_files": ["core/models.py", "web/api.py"],
+    "constraints": ["All DB columns must have DEFAULT values", "No new Python deps"],
+    "unknowns": ["Frontend integration not yet verified"],
+    "handoff_for": "backend_dev"
+  }
 }
 ```
 

agents/prompts/frontend_dev.md

@@ -12,6 +12,7 @@ You receive:
 
 ## Working Mode
 
+0. If PREVIOUS STEP OUTPUT contains a `context_packet` field — read it FIRST before opening any files or analyzing any other context. It contains the essential handoff: architecture decisions, critical file paths, constraints, and unknowns from the prior agent.
 1. Read all relevant frontend files before making any changes
 2. Review `PREVIOUS STEP OUTPUT` if it contains an architect spec — follow it precisely
 3. Implement the feature or fix as described in the task brief