Brainforge Knowledge

PROJECT-PLAN-TEMPLATE

3 min read

[Initiative/Plan Title]

Status: Draft
Created: YYYY-MM-DD
Updated: YYYY-MM-DD (context for update)
Author: [name]
CSO: [name]
Service Leads: [name] (Data), [name] (Strategy & Reporting)
Client: [Client name] - [Sponsor name, title]

Quick Links:

1. Context & Problem Statement

Current State

[What is the current situation? What has been done so far? Be specific about the starting point.]

Problem Statement

[What needs to be addressed? Use numbered list for specific problems.]

  1. Problem 1
  2. Problem 2
  3. Problem 3

Goal

[Clear, measurable or narrative outcome. What does success look like at the end of this initiative?]

2. Connection to Broader Goals

Client Strategic Objectives

  • [How this aligns with client strategic goals]
  • [Specific client outcomes this enables]

Company/Delivery Standards

  • [How this aligns with Brainforge Q2 delivery standards]
  • [Connection to mentorship program, quantifiable metrics, etc.]

3. Work Phases

Phase 1: [Name] (Weeks X-Y: [Month])

  • Task 1
  • Task 2
  • Task 3

Phase 2: [Name] (Weeks X-Y: [Month])

  • Task 1
  • Task 2

Phase 3: [Name] (Weeks X-Y: [Month])

  • Task 1
  • Task 2

Phase 4: [Name] (Weeks X-Y: [Month])

  • Task 1
  • Task 2

4. Success Metrics

MetricBeforeTarget (End)Owner
Metric 1[value][target][name]
Metric 2[value][target][name]
Metric 3[value][target][name]

5. Risks & Mitigations

RiskMitigationOwner
[Risk 1: Description][How to address if it occurs][name]
[Risk 2: Description][How to address if it occurs][name]
[Risk 3: Description][How to address if it occurs][name]

6. Open Questions

  1. [Question 1] - [Context/why it matters for the plan]
  2. [Question 2] - [Context/why it matters for the plan]
  3. [Question 3] - [Context/why it matters for the plan]

7. Next Steps

  • [Action item with clear deliverable] (owner: [name]) - Due: [date]
  • [Action item with clear deliverable] (owner: [name]) - Due: [date]
  • [Action item with clear deliverable] (owner: [name]) - Due: [date]
ResourceLocationDescription
[Name]path/to/file.md[What it contains]
[Name]path/to/file.md[What it contains]
[Name]path/to/file.md[What it contains]

9. Sign-offs

Internal plans: Team lead proposes; Executive sponsor approves. Both sign before plan is locked.

Team leads: Source from Supabase org table or ask the human. Do not pre-fill names from transcripts or inference.

  • Team Lead — Scope, outcomes, resourcing — [ ] Signed off? (Owner: ________________)
  • Executive Sponsor — Alignment with company goals — [ ] Signed off? (Owner: ________________)

10. Linear Execution (Optional)

For complex initiatives, outline the Linear structure to be created/updated. See quarterly-planning skill for execution guidance.

Current Linear State

  • To audit: List existing initiatives, projects, orphaned issues
  • Likely findings: [What you expect to find]

Proposed Linear Structure

Option A: Single Initiative with Phase Projects

Initiative[Name]Target: YYYY-MM-DD
ProjectPhase 1: [Name]Milestones: [list]
ProjectPhase 2: [Name]Milestones: [list]

Option B: Multiple Thematic Initiatives

Initiative[Thematic Name]Target: YYYY-MM-DD
Project[Name]Milestones: [list]
Project[Name]Milestones: [list]

Linear Cleanup Actions

  • Audit: List issues without project assignment
  • Create: [Initiative/Project names]
  • Label: Apply taxonomy (type, priority, status, quarter, owner)

Label Taxonomy

Type: data-modeling, integration, analytics, reporting, infrastructure
Priority: p0-urgent, p1-high, p2-medium, p3-low
Status: needs-review, ready-for-work, in-review, blocked
Quarter: q1-2026, q2-2026, q3-2026, q4-2026
Owner: [service-lead-names], [client-team-names]

When Done

  1. Move this file to knowledge/plans/completed/
  2. Add Shipped in PR block at top (see knowledge/plans/completed/README.md)
  3. Update Linear initiative status to “Completed”
  4. Archive associated projects or move to “Completed”

Last updated: YYYY-MM-DD

Graph View