lrh-design

Generate structured technical designs for software features using a multi-phase evaluation framework.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/xenotaur/logical_robotics_harness --skill lrh-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lrh-design
Source: https://github.com/xenotaur/logical_robotics_harness/tree/main/.claude/skills/lrh-design
Command: npx skills add https://github.com/xenotaur/logical_robotics_harness --skill lrh-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the lack of structured planning in software development by enforcing a rigorous design framework that catches architectural flaws and blockers before implementation begins.

Core Features & Use Cases

  • Design Framework: Guides users through a systematic process including prior art checks, best practice surveys, and high-level architectural planning.
  • Scope Assessment: Evaluates the complexity of a proposed feature and recommends the appropriate LRH artifact, such as a work item, proposal, or workstream.
  • Use Case: Use this before starting a complex feature to ensure the approach is sound, avoids duplication, and aligns with project constraints.

Quick Start

Invoke the lrh-design skill by providing a clear description of the feature or system you intend to build.

Frequently Asked Questions about lrh-design

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

FAQPage Schema
How do I create a structured technical design for a complex software feature?

To create a structured technical design, you need a framework that evaluates architectural decisions, checks prior art, and assesses scope. This skill generates that design by validating choices against project constraints before implementation begins.

What is the best way to evaluate architecture trade-offs before starting development?

Evaluating architecture trade-offs requires systematic verification of design choices against constraints. This skill applies a multi-phase evaluation framework to analyze alternatives and formalize scope, ensuring robust development planning.

How do I check for prior art and existing solutions when planning system improvements?

Checking for prior art involves surveying existing best practices and architectural decisions. This skill guides you through systematic checks to ensure your proposed approach avoids duplication and aligns with project constraints.

Can I use this design framework to assess the complexity and scope of a proposed feature?

Yes, you can use this design framework for scope assessment. It evaluates the complexity of a proposed feature and recommends the appropriate LRH artifact, such as a work item, proposal, or workstream, for subsequent implementation tasks.

Do I need to provide a full specification to generate a high-level architectural plan?

No, you do not need a full specification. You can invoke the design process by providing a clear description of the feature or system you intend to build, and the framework will generate the high-level architectural plan.

When should I not use a multi-phase design evaluation framework for software planning?

You should avoid using a multi-phase design evaluation framework for simple tasks that require no architectural decisions. It is designed for complex features where validating trade-offs, checking prior art, and formalizing scope are necessary.