Digital Platform Specification Template
Mohamad Charafeddine — mohamadcharafeddine.com/en/resources/platform-spec-template/
========================================

── Platform specification template ──

1) Overview
   Problem: [what happens today and why it is costly, slow or unfair]
   For whom: [roles in brief]
   Success after 3 months means: [observable outcomes]
   Not a goal: [what the platform will not do]

2) Roles
   For each role: name | who they are | what they want |
   how they get the role (self sign-up, invitation, assignment)

3) Permissions matrix
   Rows = actions on each entity, columns = roles
   Values: yes | no | own only | with approval

4) Entities and data
   For each entity: fields | required? | sensitive? | owner |
   relation to other entities | retention period

5) Workflows
   For each workflow: trigger | steps in order | who performs each step |
   notifications | what if it fails

6) States and transitions
   For each entity with a lifecycle: states | allowed transitions |
   who triggers them | what happens

7) First-version scope
   Must have now | Later | Will not do

8) Integrations
   Service | purpose | data direction | account owner | what if it stops

9) Non-functional requirements
   Languages and direction | accessibility | security and sign-in | backups
   | audit log | expected performance | devices

10) Risks
   Risk | likelihood | impact | mitigation | owner

11) Backlog
   As a [role] I want [action] so that [benefit]
   + acceptance criteria + priority + stage

12) Open questions and decisions log
   Question | who answers | due date | decision | date


── Critical review prompt ──

You are a strict systems analyst.
Below is the spec for a platform [short description].
Do not add features or suggest technologies. Only list:
1) Contradictions between roles, the permissions matrix and the workflows.
2) Missing or dangerous state transitions (e.g. what if cancelled after confirmation?).
3) Data collected without a clear reason, or sensitive data with no stated protection.
4) Workflow actions that no role has permission to perform.
5) Five questions the project owner must answer before starting.
Order findings from most to least serious. Do not flatter.
Spec: [paste text after removing any personal data or keys]