Document Council: Doc Type → Personas Mapping
Purpose: Map document types to expert personas for the document-council skill. Brainforge is proserve and does many things; the council must match the doc. Stakeholder persona is always included — add only if not already in this doc type’s row (avoid duplicate Stakeholder); identity dynamic: client/internal/partner.
Reference: .cursor/skills/document-council/SKILL.md
Execution model (Human vs Partly AI vs Fully AI)
Not every document describes work that people will perform end-to-end. Many plans and automation specs are AI-executed (e.g. Cursor agent, scripts). The council should not default to staffing assumptions.
| Execution | What to emphasize in review | What to de-emphasize unless the doc claims it |
|---|---|---|
| Human-executed | Timeline, capacity, handoffs, DRIs, who approves | — |
| Partly AI (Human + AI) | Human-AI handoffs, which steps are agent vs human, interfaces, approval gates, failure fallbacks, human oversight points | Full autonomy assumptions, blanket hour estimates |
| Fully AI (Autonomous) | Scope, definition of done, unambiguous steps, tooling/API access, governance (secrets, client data), failure fallbacks, self-healing capabilities | Human hours, FTE, named DRI (unless needed for approval gates) |
Detection hints
- Stated in the doc: sections like “Execution model,” “Automated by,” “Agent will…”, “Human-in-the-loop”
- Path:
.cursor/plans/, manyknowledge/plans/automation specs → often Partly AI or Fully AI - Ask once if ambiguous; note the assumption in the review scorecard
Plan / implementation docs: If Fully AI, “Delivery lead” and “Implementer” personas should still run, but their lenses shift to agent executability (can an agent follow this without guessing?) rather than human sprint planning. For Partly AI, focus on the handoff interfaces.
Audience model (Internal vs External/Client vs Partner)
The stakeholder identity and review focus change based on who the document is for.
| Audience | Stakeholder Identity | Focus in review |
|---|---|---|
| Internal (Brainforge team) | “Internal Brainforge stakeholder (e.g., Head of Delivery, CEO)“ | Resource allocation, strategic fit, internal feasibility, Brainforge-specific context |
| External/Client (Deliverable) | “[Client name] sponsor/lead reviewing this deliverable” | Client-ready quality, no internal jargon, appropriate detail level, professional presentation |
| Partner (Co-sell/Partnership) | “Partner stakeholder reviewing co-sell brief” | Partnership value, clarity of collaboration, mutual benefit, co-sell readiness |
Detection hints
- Path:
knowledge/clients/{client}/...→ External/Client - Path:
knowledge/sales/partners/or content mentions “partner”, “co-sell” → Partner - Content: Mentions “client deliverable,” “for [ClientName],” “SOW” → External/Client
- Path:
knowledge/plans/,knowledge/sales/, internal folders (non-partnership) → Internal - Ask once if ambiguous; note the assumption in the review scorecard
Doc type → personas
| Doc type | Personas (2–4) | Focus |
|---|---|---|
| PRD | Product lead, Client/stakeholder POV, Engineer (feasibility), Delivery lead | Scope creep, missing acceptance criteria, unrealistic timeline |
| TDD / Technical design | Platform engineer, Security reviewer, Ops/reliability, Data engineer (if data) | Implementation gaps, security, runbooks, data lineage |
| Lightweight design doc | Implementer, Code reviewer, Stakeholder | Agent handoff clarity, acceptance criteria |
| SOW | Client success, Legal/compliance, Delivery lead, Finance (pricing) | Scope ambiguity, liability, handoff clarity, payment terms |
| Offer | Sales, Marketing, Delivery (can we deliver?) | Value prop clarity, proof points, differentiation |
| SOP | Delivery lead, PM, Ops, New joiner (can a new person follow this?) | Completeness, handoffs, DRIs, edge cases |
| Campaign brief | Marketing lead, Copywriter, GTM, Brand | Audience fit, CTA clarity, channel appropriateness |
| Client deliverable (DISCOVERY_WIKI, deck) | Client POV, Delivery lead, SME (domain accuracy) | Client-ready, no internal jargon, accuracy |
| Runbook / playbook | Ops, On-call engineer, New joiner | Copy-pasteable, rollback steps, escalation |
| Internal proposal / decision doc | Uttam Kumaran (CEO), Stakeholder, Finance, Legal (if needed) | Decision clarity, tradeoffs, approval path, metrics, jargon-free |
| Plan (implementation / skill design) | Uttam Kumaran (CEO), Delivery lead, Ops (tooling), Implementer, Stakeholder (internal) | Completeness, handoffs, trigger/routing, token/context efficiency; if Fully AI, add agent executability and drop human hour/DRI expectations unless stated |
| Other / unknown | Ask user for 2–3 personas, or use generic: Implementer, Stakeholder, Reviewer | — |
Detection hints
- Path:
knowledge/plans/→ plan/design;knowledge/sales/→ GTM doc;standards/→ playbook;.cursor/plans/→ Plan - Filename:
*prd*,*sow*,*sop*,*brief*,*workflow*,*plan*.md - Section headers: PRD: “Goals and Non-Goals”; TDD: “Target Architecture”; SOW: “Scope of Work”; Plan: “Workflow selection”, “Implementation todos”, “Execution model”
- Execution: Phrases like “Execution model,” “AI-executed,” “agent,” “automated,” “Human-in-the-loop” → use Execution model row in the council
- Audience: Path
knowledge/clients/{client}/→ use Audience model External row; Pathknowledge/sales/partners/→ use Partner row
Uttam Kumaran (CEO) persona
When to include: Internal proposals, decision docs, implementation/skill plans, and any high-stakes document where CEO perspective (metrics, audience clarity, jargon, partner vs staffing framing) is needed.
How to load: When running Document Council with this persona, use the full prompt in standards/04-prompts/planning/personas/uttam-kumaran.md as the system prompt for the CEO reviewer. The file defines identity, voice patterns, the four review lenses (Metrics & Reality, Data Feasibility, Vulnerability & Honesty, Jargon & Clarity), and output format.
How to develop more personas
To create a named persona (e.g. a specific person or role) like the CEO persona: see How to develop Document Council personas. That guide covers gathering sources (transcripts, written artifacts), defining identity and voice, review lenses, verdict style, and wiring the new persona into this mapping.
Extending
To add a new doc type:
- Add a row to the table above
- Define 2–4 personas and their focus
- Add detection hints (path, filename, headers) if applicable