speclan-engineering:hlrd-authoring

Transform unstructured HLRDs into SPECLAN specification trees with frontmatter and cross-references.

8|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/thlandgraf/cc-marketplace --skill speclan-engineering-hlrd-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speclan-engineering:hlrd-authoring
Source: https://github.com/thlandgraf/cc-marketplace/tree/main/plugins/speclan-engineering/skills/hlrd-authoring
Command: npx skills add https://github.com/thlandgraf/cc-marketplace --skill speclan-engineering-hlrd-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill imports unstructured High-Level Requirements Documents (HLRDs), PRDs, product briefs, or requirements text and transforms them into SPECLAN directory structures. It orchestrates a multi-phase pipeline that extracts a project Vision and Mission, plans Goals and Features, creates or updates them, generates testable Requirements, and performs cross-references — all driven by interactive prompts to resolve ambiguities.

Core Features & Use Cases

  • Import HLRDs and convert them into SPECLAN goals, features, and requirements.
  • Run a guided multi-phase pipeline (Vision/Mission, Planning, Creation, Cross-Referencing) with guided decisions.
  • Resolve the owner from git configuration and apply it to all created specs; support interactive clarification loops when needed.
  • Leverage the SPECLAN body templates and merge rules to maintain consistent frontmatter and prose.

Quick Start

Provide your HLDR document or paste the text when prompted, and invoke the hlrd import to scaffold SPECLAN specs.

Frequently Asked Questions about speclan-engineering:hlrd-authoring

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

FAQPage Schema
How do I convert unstructured product requirements into a specification tree?

To convert unstructured product requirements into a specification tree, this Skill imports your prose HLRDs or PRDs and applies a multi-phase pipeline to extract Vision and Mission, plan goals, create features, and generate testable requirements.

What is the best way to import a High-Level Requirements Document into SPECLAN?

The best way to import a High-Level Requirements Document into SPECLAN is to provide the document or paste text when prompted, which triggers a guided pipeline to scaffold SPECLAN directory structures and frontmatter.

Can I resolve project owner ambiguities when generating specs from a PRD?

Yes, you can resolve project owner ambiguities when generating specs by using interactive AskUserQuestion prompts; the Skill also automatically resolves the owner from git configuration to apply to created specs.

Does the SPECLAN specification pipeline support interactive clarification loops?

The SPECLAN specification pipeline supports interactive clarification loops through AskUserQuestion prompts, resolving ambiguities during Vision/Mission extraction, planning, creation, and cross-referencing phases.

How do I maintain consistent formatting when creating SPECLAN specifications from text?

To maintain consistent formatting when creating SPECLAN specifications from text, the Skill uses SPECLAN body templates, merge rules, and speclan-format to ensure frontmatter and prose structure remain uniform.