chore: install openagent opencode
Signed-off-by: Dmytro Stanchiev <git@dmytros.dev>
This commit is contained in:
88
.opencode/context/project-intelligence/business-domain.md
Normal file
88
.opencode/context/project-intelligence/business-domain.md
Normal file
@@ -0,0 +1,88 @@
|
||||
<!-- Context: project-intelligence/business | Priority: high | Version: 1.0 | Updated: 2025-01-12 -->
|
||||
|
||||
# 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
|
||||
@@ -0,0 +1,94 @@
|
||||
<!-- Context: project-intelligence/bridge | Priority: high | Version: 1.0 | Updated: 2025-01-12 -->
|
||||
|
||||
# Business ↔ Tech Bridge
|
||||
|
||||
> Document how business needs translate to technical solutions. This is the critical connection point.
|
||||
|
||||
## Quick Reference
|
||||
|
||||
- **Purpose**: Show stakeholders technical choices serve business goals
|
||||
- **Purpose**: Show developers business constraints drive architecture
|
||||
- **Update When**: New features, refactoring, business pivot
|
||||
|
||||
## Core Mapping
|
||||
|
||||
| Business Need | Technical Solution | Why This Mapping | Business Value |
|
||||
|---------------|-------------------|------------------|----------------|
|
||||
| [Users need X] | [Technical implementation] | [Why this maps] | [Value delivered] |
|
||||
| [Business wants Y] | [Technical implementation] | [Why this maps] | [Value delivered] |
|
||||
| [Compliance requires Z] | [Technical implementation] | [Why this maps] | [Value delivered] |
|
||||
|
||||
## Feature Mapping Examples
|
||||
|
||||
### Feature: [Feature Name]
|
||||
|
||||
**Business Context**:
|
||||
- User need: [What users need]
|
||||
- Business goal: [Why this matters to business]
|
||||
- Priority: [Why this was prioritized]
|
||||
|
||||
**Technical Implementation**:
|
||||
- Solution: [What was built]
|
||||
- Architecture: [How it fits the system]
|
||||
- Trade-offs: [What was considered and why it won]
|
||||
|
||||
**Connection**:
|
||||
[Explain clearly how the technical solution serves the business need. What would happen without this feature? What does this feature enable for the business?]
|
||||
|
||||
### Feature: [Feature Name]
|
||||
|
||||
**Business Context**:
|
||||
- User need: [What users need]
|
||||
- Business goal: [Why this matters to business]
|
||||
- Priority: [Why this was prioritized]
|
||||
|
||||
**Technical Implementation**:
|
||||
- Solution: [What was built]
|
||||
- Architecture: [How it fits the system]
|
||||
- Trade-offs: [What was considered and why it won]
|
||||
|
||||
**Connection**:
|
||||
[Explain clearly how the technical solution serves the business need.]
|
||||
|
||||
## Trade-off Decisions
|
||||
|
||||
When business and technical needs conflict, document the trade-off:
|
||||
|
||||
| Situation | Business Priority | Technical Priority | Decision Made | Rationale |
|
||||
|-----------|-------------------|-------------------|---------------|-----------|
|
||||
| [Conflict] | [What business wants] | [What tech wants] | [What was chosen] | [Why this was right] |
|
||||
|
||||
## Common Misalignments
|
||||
|
||||
| Misalignment | Warning Signs | Resolution Approach |
|
||||
|--------------|---------------|---------------------|
|
||||
| [Type of mismatch] | [Symptoms to watch for] | [How to address] |
|
||||
|
||||
## Stakeholder Communication
|
||||
|
||||
This file helps translate between worlds:
|
||||
|
||||
**For Business Stakeholders**:
|
||||
- Shows that technical investments serve business goals
|
||||
- Provides context for why certain choices were made
|
||||
- Demonstrates ROI of technical decisions
|
||||
|
||||
**For Technical Stakeholders**:
|
||||
- Provides business context for architectural decisions
|
||||
- Shows the "why" behind constraints and requirements
|
||||
- Helps prioritize technical debt with business impact
|
||||
|
||||
## Onboarding Checklist
|
||||
|
||||
- [ ] Understand the core business needs this project addresses
|
||||
- [ ] See how each major feature maps to business value
|
||||
- [ ] Know the key trade-offs and why decisions were made
|
||||
- [ ] Be able to explain to stakeholders why technical choices matter
|
||||
- [ ] Be able to explain to developers why business constraints exist
|
||||
|
||||
## Related Files
|
||||
|
||||
- `business-domain.md` - Business needs in detail
|
||||
- `technical-domain.md` - Technical implementation in detail
|
||||
- `decisions-log.md` - Decisions made with full context
|
||||
- `living-notes.md` - Current open questions and issues
|
||||
130
.opencode/context/project-intelligence/decisions-log.md
Normal file
130
.opencode/context/project-intelligence/decisions-log.md
Normal file
@@ -0,0 +1,130 @@
|
||||
<!-- Context: project-intelligence/decisions | Priority: high | Version: 1.0 | Updated: 2025-01-12 -->
|
||||
|
||||
# Decisions Log
|
||||
|
||||
> Record major architectural and business decisions with full context. This prevents "why was this done?" debates.
|
||||
|
||||
## Quick Reference
|
||||
|
||||
- **Purpose**: Document decisions so future team members understand context
|
||||
- **Format**: Each decision as a separate entry
|
||||
- **Status**: Decided | Pending | Under Review | Deprecated
|
||||
|
||||
## Decision Template
|
||||
|
||||
```markdown
|
||||
## [Decision Title]
|
||||
|
||||
**Date**: YYYY-MM-DD
|
||||
**Status**: [Decided/Pending/Under Review/Deprecated]
|
||||
**Owner**: [Who owns this decision]
|
||||
|
||||
### Context
|
||||
[What situation prompted this decision? What was the problem or opportunity?]
|
||||
|
||||
### Decision
|
||||
[What was decided? Be specific about the choice made.]
|
||||
|
||||
### Rationale
|
||||
[Why this decision? What were the alternatives and why were they rejected?]
|
||||
|
||||
### Alternatives Considered
|
||||
| Alternative | Pros | Cons | Why Rejected? |
|
||||
|-------------|------|------|---------------|
|
||||
| [Alt 1] | [Pros] | [Cons] | [Why not chosen] |
|
||||
| [Alt 2] | [Pros] | [Cons] | [Why not chosen] |
|
||||
|
||||
### Impact
|
||||
**Positive**: [What this enables or improves]
|
||||
**Negative**: [What trade-offs or limitations this creates]
|
||||
**Risk**: [What could go wrong]
|
||||
|
||||
### Related
|
||||
- [Links to related decisions, PRs, issues, or documentation]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Decision: [Title]
|
||||
|
||||
**Date**: YYYY-MM-DD
|
||||
**Status**: [Status]
|
||||
**Owner**: [Owner]
|
||||
|
||||
### Context
|
||||
[What was happening? Why did we need to decide?]
|
||||
|
||||
### Decision
|
||||
[What we decided]
|
||||
|
||||
### Rationale
|
||||
[Why this was the right choice]
|
||||
|
||||
### Alternatives Considered
|
||||
| Alternative | Pros | Cons | Why Rejected? |
|
||||
|-------------|------|------|---------------|
|
||||
| [Option A] | [Good things] | [Bad things] | [Reason] |
|
||||
| [Option B] | [Good things] | [Bad things] | [Reason] |
|
||||
|
||||
### Impact
|
||||
- **Positive**: [What we gain]
|
||||
- **Negative**: [What we trade off]
|
||||
- **Risk**: [What to watch for]
|
||||
|
||||
### Related
|
||||
- [Link to PR #000]
|
||||
- [Link to issue #000]
|
||||
- [Link to documentation]
|
||||
|
||||
---
|
||||
|
||||
## Decision: [Title]
|
||||
|
||||
**Date**: YYYY-MM-DD
|
||||
**Status**: [Status]
|
||||
**Owner**: [Owner]
|
||||
|
||||
### Context
|
||||
[What was happening?]
|
||||
|
||||
### Decision
|
||||
[What we decided]
|
||||
|
||||
### Rationale
|
||||
[Why this was right]
|
||||
|
||||
### Alternatives Considered
|
||||
| Alternative | Pros | Cons | Why Rejected? |
|
||||
|-------------|------|------|---------------|
|
||||
| [Option A] | [Good things] | [Bad things] | [Reason] |
|
||||
|
||||
### Impact
|
||||
- **Positive**: [What we gain]
|
||||
- **Negative**: [What we trade off]
|
||||
|
||||
### Related
|
||||
- [Link]
|
||||
|
||||
---
|
||||
|
||||
## Deprecated Decisions
|
||||
|
||||
Decisions that were later overturned (for historical context):
|
||||
|
||||
| Decision | Date | Replaced By | Why |
|
||||
|----------|------|-------------|-----|
|
||||
| [Old decision] | [Date] | [New decision] | [Reason] |
|
||||
|
||||
## Onboarding Checklist
|
||||
|
||||
- [ ] Understand the philosophy behind major architectural choices
|
||||
- [ ] Know why certain technologies were chosen over alternatives
|
||||
- [ ] Understand trade-offs that were made
|
||||
- [ ] Know where to find decision context when questions arise
|
||||
- [ ] Understand what decisions are pending and why
|
||||
|
||||
## Related Files
|
||||
|
||||
- `technical-domain.md` - Technical implementation affected by these decisions
|
||||
- `business-tech-bridge.md` - How decisions connect business and technical
|
||||
- `living-notes.md` - Current open questions that may become decisions
|
||||
114
.opencode/context/project-intelligence/living-notes.md
Normal file
114
.opencode/context/project-intelligence/living-notes.md
Normal file
@@ -0,0 +1,114 @@
|
||||
<!-- Context: project-intelligence/notes | Priority: high | Version: 1.0 | Updated: 2025-01-12 -->
|
||||
|
||||
# Living Notes
|
||||
|
||||
> Active issues, technical debt, open questions, and insights that don't fit elsewhere. Keep this alive.
|
||||
|
||||
## Quick Reference
|
||||
|
||||
- **Purpose**: Capture current state, problems, and open questions
|
||||
- **Update**: Weekly or when status changes
|
||||
- **Archive**: Move resolved items to bottom with status
|
||||
|
||||
## Technical Debt
|
||||
|
||||
| Item | Impact | Priority | Mitigation |
|
||||
|------|--------|----------|------------|
|
||||
| [Debt item] | [What risk it creates] | [High/Med/Low] | [How to manage] |
|
||||
|
||||
### Technical Debt Details
|
||||
|
||||
**[Debt Item]**
|
||||
*Priority*: [High/Med/Low]
|
||||
*Impact*: [What happens if not addressed]
|
||||
*Root Cause*: [Why this debt exists]
|
||||
*Proposed Solution*: [How to fix it]
|
||||
*Effort*: [Small/Medium/Large]
|
||||
*Status*: [Acknowledged | Scheduled | In Progress | Deferred]
|
||||
|
||||
## Open Questions
|
||||
|
||||
| Question | Stakeholders | Status | Next Action |
|
||||
|----------|--------------|--------|-------------|
|
||||
| [Question] | [Who needs to decide] | [Open/In Progress] | [What needs to happen] |
|
||||
|
||||
### Open Question Details
|
||||
|
||||
**[Question]**
|
||||
*Context*: [Why this question matters]
|
||||
*Stakeholders*: [Who needs to be involved]
|
||||
*Options*: [What are the possibilities]
|
||||
*Timeline*: [When does this need resolution]
|
||||
*Status*: [Open/In Progress/Blocked]
|
||||
|
||||
## Known Issues
|
||||
|
||||
| Issue | Severity | Workaround | Status |
|
||||
|-------|----------|------------|--------|
|
||||
| [Issue] | [Critical/High/Med/Low] | [Temporary fix] | [Known/In Progress/Fixed] |
|
||||
|
||||
### Issue Details
|
||||
|
||||
**[Issue Title]**
|
||||
*Severity*: [Critical/High/Med/Low]
|
||||
*Impact*: [Who/what is affected]
|
||||
*Reproduction*: [Steps to reproduce if applicable]
|
||||
*Workaround*: [Temporary solution if exists]
|
||||
*Root Cause*: [If known]
|
||||
*Fix Plan*: [How to properly fix]
|
||||
*Status*: [Known/In Progress/Fixed in vX.X]
|
||||
|
||||
## Insights & Lessons Learned
|
||||
|
||||
### What Works Well
|
||||
- [Positive pattern 1] - [Why it works]
|
||||
- [Positive pattern 2] - [Why it works]
|
||||
|
||||
### What Could Be Better
|
||||
- [Area for improvement 1] - [Why it's a problem]
|
||||
- [Area for improvement 2] - [Why it's a problem]
|
||||
|
||||
### Lessons Learned
|
||||
- [Lesson 1] - [Context and implication]
|
||||
- [Lesson 2] - [Context and implication]
|
||||
|
||||
## Patterns & Conventions
|
||||
|
||||
### Code Patterns Worth Preserving
|
||||
- [Pattern 1] - [Where it lives, why it's good]
|
||||
- [Pattern 2] - [Where it lives, why it's good]
|
||||
|
||||
### Gotchas for Maintainers
|
||||
- [Gotcha 1] - [What to watch out for]
|
||||
- [Gotcha 2] - [What to watch out for]
|
||||
|
||||
## Active Projects
|
||||
|
||||
| Project | Goal | Owner | Timeline |
|
||||
|---------|------|-------|----------|
|
||||
| [Project] | [What we're doing] | [Who owns it] | [When it matters] |
|
||||
|
||||
## Archive (Resolved Items)
|
||||
|
||||
Moved here for historical reference. Current team should refer to current notes above.
|
||||
|
||||
### Resolved: [Item]
|
||||
- **Resolved**: [Date]
|
||||
- **Resolution**: [What was decided/done]
|
||||
- **Learnings**: [What we learned from this]
|
||||
|
||||
## Onboarding Checklist
|
||||
|
||||
- [ ] Review known technical debt and understand impact
|
||||
- [ ] Know what open questions exist and who's involved
|
||||
- [ ] Understand current issues and workarounds
|
||||
- [ ] Be aware of patterns and gotchas
|
||||
- [ ] Know active projects and timelines
|
||||
- [ ] Understand the team's priorities
|
||||
|
||||
## Related Files
|
||||
|
||||
- `decisions-log.md` - Past decisions that inform current state
|
||||
- `business-domain.md` - Business context for current priorities
|
||||
- `technical-domain.md` - Technical context for current state
|
||||
- `business-tech-bridge.md` - Context for current trade-offs
|
||||
65
.opencode/context/project-intelligence/navigation.md
Normal file
65
.opencode/context/project-intelligence/navigation.md
Normal file
@@ -0,0 +1,65 @@
|
||||
<!-- Context: project-intelligence/nav | Priority: high | Version: 1.0 | Updated: 2025-01-12 -->
|
||||
|
||||
# Project Intelligence
|
||||
|
||||
> Start here for quick project understanding. These files bridge business and technical domains.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
.opencode/context/project-intelligence/
|
||||
├── navigation.md # This file - quick overview
|
||||
├── business-domain.md # Business context and problem statement
|
||||
├── technical-domain.md # Stack, architecture, technical decisions
|
||||
├── business-tech-bridge.md # How business needs map to solutions
|
||||
├── decisions-log.md # Major decisions with rationale
|
||||
└── living-notes.md # Active issues, debt, open questions
|
||||
```
|
||||
|
||||
## Quick Routes
|
||||
|
||||
| What You Need | File | Description |
|
||||
|---------------|------|-------------|
|
||||
| Understand the "why" | `business-domain.md` | Problem, users, value proposition |
|
||||
| Understand the "how" | `technical-domain.md` | Stack, architecture, integrations |
|
||||
| See the connection | `business-tech-bridge.md` | Business → technical mapping |
|
||||
| Know the context | `decisions-log.md` | Why decisions were made |
|
||||
| Current state | `living-notes.md` | Active issues and open questions |
|
||||
| All of the above | Read all files in order | Full project intelligence |
|
||||
|
||||
## Usage
|
||||
|
||||
**New Team Member / Agent**:
|
||||
1. Start with `navigation.md` (this file)
|
||||
2. Read all files in order for complete understanding
|
||||
3. Follow onboarding checklist in each file
|
||||
|
||||
**Quick Reference**:
|
||||
- Business focus → `business-domain.md`
|
||||
- Technical focus → `technical-domain.md`
|
||||
- Decision context → `decisions-log.md`
|
||||
|
||||
## Integration
|
||||
|
||||
This folder is referenced from:
|
||||
- `.opencode/context/core/standards/project-intelligence.md` (standards and patterns)
|
||||
- `.opencode/context/core/system/context-guide.md` (context loading)
|
||||
|
||||
See `.opencode/context/core/context-system.md` for the broader context architecture.
|
||||
|
||||
## Maintenance
|
||||
|
||||
Keep this folder current:
|
||||
- Update when business direction changes
|
||||
- Document decisions as they're made
|
||||
- Review `living-notes.md` regularly
|
||||
- Archive resolved items from decisions-log.md
|
||||
|
||||
**Management Guide**: See `.opencode/context/core/standards/project-intelligence-management.md` for complete lifecycle management including:
|
||||
- How to update, add, and remove files
|
||||
- How to create new subfolders
|
||||
- Version tracking and frontmatter standards
|
||||
- Quality checklists and anti-patterns
|
||||
- Governance and ownership
|
||||
|
||||
See `.opencode/context/core/standards/project-intelligence.md` for the standard itself.
|
||||
108
.opencode/context/project-intelligence/technical-domain.md
Normal file
108
.opencode/context/project-intelligence/technical-domain.md
Normal file
@@ -0,0 +1,108 @@
|
||||
<!-- Context: project-intelligence/technical | Priority: high | Version: 1.0 | Updated: 2025-01-12 -->
|
||||
|
||||
# Technical Domain
|
||||
|
||||
> Document the technical foundation, architecture, and key decisions.
|
||||
|
||||
## Quick Reference
|
||||
|
||||
- **Purpose**: Understand how the project works technically
|
||||
- **Update When**: New features, refactoring, tech stack changes
|
||||
- **Audience**: Developers, DevOps, technical stakeholders
|
||||
|
||||
## Primary Stack
|
||||
|
||||
| Layer | Technology | Version | Rationale |
|
||||
|-------|-----------|---------|-----------|
|
||||
| Language | [e.g., TypeScript] | [Version] | [Why this language] |
|
||||
| Framework | [e.g., Node.js] | [Version] | [Why this framework] |
|
||||
| Database | [e.g., PostgreSQL] | [Version] | [Why this database] |
|
||||
| Infrastructure | [e.g., AWS, Vercel] | [N/A] | [Why this infra] |
|
||||
| Key Libraries | [List important ones] | [Versions] | [Why each matters] |
|
||||
|
||||
## Architecture Pattern
|
||||
|
||||
```
|
||||
Type: [Monolith | Microservices | Serverless | Agent-based | Hybrid]
|
||||
Pattern: [Brief description]
|
||||
Diagram: [Link to architecture diagram if exists]
|
||||
```
|
||||
|
||||
### Why This Architecture?
|
||||
|
||||
[Explain the business and technical reasons for this architecture choice. What problem does this architecture solve? What were alternatives considered?]
|
||||
|
||||
## Project Structure
|
||||
|
||||
```
|
||||
[Project Root]
|
||||
├── src/ # Source code
|
||||
├── tests/ # Test files
|
||||
├── docs/ # Documentation
|
||||
├── scripts/ # Build/deploy scripts
|
||||
└── [Other key directories]
|
||||
```
|
||||
|
||||
**Key Directories**:
|
||||
- `src/` - Contains all application logic organized by [module/feature/domain]
|
||||
- `tests/` - [How tests are organized]
|
||||
- `docs/` - [What documentation lives here]
|
||||
|
||||
## Key Technical Decisions
|
||||
|
||||
| Decision | Rationale | Impact |
|
||||
|----------|-----------|--------|
|
||||
| [Decision 1] | [Why this choice] | [What it enables] |
|
||||
| [Decision 2] | [Why this choice] | [What it enables] |
|
||||
|
||||
See `decisions-log.md` for full decision history with alternatives.
|
||||
|
||||
## Integration Points
|
||||
|
||||
| System | Purpose | Protocol | Direction |
|
||||
|--------|---------|----------|-----------|
|
||||
| [API 1] | [What it does] | [REST/GraphQL/gRPC] | [Inbound/Outbound] |
|
||||
| [Database] | [What it stores] | [PostgreSQL/Mongo/etc] | [Internal] |
|
||||
| [Service] | [What it provides] | [HTTP/gRPC] | [Outbound] |
|
||||
|
||||
## Technical Constraints
|
||||
|
||||
| Constraint | Origin | Impact |
|
||||
|------------|--------|--------|
|
||||
| [Legacy systems] | [Business/Tech] | [What limitation it creates] |
|
||||
| [Compliance] | [Regulation] | [What must be followed] |
|
||||
| [Performance] | [SLAs] | [What must be met] |
|
||||
|
||||
## Development Environment
|
||||
|
||||
```
|
||||
Setup: [Quick setup command or link]
|
||||
Requirements: [What developers need installed]
|
||||
Local Dev: [How to run locally]
|
||||
Testing: [How to run tests]
|
||||
```
|
||||
|
||||
## Deployment
|
||||
|
||||
```
|
||||
Environment: [Production/Staging/Development]
|
||||
Platform: [Where it deploys]
|
||||
CI/CD: [Pipeline used]
|
||||
Monitoring: [Tools for observability]
|
||||
```
|
||||
|
||||
## Onboarding Checklist
|
||||
|
||||
- [ ] Know the primary tech stack
|
||||
- [ ] Understand the architecture pattern and why it was chosen
|
||||
- [ ] Know the key project directories and their purpose
|
||||
- [ ] Understand major technical decisions and rationale
|
||||
- [ ] Know integration points and dependencies
|
||||
- [ ] Be able to set up local development environment
|
||||
- [ ] Know how to run tests and deploy
|
||||
|
||||
## Related Files
|
||||
|
||||
- `business-domain.md` - Why this technical foundation exists
|
||||
- `business-tech-bridge.md` - How business needs map to technical solutions
|
||||
- `decisions-log.md` - Full decision history with context
|
||||
Reference in New Issue
Block a user