ln-73-system-design-proposal-builder

Creates decision-complete target system design documents from requirements and constraints.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning requirements into a concrete system architecture often produces vague diagrams, hidden assumptions, and unjustified technology choices. This Skill enforces an evidence-backed workflow that produces a target design with explicit boundaries, contracts, estimates, failure behavior, and recorded tradeoffs before any implementation begins.

Core Features & Use Cases

  • Estimate-Driven Design: Computes request rates, storage growth, and bottleneck thresholds from sourced assumptions before selecting components, rejecting speculative scale.
  • Structured Architecture Artifacts: Produces domains, data models, API contracts, HLD, critical LLD, failure modes, and operations models in a single target-design document.
  • Decision Governance: Compares at least two credible alternatives per consequential decision, records reopen triggers, and returns READY, REVISE, or BLOCKED verdicts.
  • Use Case: Given an approved requirements baseline for a new ordering platform, generate a target design covering service boundaries, data ownership, failure handling, and rollout implications that an implementation planner can consume directly.

Quick Start

Ask the agent to build a target system design from your approved requirements document and constraints, writing the result to docs/architecture/target-design.md.

Frequently Asked Questions about ln-73-system-design-proposal-builder

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

FAQPage Schema
How do I create a system design document from requirements?

Provide approved requirements and constraints, then the workflow estimates load, defines domains and contracts, builds HLD and critical LLD, compares alternatives, and writes a target design document with a READY, REVISE, or BLOCKED verdict.

What should a target system design document include?

It should cover requirements and estimates, domain boundaries, data models, API contracts, high-level design, critical low-level design, failure and recovery behavior, security, operations, alternatives with tradeoffs, and open decisions.

When should I write a system design before implementation planning?

Write it after requirements are baselined but before implementation planning, so boundaries, contracts, and tradeoffs are decided. This Skill explicitly excludes requirements baselines, reviews, audits, and code changes.

Does this Skill modify code or implementation plans?

No. It only mutates the approved target-design document, defaulting to docs/architecture/target-design.md. It confirms no code, tests, delivery plans, or external state changed before returning.

What happens when design information is missing or unverifiable?

Gaps are labeled as assumptions, unknowns, or unverified claims. Material gaps produce a REVISE verdict, while missing business boundaries, authority, or safety constraints produce BLOCKED with the exact next action.