lss-tech

Embed architectural decisions and test mappings into functional story text.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/liminal-ai/code-steward --skill lss-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lss-tech
Source: https://github.com/liminal-ai/code-steward/tree/main/.claude/skills/lss-tech
Command: npx skills add https://github.com/liminal-ai/code-steward --skill lss-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inline technical design and enrichment are split across multiple artifacts, creating friction between functional stories and architectural decisions. This skill closes the loop by performing the design inline and embedding it into the story narrative so engineers can implement with a single artifact.

Core Features & Use Cases

  • Inline design generation: produce architecture, interfaces, and test planning embedded directly into the story.
  • Codebase-aware analysis: analyze the target repository to align design decisions with existing patterns, conventions, and test strategies.
  • Story-size scope enrichment: tailor design outputs to a single story, avoiding epic-scale overhead.
  • Provenance and validation: capture the codebase context and deviations to guide implementation.

Quick Start

Provide a functional story; lss-tech will generate and embed inline technical design within the story text.

Frequently Asked Questions about lss-tech

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

FAQPage Schema
How do I embed inline technical design directly into a functional story?

Inline technical design is embedded directly into a functional story by automating architectural decisions, interfaces, and test mapping within the story's technical sections. This provides engineers with a single artifact for implementation.

What is story-enrichment for codebase analysis?

Story-enrichment for codebase analysis tailors technical design outputs to a single functional story. It analyzes the target repository to align architectural decisions with existing patterns, conventions, and test strategies.

Can I generate architecture context and interface contracts for a single story scope?

Yes, inline technical design generation produces architecture context and interface contracts specifically scoped to a single story. This avoids epic-scale overhead and embeds the contracts directly within the story narrative.

How do I map test cases to tests within a technical design document?

Test case to test mapping is automated by embedding TC-to-Test mapping and non-TC decided tests directly into the functional story. This ensures test planning aligns with the architectural decisions within the same artifact.

Does inline technical design capture provenance and deviations from existing codebase patterns?

Yes, the inline design process captures codebase context, provenance, and deviations. This guides implementation by documenting where and why the technical design diverges from existing repository patterns.

What is the best way to consolidate technical design artifacts with functional stories?

Consolidating technical design with functional stories is best achieved by embedding architecture, interfaces, and test mapping directly into the story text. This closes the loop between functional requirements and technical decisions into a single artifact.