Back to list
WellApp-ai

tech-divergence

by WellApp-ai

No more Sundays on Finance. We build the infrastructure that retrieves, processes, and routes your financial and business data to your FinOps stack, so founders can ship, not spreadsheet.

305🍴 43📅 Jan 23, 2026

SKILL.md


name: tech-divergence description: Evaluate technical options with scoring matrix, trigger Gate 4 for significant decisions

Tech Divergence Skill

Evaluate technical implementation options using an 8-dimension scoring matrix. Low scores auto-proceed; high scores (>= 4) trigger Gate 4 for human decision.

When to Use

  • During Plan Mode Phase 2 (Technical Diverge)
  • Before committing to a specific architecture or pattern
  • When multiple valid implementation approaches exist

Scoring Matrix (8 Dimensions)

Each dimension scores 0 (auto-proceed) or 1 (adds to checkpoint score):

Dimension0 (Low Risk)1 (Checkpoint)
PatternExists in codebaseNew pattern required
ScopeSingle domainCross-domain impact
Data ModelAdd field to existingNew entity/table
DependenciesUse existing libsNew dependency
API SurfaceInternal onlyPublic/breaking change
ReversibilityEasy to undoRequires migration
SecurityNon-sensitive dataAuth/permissions
PerformanceSimple CRUDCache/queue/optimization

Phase 1: Gather Context

1.1 Query Pattern Library (Notion)

Check if similar patterns exist:

API-query-database:
  database_id: "[PATTERN_LIBRARY_DB_ID]"
  filter:
    property: "Domain"
    select:
      equals: "[current domain]"

1.2 Search Codebase

SemanticSearch: "How is [similar feature] implemented?"
Grep: "[pattern name]" in relevant directories

1.3 Query Context7 (External Libraries)

If new libraries are being considered:

Context7 MCP:
1. resolve-library-id: libraryName = "[library]"
2. get-library-docs: topic = "best practices", mode = "info"

Phase 2: Score Each Dimension

For each of the 8 dimensions, evaluate and score:

## Technical Divergence Score

| Dimension | Score | Rationale |
|-----------|-------|-----------|
| Pattern | 0/1 | [Exists/New] |
| Scope | 0/1 | [Single/Cross-domain] |
| Data Model | 0/1 | [Field/Entity] |
| Dependencies | 0/1 | [Existing/New] |
| API Surface | 0/1 | [Internal/Public] |
| Reversibility | 0/1 | [Easy/Migration] |
| Security | 0/1 | [Non-sensitive/Auth] |
| Performance | 0/1 | [CRUD/Optimization] |
| **TOTAL** | [0-8] | |

Phase 3: Determine Path

If Score < 4: Auto-Proceed

## Technical Approach: Auto-Proceed

**Score:** [N]/8 (below threshold)

**Selected Approach:** [Describe the approach]

**Rationale:** 
- Pattern exists: [reference]
- Low cross-domain impact
- Easy to reverse if needed

Proceeding to Commit Plan...

If Score >= 4: Gate 4 (Human Checkpoint)

## Gate 4: Technical Approach Selection

**Score:** [N]/8 (threshold reached)

**Why human input needed:**
- [List dimensions that scored 1]

### Option A: [Name] (Conservative)

**Approach:** [Description]
**Effort:** S
**Risk:** Low
**Trade-off:** [What you give up]

### Option B: [Name] (Balanced)

**Approach:** [Description]
**Effort:** M
**Risk:** Medium
**Trade-off:** [What you give up]

### Option C: [Name] (Bold)

**Approach:** [Description]
**Effort:** L
**Risk:** Higher
**Trade-off:** [What you give up]

---

**Which approach would you like to proceed with?** (A / B / C)

*If you reject an option, I'll invoke decision-capture to record why.*

Phase 4: Record Decision

After Gate 4 selection:

  1. If option rejected, invoke decision-capture skill
  2. Record selected approach in context for Commit Plan
  3. Update Pattern Library if new pattern established

Integration with Plan Mode

This skill is invoked during Plan Mode Phase 2:

Plan Mode Flow:
Phase 1: APPETITE → 
Phase 2: TECHNICAL DIVERGE (this skill) →
  If score < 4: Auto-proceed
  If score >= 4: Gate 4 → Human selects
Phase 3: COMMIT PLAN

MCP Tools Used

ToolPurpose
Notion MCPQuery Pattern Library database
Context7 MCPGet library best practices
SemanticSearchFind existing codebase patterns
GrepSearch for specific implementations

Example Scoring

Low Score Example (Auto-Proceed)

Feature: Add a new column to existing table

DimensionScoreRationale
Pattern0Column additions done before
Scope0Single domain (tables)
Data Model0Adding field, not entity
Dependencies0Using existing libs
API Surface0Internal only
Reversibility0Easy migration
Security0Non-sensitive data
Performance0Simple CRUD
TOTAL0Auto-proceed

High Score Example (Gate 4)

Feature: Add real-time collaboration

DimensionScoreRationale
Pattern1No WebSocket patterns yet
Scope1Affects auth, tables, workflows
Data Model1New presence entity
Dependencies1Need socket.io
API Surface1New WS endpoints
Reversibility1Would need cleanup migration
Security1User session handling
Performance1Needs connection pooling
TOTAL8Gate 4 required

Invocation

Invoked automatically by Plan Mode Phase 2, or manually with "use tech-divergence skill".

Score

Total Score

80/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

+5
最近の活動

1ヶ月以内に更新

+10
フォーク

10回以上フォークされている

+5
Issue管理

オープンIssueが50未満

0/5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

+5

Reviews

💬

Reviews coming soon