Handoff to Departments

What management produces and where each downstream department picks it up.

---

What management hands off

Doc	Lives in	Read by
PRD_v<N>.md	docs/management/mvp/v<N>/	All departments
SRS_v<N>.md	docs/management/mvp/v<N>/	Backend, Frontend, QA
user_story_v<N>.md	docs/management/mvp/v<N>/	Design, Frontend, QA
roadmap_v<N>.md	docs/management/mvp/v<N>/	All departments
tasks_v<N>.md (per dept)	docs/<dept>/mvp/v<N>/	The owning department
acceptance_v<N>.md (per dept)	docs/<dept>/mvp/v<N>/	The owning department + QA
deps_v<N>.md	docs/management/mvp/v<N>/	All departments

---

Handoff rules

• Management creates the per-department task and acceptance docs. The department owns and updates them afterwards.
• Management never edits a department's internal docs (code conventions, design system, etc.).
• Every handoff doc must be at status: review minimum before a department starts work on it.

---

What management expects back

From	What	Where
Backend	API contracts, schema updates	docs/backend/mvp/v<N>/
Frontend	Component map, route plan	docs/frontend/mvp/v<N>/
Design	Page specs, component library	docs/design/mvp/v<N>/
QA	Test plan, coverage report	docs/qa/mvp/v<N>/
Marketing	Launch checklist, messaging	docs/marketing/mvp/v<N>/

These appear in dept.yaml → inputs for management's next planning round.

---

Coordination

For cross-department blockers use:

management: agent project-management-project-shepherd unblock <topic>

The shepherd reads all dept folders, identifies the dependency, and writes a coordination note to docs/management/mvp/v<N>/coordination_<topic>.md.