skills.rest
bianhaifeng789-hue
bianhaifeng789-hueCOMMUNITY
Explore all skills by this author →
GitHub

harness-planner

Expand 1-4 sentence briefs into a structured spec.md with required sections.

Updated Apr 14, 2026
Search Tags:#roadmap#user-stories#planner#design-direction#product-spec#technical-stack
One-click install
npx skills add https://github.com/bianhaifeng789-hue/openclaw-config --skill harness-planner-bianhaifeng789-hue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-planner
Source: https://github.com/bianhaifeng789-hue/openclaw-config/tree/main/skills/harness-planner
Command: npx skills add https://github.com/bianhaifeng789-hue/openclaw-config --skill harness-planner-bianhaifeng789-hue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brief product requests are often under-specified, requiring manual interpretation to produce a usable specification document.

Core Features & Use Cases

  • Automatically expand 1-4 sentence briefs into a full spec.md with sections for Overview, Features, User Stories, Technical Stack, and Design Direction.
  • Include placeholders for design direction, tech choices, and evaluation criteria to guide subsequent work.
  • Use cases include early product ideas, feature requests, and roadmap planning.

Quick Start

Install and run planner with a short brief to generate spec.md in the workspace.

Frequently Asked Questions about harness-planner

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

FAQPage Schema
How do I turn a brief product idea into a full specification document?▼

To expand brief product needs into a specification document, input a 1-4 sentence brief to automatically generate a structured spec.md. The resulting document includes sections for Overview, Features, User Stories, Technical Stack, and Design Direction to guide development teams.

What sections are needed in a product spec for early-stage roadmap planning?▼

A product spec for roadmap planning needs Overview, Features, User Stories, Technical Stack, and Design Direction sections. It should also include placeholders for tech choices and evaluation criteria to guide subsequent implementation work.

Can I generate user stories directly from a short feature request?▼

You can generate user stories from a short feature request by processing a 1-4 sentence brief. The brief is automatically expanded into a structured specification that explicitly includes a dedicated User Stories section alongside features and technical stack details.

Does this product planning approach work for early-stage ideas with only a few sentences?▼

This product planning approach is designed for early-stage ideas with only 1-4 sentences. It takes under-specified brief requests and outputs a comprehensive specification document without requiring manual interpretation or additional prerequisite setup.

What is the best way to structure technical stack and design direction for a new feature?▼

The best way to structure technical stack and design direction is to use dedicated sections within a spec.md file. This approach includes specific placeholders for tech choices and design direction to guide subsequent development team implementation.

Related Skills

Explore More Product & Management Skills→
walker-hzxwalker-hzx

requirement-understanding

Convert ambiguous user input into a one-sentence goal with clarifying questions.

Community
Basic
notquenotque
415

spec-writer

Create a SPEC.md with user stories, acceptance criteria, and risks.

Community
Advanced
DergaczDergacz

10x-roadmap

Convert Product Requirements Documents into prioritized development roadmaps with milestones.

Community
Advanced
Lands-1203Lands-1203
40

f2s-doc-arch

Generate project architecture description drafts from documentation or code.

Community
Intermediate