lrh-workstream

Creates formal workstream artifacts with scope, exit criteria, and validation for Logical Robotics Harness.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of fragmented project planning by providing a standardized, evidence-backed workflow for creating and tracking formal workstreams within the Logical Robotics Harness.

Core Features & Use Cases

  • Formalized Planning: Guides the user through an interview process to define purpose, scope, exit criteria, and work items for a new workstream.
  • Prior Art Integration: Automatically performs duplication and demand searches to ensure new workstreams align with existing project efforts.
  • Traceable Execution: Mints unique prompt IDs and creates execution records to maintain a clear audit trail from proposal to closeout.

Quick Start

Invoke the lrh-workstream skill with a unique identifier to begin the interactive planning process for your new workstream.

Frequently Asked Questions about lrh-workstream

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

FAQPage Schema
How do I create a formal project workstream with traceable exit criteria?

You create a formal project workstream through an interactive interview that defines purpose, scope, exit criteria, and work items. The process mints unique prompt IDs to maintain a clear audit trail from proposal to closeout.

How does workstream planning prevent duplication with existing project efforts?

Workstream planning prevents duplication by performing automated prior art searches. This demand validation process ensures any new workstream aligns with existing project design documentation before execution.

Can I link new work items to existing project design documentation?

Yes, you can link new work items to existing project design documentation. The skill ensures traceability by automatically connecting new workstreams to existing execution records and prior project artifacts.

What is the best way to orchestrate structured governance for software engineering projects?

Orchestrating structured governance requires standardizing project scope definition and traceability. This skill provides an evidence-backed workflow to define exit criteria and track formal workstreams within a dedicated control plane.

Do I need a unique identifier to start the interactive project planning process?

Yes, you need a unique identifier to start the interactive planning process. Invoking the skill with this identifier initiates the interview to formalize your project workstream and validate prior art.

When should I not use an interactive interview for project workstream definition?

Interactive interviews are not suited for rapid, informal task tracking lacking formal governance. Use this approach only when your project requires strict exit criteria, evidence-backed validation, and full execution traceability.