skills.rest
kapilvirenahuja
kapilvirenahujaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

draft-lld

Generates a tech.yaml draft from features.yaml and architecture.yaml inputs.

3|Updated Jan 25, 2026
Search Tags:#system architecture#data model#low-level design#component mapping#deterministic delivery#tech.yaml
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill draft-lld
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: draft-lld
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/draft-lld
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill draft-lld

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft-lld turns high-level feature and architecture specifications into a concrete low-level design artifact, so teams can move from intent to implementable component structure without guessing.

Core Features & Use Cases

  • Creates a tech.yaml artifact only: produces a single tech.yaml (as a DRAFT) that captures project structure, libraries, data model, components, design decisions, and feature-to-component mappings.
  • Derives everything from inputs: reads features.yaml and architecture.yaml and uses them as the source of truth, without inventing stack choices.
  • Supports re-trigger safety: detects an existing LOCKED tech.yaml and fails with a structured message; overwrites an existing DRAFT artifact when re-triggered.
  • Keeps planning separate: intentionally does not validate output, does not generate plan.yaml, and does not decide execution order.

Quick Start

Use the draft-lld skill to generate tech.yaml from features.yaml and architecture.yaml at the specified output base directory.

Frequently Asked Questions about draft-lld

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

FAQPage Schema
How do I generate a low-level design from architecture specifications?▼

Generate a low-level design by converting feature and architecture specifications into a structured tech.yaml draft that decomposes logical architecture into buildable components, concrete libraries, and a data model for deterministic implementation.

What is tech.yaml used for in software design?▼

tech.yaml is used as a low-level design artifact to capture project structure, libraries, data model, components, design decisions, and feature-to-component mappings for deterministic implementation planning.

Does draft-lld validate the tech.yaml output or generate a plan?▼

No, draft-lld intentionally does not validate output, generate plan.yaml, or decide execution order. It strictly produces a tech.yaml draft and keeps planning separate.

How do I re-trigger tech.yaml generation without losing a locked design?▼

Re-triggering tech.yaml generation safely overwrites any existing DRAFT artifact, but detects an existing LOCKED tech.yaml and fails with a structured message to prevent overwriting locked designs.

Can I use custom technology selections in the low-level design draft?▼

No, you cannot use custom technology selections. The low-level design draft derives all technology selections strictly from architecture.yaml and uses it as the source of truth without inventing stack choices.

Related Skills

Explore More Software Engineering Skills→
kapilvirenahujakapilvirenahuja
3

draft-technical-approach

Convert a features specification into a DRAFT architecture.yaml with technology selections and prioritized NFRs.

Community
Advanced
kapilvirenahujakapilvirenahuja
3

draft-reference-algorithms

Generate language-agnostic reference pseudocode for complex internal interfaces from tech.yaml.

Community
Intermediate
SteveGJonesSteveGJones
41

author-workflow

Generate .archon/workflows YAML with prompts, team manifests, and validation steps.

Community
Advanced
yfyang86yfyang86
1

dennis-ritchie-perspective

Apply Dennis Ritchie's mental models to system design and language architecture decisions.

Community
Basic