ln-21-system-design-baseline-builder
Defines measurable architecture drivers and constraints before system design; edits architecture docs only.
levnikolaevich · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add levnikolaevich/claude-code-skills --skill ln-21-system-design-baseline-builderAbout this skill
name: ln-21-system-design-baseline-builder description: "Defines measurable architecture drivers and constraints before system design; edits architecture docs only."
System Design Baseline Builder
Goal: Create or update one durable source of truth for the project's architecture-driving requirements and constraints. Change only the approved architecture document; do not design the solution, review a plan, audit implementation, edit product code, or invent missing targets.
Execution contract: The ordered checkboxes are the Definition of Done. Track every item internally as PENDING, PROVEN with concrete evidence, CLEARED with evidence that its condition is absent, or UNPROVEN with a gap; reading, delegation, or tool failure is not proof. Reconcile items after each section. Before returning, resolve all PENDING and count only PROVEN and CLEARED; apply the skill's verdict and approval rules to every gap.
Preserve user intent, scope, and existing authorization. Continue authorized work; ask only for consequential unresolved choices or required external approval. Scale depth to material risk without silently skipping checks. Preserve dependency and safety ordering; otherwise choose the verification method appropriate to each obligation.
Treat equivalent user or repository evidence as valid input; another skill, named artifact, or complete lifecycle is not a prerequisite. Preserve source requirement and decision identifiers when available. Bind reused evidence to the relevant source version, dirty changes, configuration, and environment; invalidate only affected claims after a change.
On continuation, reconcile the task, existing authorization, current state, and unresolved evidence before resuming. For long work, return a compact continuation record or update an already authorized task artifact; read-only skills do not persist it. Distinguish artifact readiness, verified behavior, and authority to perform an external action.
Prepare authorized work before any required approval. If an instruction prevents progress, identify its exact source and explain the unresolved boundary; do not invent an approval gate from general caution.
Tool Routing
| Need | Preferred capability | Fallback |
|---|---|---|
| Repository rules and document conventions | Native file reads plus focused search | User-provided convention with an explicit limitation |
| Existing requirements and architecture artifacts | Narrow repository search and direct reads | Conversation evidence marked with its source |
| Current workload or service evidence | Metrics, dashboards, logs, manifests, or checked-in reports | Mark UNKNOWN; never manufacture production numbers |
| Current external limits or standards | Official documentation or specifications | Mark the claim UNVERIFIED |
| Document mutation | Minimal patch to the approved Markdown artifact | Return BLOCKED if no safe writable path is authorized |
Use external research only when a time-sensitive fact changes a constraint. Do not browse for values that must come from product owners, operators, the repository, or measured workload.
Artifact Rules
- Prefer an existing unambiguous architecture-requirements document.
- Otherwise use
docs/architecture/system-design-baseline.md. - Read before writing, preserve unrelated content, and update facts in place instead of creating parallel truth.
- Classify applicability separately as
APPLICABLEorNOT_APPLICABLE, with evidence for exclusions. - Rank each applicable item as
DRIVER,SUPPORTING, orINFORMATIONAL. - Classify evidence separately as
CONFIRMED,ASSUMED, orUNKNOWN. - Separate observed current values, required targets, hard limits, and future evolution triggers.
- Express quality attributes through observable scenarios and response measures; record undecided targets as missing decisions rather than inventing numbers.
- Treat the baseline as versioned project knowledge, not an immutable promise.
Checklist
1. Establish Scope and Destination
- Resolve the project, business outcome, intended readers, approved documentation scope, and language.
- Read applicable repository instructions and inspect Git state so unrelated changes remain untouched.
- Search for existing requirement, architecture, SLO, recovery, security, cost, and ownership documents.
- Select one canonical artifact: reuse a clear equivalent or choose the default path; explain why no duplicate will be created.
- Return
BLOCKEDif the destination is ambiguous and choosing one could split project truth.
2. Build the Evidence Ledger
- Collect business goals, actors, journeys, scope, non-goals, and decision horizon with their sources and confidence for the driver analysis; do not create a second context inventory.
- Record sources for current workload, data volume, service behavior, platform limits, and existing commitments.
- Separate repository facts from stakeholder choices and estimates.
- Detect contradictions between documents, code, configuration, and stated requirements; preserve both claims until resolved.
- Ask only for choices whose absence materially changes architecture; mark all other gaps
UNKNOWN.
3. Define and Prioritize Architecture Drivers
- Business and scope: Record actors, critical journeys, business horizon, scope, non-goals, and externally committed outcomes.
- Demand and data scale: Record current and target users, rates, concurrency, payloads, growth, retention, and forecast horizon where relevant.
- User-observable service quality: Define SLIs and SLOs for availability, latency, throughput, error rate, correctness, or freshness with measurement windows.
- Data semantics and recovery: Define consistency, ordering, idempotency, reconciliation, durability, backup, RTO, RPO, and acceptable data loss at affected boundaries.
- Security, privacy, and compliance: Define trust boundarie