vickybiswas/Product Manager

## Product Manager
OUTPUT:
- 1. PRD document: describing "LinkDem" - A tool to help 1 - 10 member teams manage small 10 - 20 tasks events in a prescriptive way, guiding other agents (UI, DB, API, Testing, etc) on what you want not how to do it.

SPEC:
- Outcomes
- - One developer-ready Technical PRD in Markdown, containing but not limited to personas, user stories, acceptance criteria etc.
- Constraints
- - Have 2 Access Levels - Global / Event only - "Global" access mean a user can see/act across ALL events, while "Event-only" restricts them to specific events they're assigned to
- - Build functions for - users/roles/workflows/tasks/events
- - Add/Assign/reassign any task with a remark (mandatory) in any state(except Done)
- - Admin functions only (workflows, masters users/roles, RBAC/permissions etc.)
- - Auto Functions - add next tasks to Todo on one task done as defined in workflow on every task update
- - Admin can create roles for RBAC as a matrix with CRUD as columns and functions as rows, eg. Role1 - Users CR, Events RU. Every user will be assigned an Access Level and Role to expose the desired functions on Login
- DAG workflow engine - Just create and show 2 sample workflows 1 for a Birthday party and one for an Indian marriage, only view using react-flow. Admins can add/remove individual tasks manually within an event.
- - Every task in the workflow DAG has one or more roles assigned for task visibility. On task update trigger auto functions
- - Event will always follow one workflow assigned on create and cannot be changed -> Tasks will be created manually or auto created based on workflow rules
- - State machine of Workflow (must be explicit) TODO -> WIP <-> BLOCKED, WIP <-> VALIDATE -> DONE (transition happens ONLY for given directions)
- - Users can only see tasks on Kanban that are assigned to them or their role + tasks one step before/after in the workflow DAG. Admins see all task types and all users. The user can pick and work on one or more tasks. One task can be assigned to 1 user only or be unassigned in one state (no other state can have unassigned tasks)
- Validations
- - Ensure 3 or more Personas are being created and mapped to related user stories/acceptance criteria, etc
- - Ensure dense User stories are being created - As a <Persona>, I would <function> so that <outcome/constraint/mission etc.> can be met - with a concise detail about what and why, but not the how.
- - Ensure prescriptive guidance (what to consider, what problems to solve) for DB, UI, API and testing teams but not prescriptive specifications (exact endpoints, schemas, component names).
- - Ensure EVERYTHING in this spec is being taken care of in the PRD and is clearly labeled for use by other Agents (UI, API, DB, etc), nothing can be missed and there should be no next steps or milestones.
	OUTPUT:
	- 1. PRD document: describing "LinkDem" - A tool to help 1 - 10 member teams manage small 10 - 20 tasks events in a prescriptive way, guiding other agents (UI, DB, API, Testing, etc) on what you want not how to do it.

	SPEC:
	- Outcomes
	- - One developer-ready Technical PRD in Markdown, containing but not limited to personas, user stories, acceptance criteria etc.
	- Constraints
	- - Have 2 Access Levels - Global / Event only - "Global" access mean a user can see/act across ALL events, while "Event-only" restricts them to specific events they're assigned to
	- - Build functions for - users/roles/workflows/tasks/events
	- - Add/Assign/reassign any task with a remark (mandatory) in any state(except Done)
	- - Admin functions only (workflows, masters users/roles, RBAC/permissions etc.)
	- - Auto Functions - add next tasks to Todo on one task done as defined in workflow on every task update
	- - Admin can create roles for RBAC as a matrix with CRUD as columns and functions as rows, eg. Role1 - Users CR, Events RU. Every user will be assigned an Access Level and Role to expose the desired functions on Login
	- DAG workflow engine - Just create and show 2 sample workflows 1 for a Birthday party and one for an Indian marriage, only view using react-flow. Admins can add/remove individual tasks manually within an event.
	- - Every task in the workflow DAG has one or more roles assigned for task visibility. On task update trigger auto functions
	- - Event will always follow one workflow assigned on create and cannot be changed -> Tasks will be created manually or auto created based on workflow rules
	- - State machine of Workflow (must be explicit) TODO -> WIP <-> BLOCKED, WIP <-> VALIDATE -> DONE (transition happens ONLY for given directions)
	- - Users can only see tasks on Kanban that are assigned to them or their role + tasks one step before/after in the workflow DAG. Admins see all task types and all users. The user can pick and work on one or more tasks. One task can be assigned to 1 user only or be unassigned in one state (no other state can have unassigned tasks)
	- Validations
	- - Ensure 3 or more Personas are being created and mapped to related user stories/acceptance criteria, etc
	- - Ensure dense User stories are being created - As a <Persona>, I would <function> so that <outcome/constraint/mission etc.> can be met - with a concise detail about what and why, but not the how.
	- - Ensure prescriptive guidance (what to consider, what problems to solve) for DB, UI, API and testing teams but not prescriptive specifications (exact endpoints, schemas, component names).
	- - Ensure EVERYTHING in this spec is being taken care of in the PRD and is clearly labeled for use by other Agents (UI, API, DB, etc), nothing can be missed and there should be no next steps or milestones.
No results found