skills.rest
mattjefferson
mattjeffersonCOMMUNITY
Explore all skills by this author →
Website𝕏@mjeffersonGitHub

he-spec

Convert fuzzy requests into initiative specifications with measurable success criteria.

4|1|Updated Feb 14, 2026
Search Tags:#specification#requirements#product management#success criteria#scope#initiative definition
One-click install
npx skills add https://github.com/mattjefferson/harness-engineering --skill he-spec-mattjefferson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: he-spec
Source: https://github.com/mattjefferson/harness-engineering/tree/main/skills/he-spec
Command: npx skills add https://github.com/mattjefferson/harness-engineering --skill he-spec-mattjefferson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms vague ideas or requests into concrete, actionable specifications with clear requirements and success criteria, ensuring alignment before development begins.

Core Features & Use Cases

  • Initiative Formalization: Converts fuzzy requests into structured initiative specs.
  • Requirement Definition: Defines measurable success criteria and scope.
  • Use Case: When a product manager has a new feature idea, they can use he-spec to flesh out the requirements, define what "done" looks like, and identify any initial research or spike needs before handing it off to engineering.

Quick Start

Use the he-spec skill to create a spec for adding user authentication to the platform.

Frequently Asked Questions about he-spec

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

FAQPage Schema
How do I convert a vague product idea into a concrete initiative specification?▼

To create an initiative specification, you formalize fuzzy requests into structured specs using a single slug and measurable success criteria. This defines scope and identifies next steps like research or spikes before development begins.

What is the best way to define measurable success criteria for new feature requirements?▼

Defining success criteria requires translating abstract product requirements into measurable outcomes within a formal specification. This ensures clear alignment on what constitutes done before engineering work starts.

When do I need to formalize product management scope before handing off to engineering?▼

You need to formalize scope at the start of any non-trivial work. Defining requirements and measurable success criteria ensures engineering teams have clear boundaries and expectations before development begins.

Can I map external documents and integrate artifacts into my requirement specs?▼

Yes, specification formalization supports external document mapping and artifact integration. This allows you to connect your initiative specs with existing references and external materials during requirement definition.

How do I identify if a product initiative requires initial research or spike needs?▼

By formalizing the initiative into a concrete specification, you clarify requirements and scope, which highlights knowledge gaps. This process explicitly identifies necessary next steps like initial research or technical spikes.

Related Skills

Explore More Product & Management Skills→
psd401psd401
2

product-manager

Translate product ideas into structured PRDs and user stories.

Official
Advanced
zeronx798zeronx798

darwinian-evolver

Evolve prompts, regex patterns, SQL queries, and code snippets via LLM-driven fitness loops.

Community
Advanced
jongwonyjongwony
4

activity

Queries Linear MCP and organizes activity into hourly Markdown and JSON reports.

Community
Advanced
TrogonStackTrogonStack
10

prd-personas

Draft user personas with roles, jobs-to-be-done, and success criteria for product requirement documents.

Official
Intermediate