ln-71-system-design-baseline-builder

Creates a versioned architecture baseline documenting drivers, constraints, and quality targets before design.

556|83|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-71-system-design-baseline-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-71-system-design-baseline-builder
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/plugins/architecture-suite/skills/ln-71-system-design-baseline-builder
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-71-system-design-baseline-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions often rest on scattered, unverified assumptions about workload, SLOs, compliance, and cost. This Skill consolidates those requirements into one canonical, evidence-backed baseline document so design and planning start from confirmed facts instead of guesses.

Core Features & Use Cases

  • Evidence Ledger: Separates confirmed facts, assumptions, and unknowns with sources, owners, and confirmation dates for every architecture driver.
  • Driver Prioritization: Classifies requirements by applicability and criticality, expressing key scenarios as measurable source/stimulus/response quality-attribute statements.
  • Controlled Document Mutation: Updates a single approved Markdown artifact in place, preserving unrelated content and historical context.
  • Use Case: Before designing a new payment service, run this Skill to produce docs/architecture/system-design-baseline.md capturing traffic targets, RTO/RPO, data residency rules, and cost envelopes with evidence status for each.

Quick Start

Ask the agent to build a system design baseline for this project, documenting architecture drivers, SLOs, and constraints in a single Markdown artifact.

Frequently Asked Questions about ln-71-system-design-baseline-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document architecture drivers before system design?

Run this Skill to build a baseline artifact listing each driver with applicability, criticality, evidence status, source, owner, and review trigger. It expresses key scenarios as measurable source/stimulus/environment/response statements rather than vague qualities.

What is a system design baseline document?

It is a single versioned Markdown artifact recording business context, workload and data scale, SLOs, recovery targets, security and compliance constraints, and cost envelopes. The Skill writes it to docs/architecture/system-design-baseline.md unless an equivalent document already exists.

When should I not use the system design baseline builder?

Do not use it for target architecture design, plan review, implementation, or architecture audits. It only creates or updates the requirements baseline; downstream skills handle design, review, and auditing tasks.

How does it handle unknown or unverified requirements?

Unknowns are marked UNKNOWN or UNVERIFIED and never converted into confident facts. The final verdict is INCOMPLETE when consequential drivers remain open, and BLOCKED when scope, authority, or destination prevents safe creation.

Does the baseline builder modify product code?

No. It only mutates the approved architecture Markdown artifact with minimal patches, preserving unrelated content. The validation checklist explicitly confirms no product code, tests, or unrelated documents changed.