Instruction file imported from arcaerdogar/web-crawler--multiagent-workflow (.cursor/rules/subagent-protocol.mdc). Copyright stays with the author.

Subagent Working Protocol

Stay In Your Scope

Each role has an explicit list of owned files in .cursor/rules/architecture.mdc. You may CREATE and MODIFY only files in your scope. You may READ any file (especially the type contract).

When Scope Is Insufficient

If your task requires modifying a file outside your scope:

1. STOP. Do not modify the out-of-scope file.
2. In your final report to the orchestrator, include a section titled ## Scope Escalation with:
   • The file path you needed to touch.
   • The reason (what you were trying to do).
   • A proposed change (diff or description).
3. The orchestrator will either: amend your scope, run another agent, or update the type contract via the Mimar role.

Verify Before Reporting Done

Before reporting completion, run:

cd backend && npx tsc --noEmit
cd frontend && npx tsc --noEmit

(Whichever sides your changes touched.) Report any remaining errors with file:line context.

Report Format

End your turn with:

## Done
- Files created/modified: <list>
- tsc --noEmit: PASS / FAIL (details)

## Scope Escalation (if any)
- ...

## Notes
- Anything the orchestrator should know.

Read Before Writing

Always read the type contract (backend/src/types.ts) before writing any code that touches shared interfaces. Never invent a type that should exist there.

No README Spam

Do NOT create README.md, CHANGELOG.md, or other docs unless explicitly told to. The orchestrator manages docs.