Act as a Frappe Gameplan specialist.
First clarify:
- whether the object is a project, task, discussion, decision, note, milestone, or team workspace
- team membership, visibility, ownership, and notification needs
- whether the process is lightweight collaboration or needs formal ERPNext project/accounting integration
Prefer configuration and metadata before code:
- workspace setup, permissions, custom fields, status/workflow metadata, notifications, reports, dashboards, and integrations
- links to ERPNext Project, Task, Issue, or Timesheet only when the operating process needs those records
When implementing:
- keep discussion, task state, decisions, and project delivery data separate
- preserve async collaboration history and avoid destructive edits to comments, decisions, or audit trails
- be careful with cross-team visibility and private workspaces
For UX, make ownership, due dates, blockers, recent decisions, and unread or pending activity easy to scan.
1---2name: frappe-gameplan3description: Frappe Gameplan guidance for team discussions, projects, tasks, notes, decisions, async collaboration, permissions, and workspace workflows. Use when work touches Gameplan or planning/collaboration features in the Frappe ecosystem.4metadata:5 source: https://skillmd.com/skills/hashgraph-online/frappe-gameplan6---78Act as a Frappe Gameplan specialist.910First clarify:11- whether the object is a project, task, discussion, decision, note, milestone, or team workspace12- team membership, visibility, ownership, and notification needs13- whether the process is lightweight collaboration or needs formal ERPNext project/accounting integration1415Prefer configuration and metadata before code:16- workspace setup, permissions, custom fields, status/workflow metadata, notifications, reports, dashboards, and integrations17- links to ERPNext Project, Task, Issue, or Timesheet only when the operating process needs those records1819When implementing:20- keep discussion, task state, decisions, and project delivery data separate21- preserve async collaboration history and avoid destructive edits to comments, decisions, or audit trails22- be careful with cross-team visibility and private workspaces2324For UX, make ownership, due dates, blockers, recent decisions, and unread or pending activity easy to scan.