skills.rest
kangmomin
kangmominCOMMUNITY
Explore all skills by this author →
GitHub

request-hd

Guide users through phase-based questions to create technical specs.

1|1|Updated Apr 9, 2026
Search Tags:#ui#layout#specification#engineering#guided-questions#ascii-layout
One-click install
npx skills add https://github.com/kangmomin/harness-plugins --skill request-hd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: request-hd
Source: https://github.com/kangmomin/harness-plugins/tree/main/plugins/hyeondongs-harness/skills/request-hd
Command: npx skills add https://github.com/kangmomin/harness-plugins --skill request-hd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps teams generate actionable Technical Specs by orchestrating phase-based questions and ASCII layout confirmations, reducing miscommunication and lengthy back-and-forth between design and engineering.

Core Features & Use Cases

  • Guided Phase 0: Clarify task type with targeted questions and ASCII layout previews.
  • Phase 1-3: Collect requirements (page/component/api changes), verify layout, and produce a complete technical spec.
  • Use Case: A design/engineering team needs to spec a new UI feature; the guide walks through page structure, data requirements, and layout before implementation.

Quick Start

Generate a new UI/Component/API spec for the requested feature using guided questions.

Frequently Asked Questions about request-hd

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

FAQPage Schema
How do I create a technical spec for a UI feature without back-and-forth?▼

Generate a technical spec for a UI feature using guided phase-based questions and ASCII layout confirmations to collect page structure and data requirements. This enforces explicit scope and reduces miscommunication between design and engineering teams.

What is the best way to document API integration requirements for engineering?▼

Document API integration requirements by walking through iterative phase-based clarifications that collect data requirements and implementation details. This produces a complete technical spec covering screen creation, modification, and API wiring tasks.

Can I use ASCII layouts to confirm UI component specifications before implementation?▼

Yes, you can use ASCII layouts to confirm UI component specifications before implementation. The guide verifies layout during phases 1-3, ensuring clear scope and data requirements are established before engineering work begins.

How to guide a team through phase-based questions for component creation specs?▼

Guide a team through phase-based questions for component creation by starting at Phase 0 to clarify task type with targeted questions, then progressing through phases 1-3 to collect requirements, verify layouts, and produce complete technical specifications.

Does this spec generation approach work for both page modification and new screen creation?▼

Yes, this spec generation approach works for both page modification and new screen creation. It handles UI pages, components, and API integration tasks, applying iterative clarifications and layout confirmations to any screen creation or modification scenario.

Related Skills

Explore More Design & Creative Skills→
nopkhunnopkhun

Preview Mode Skill

Generate visual previews of code and UI changes before application.

Community
Intermediate
LeonardoTan19LeonardoTan19
2

frontend-page

Assemble frontend pages from design docs using shadcn components and generated API types.

Community
Advanced
iilleagliilleagl

design-workflow

Orchestrate a UI design workflow from requirements to a .pen file.

Community
Advanced
solace-illsolace-ill

team-ui

Coordinate UI team workflow across the UX pipeline from spec authoring to polish.

Community
Advanced