cclohmar/OpenWriterControle
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
OpenWriterControle/.opencode/context/project-intelligence/business-domain.md
Darren Hinde 7590a7a2ff
docs(core): refine project intelligence system and deprecate legacy context (#93) 
* feat(context): Add project intelligence system

- Add project-intelligence.md standard (what & why)
- Add project-intelligence-management.md guide (how to manage)
- Add project-intelligence/ folder with 6 context files:
  - navigation.md (quick overview & routes)
  - business-domain.md (business context, users, value)
  - technical-domain.md (stack, architecture, decisions)
  - business-tech-bridge.md (business → technical mapping)
  - decisions-log.md (decision history with context)
  - living-notes.md (active issues, debt, questions)
- Update standards navigation with new entries
- Register all new contexts in registry.json

This enables projects to document and maintain business + technical
context for quick onboarding and lasting project understanding.

* fix(registry): Add project-intelligence to profiles

- Add context:project-intelligence/* to developer, business, full, and advanced profiles
- Ensures project intelligence contexts are included when these profiles are selected

This complements commit c731328 which added the context entries.

* docs(core): refine project intelligence system and deprecate legacy context
2026-01-13 11:25:18 +00:00

2.4 KiB
Raw Blame History

Business Domain

Document the business context, problems solved, and value created.

Quick Reference

  • Purpose: Understand why this project exists
  • Update When: Business direction changes, new features shipped, pivot
  • Audience: Developers needing context, stakeholders, product team

Project Identity

Project Name: [Name]
Tagline: [One-line description]
Problem Statement: [What problem are we solving?]
Solution: [How we're solving it]

Target Users

User Segment Who They Are What They Need Pain Points
[Primary] [Description] [Their needs] [Their frustrations]
[Secondary] [Description] [Their needs] [Their frustrations]

Value Proposition

For Users:

  • [Key benefit 1]
  • [Key benefit 2]
  • [Key benefit 3]

For Business:

  • [Key value 1]
  • [Key value 2]

Success Metrics

Metric Definition Target Current
[Metric 1] [What it measures] [Goal] [Actual]
[Metric 2] [What it measures] [Goal] [Actual]

Business Model (if applicable)

Revenue Model: [How the business makes money]
Pricing Strategy: [If applicable]
Unit Economics: [CAC, LTV, etc.]
Market Position: [Where we fit in the market]

Key Stakeholders

Role Name Responsibility Contact
[Product Owner] [Name] [What they own] [Contact]
[Tech Lead] [Name] [What they own] [Contact]
[Business Lead] [Name] [What they own] [Contact]

Roadmap Context

Current Focus: [What we're working on now] Next Milestone: [Upcoming goal] Long-term Vision: [Where this is heading]

Business Constraints

  • [Constraint 1] - [Why it exists]
  • [Constraint 2] - [Why it exists]

Onboarding Checklist

  • Understand the problem statement
  • Identify target users and their needs
  • Know the key value proposition
  • Understand success metrics
  • Know who the stakeholders are
  • Understand current business constraints

Related Files

  • technical-domain.md - How this business need is solved technically
  • business-tech-bridge.md - Mapping between business and technical
  • decisions-log.md - Business decisions with context