starred/aryx
1
0
Fork 0
mirror of https://github.com/davidkaya/aryx.git synced 2026-07-28 15:38:37 +02:00
Code Issues 3 Packages Projects Releases 10 Wiki Activity

docs: strengthen backend/frontend plan-splitting requirement in AGENTS.md

Browse Source 
Make the two-phase planning rule a hard, no-exceptions requirement.
Clarify sequencing, separate-session expectation, and handover
artifact contract coverage. Add when-in-doubt-split directive.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
David Kaya
2026-03-28 14:08:30 +01:00
co-authored by Copilot
parent ae56d55c85
commit fa5774cbc0
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+6 -3
View File
@@ -158,10 +158,13 @@ Every interactive component must include basic accessibility:
## 8. Planning requirements
- If a task spans both backend and frontend work, the implementation plan must be split into **Part 1 — Backend** and **Part 2 — Frontend**. The Frontend part will be launched manually by the user.
- Backend work must be planned and executed first.
- Before frontend work begins, backend work must produce a handover artifact in the session workspace `files\` directory. Do not put this handover document in the repository.
> **Hard rule — no exceptions.** Every task that touches both backend (C# / sidecar) and frontend (TypeScript / renderer) code **must** produce a plan with exactly two phases: **Part 1 — Backend** and **Part 2 — Frontend**. A single combined plan that mixes backend and frontend work is never acceptable, even if the changes seem small or tightly coupled. When in doubt about whether a task spans both surfaces, treat it as spanning both and split the plan.
- **Part 1 — Backend** is always planned, implemented, tested, and committed first. No frontend work may begin until Part 1 is complete.
- **Part 2 — Frontend** is launched manually by the user in a separate session. Do not start frontend implementation in the same session as backend work.
- Before frontend work begins, backend work must produce a handover artifact in the session workspace `files\` directory. Do not put this handover document in the repository. The handover must describe every new or changed contract (DTOs, IPC messages, events, API shapes) that the frontend needs to consume.
- The frontend phase must consume that backend handover artifact and build on it rather than rediscovering backend contracts from scratch.
- If a task is frontend-only or backend-only, a two-part split is not required — but you must still confirm the scope before planning.
## 9. Validation checklist