Activate for The Side System™ scoping phase. Runs side:scope — translates the side:sight diagnosis into a structured Priority Matrix, defines what is actually possible in what order, and produces a Scope Map. Use after diagnosis is complete and before any build work begins.
From brand-bond-osnpx claudepluginhub brandbondco/brand-bond-os --plugin brand-bond-osThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
"Before we build anything, we define what's actually possible."
side:scope is the filter between diagnosis and execution.
It prevents building the right thing in the wrong order.
| Trigger | Why |
|---|---|
| side:sight complete, real problem identified | Always follows side:sight |
| Client asks "where do we start?" | Scope before build |
| Multiple problems identified, prioritization unclear | Scope defines the order |
| Budget or timeline constraints need to be applied | Scope maps reality to ambition |
| Proposal requires defined deliverables | Can't price what isn't scoped |
Prerequisite: tss-sight must be complete. If the real problem isn't named, do not scope.
Every scope session produces a Priority Matrix. Each initiative is evaluated on:
| Axis | Definition |
|---|---|
| Impact | How directly does this fix the real problem? (1–5) |
| Effort | How complex is this to build or change? (1–5, lower = easier) |
| Dependency | Does this unlock other things? (Yes / No) |
| Risk | What breaks if we get this wrong? (Low / Medium / High) |
Scoring: Impact ÷ Effort = Priority Score. Sort descending. Dependencies override score when relevant.
Priority Matrix Format:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Initiative | Impact | Effort | Dependency | Risk | Priority
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[Initiative 1] | 5 | 2 | Yes | Med | 2.5 → 1st
[Initiative 2] | 4 | 3 | No | Low | 1.3 → 2nd
[Initiative 3] | 3 | 4 | No | Low | 0.75 → 3rd
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
After the Priority Matrix, map initiatives to 5S phases:
| Phase | Question it answers |
|---|---|
side:setup | What must be built first to unlock everything else? |
side:scale | What amplifies growth once the foundation exists? |
side:sync | What do we maintain and evolve over time? |
Scope Map Format:
SCOPE MAP
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Phase 1 — side:setup (Weeks 1–X)
→ [Initiative A] — [Deliverable]
→ [Initiative B] — [Deliverable]
Phase 2 — side:scale (Weeks X–Y)
→ [Initiative C] — [Deliverable]
Phase 3 — side:sync (Ongoing)
→ [Initiative D] — [Deliverable]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Every scope must define:
| Element | Rule |
|---|---|
| What's in | Named deliverables, not activities |
| What's out | Explicit — silence is not exclusion |
| Client inputs required | Defined upfront, not discovered during build |
| Revision rounds | Capped number per deliverable |
| Timeline owner | The Side System™ sets the timeline — client approves it |
Apply constraints before finalizing scope:
| Constraint | Scope adjustment |
|---|---|
| Limited budget | Reduce scope to highest-priority initiatives only |
| Short timeline | Compress phases, not quality — or extend timeline |
| Limited client access | Build for fewer dependencies on client input |
| Undefined data | Add side:sight loop before side:setup begins |
| Multiple decision makers | Map approval process into timeline |
SCOPE OUTPUT — side:scope
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Company: [Name]
Date: [YYYY-MM-DD]
Based on: side:sight report [date]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
PRIORITY MATRIX
[table]
SCOPE MAP
[phase breakdown]
WHAT'S NOT IN SCOPE
[explicit exclusions]
CLIENT INPUTS REQUIRED
[what we need from them, and when]
TIMELINE
[phase dates, with dependencies noted]
OPEN RISKS
[what could shift this scope and how]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
"Can't we just start building and figure it out?"
That's how scope creep starts. Two days of scoping prevents months of correction.
"The priority matrix takes too long."
It takes 90 minutes. That's 90 minutes to prevent building the wrong thing first.
"We want everything in Phase 1."
Everything can't be Phase 1. That's what makes Phase 1 Phase 1. Which three initiatives, if completed, unlock the rest?
| After side:scope | Next skill |
|---|---|
| Scope defined, proposal needed | → tss-proposal |
| Scope involves AI or design systems | → tss-intel |
| Scope involves build/execution | → tss-deck (for client presentation) |