跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

ln-71-system-design-baseline-builder

Creates a project baseline of architecture drivers and constraints. Use before design or planning; not for target design, plan review, implementation, or architecture audit.

levnikolaevich · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add levnikolaevich/claude-code-skills --skill ln-71-system-design-baseline-builder

技能说明


name: ln-71-system-design-baseline-builder description: "Creates a project baseline of architecture drivers and constraints. Use before design or planning; not for target design, plan review, implementation, or architecture audit."

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: Treat the ordered checkbox workflow below as this skill's Definition of Done. Track every checkbox as PENDING, then resolve it to PROVEN with concrete evidence, CLEARED with evidence that its conditional trigger is absent, or UNPROVEN; reading, mentioning, delegating, skipping, or tool failure is not proof. Before returning, resolve every PENDING, count only PROVEN and CLEARED items as complete, apply this skill's verdict, decision, and approval rules to every UNPROVEN, and prepend Checklist: X/Y completeIncomplete: None | section/item — reason; outcome impact; exact next action; list every UNPROVEN item.

Tool Routing

NeedPreferred capabilityFallback
Repository rules and document conventionsNative file reads plus focused searchUser-provided convention with an explicit limitation
Existing requirements and architecture artifactsNarrow repository search and direct readsConversation evidence marked with its source
Current workload or service evidenceMetrics, dashboards, logs, manifests, or checked-in reportsMark UNKNOWN; never manufacture production numbers
Current external limits or standardsOfficial documentation or specificationsMark the claim UNVERIFIED
Document mutationMinimal patch to the approved Markdown artifactReturn 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 APPLICABLE or NOT_APPLICABLE, with evidence for exclusions.
  • Rank each applicable item as DRIVER, SUPPORTING, or INFORMATIONAL.
  • Classify evidence separately as CONFIRMED, ASSUMED, or UNKNOWN.
  • Record source, owner, confirmation date, and review trigger for each architecture driver.
  • Separate observed current values, required targets, hard limits, and future evolution triggers.
  • Use measurable quality-attribute scenarios; avoid words such as "fast", "scalable", or "secure" without a response measure.
  • 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 BLOCKED if the destination is ambiguous and choosing one could split project truth.

2. Build the Evidence Ledger

  • Extract confirmed business goals, actors, critical journeys, scope, non-goals, and decision horizon.
  • 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 boundaries, data classification, residency, access, audit, and destructive-action constraints.
  • Operations and economics: Define ownership, operational capacity, cost envelope, supported regions, delivery cadence, and platform or vendor constraints.
  • Evolution: Record thresholds, business events, or evidence that justify revisiting an assumption, target, or deferred capability.
  • Separate applicability, criticality, and evidence status; do not use UNKNOWN to mean unimportant or NOT_APPLICABLE.
  • Prioritize the few scenarios most likely to shape architecture and express each as source/stimulus/environment/artifact/response/measure.

4. Write the Baseline

  • Create or update the artifact with: identity and status; business context; scope and non-goals; critical scenarios; workload and data; quality targets; recovery; consistency; security; cost and operations; constraints; assumptions and unknowns; review triggers.
  • Give every material paramete
阅读完整来源 ↗