define

Convert vague feature ideas into structured GitHub issue outlines.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/LoanLemur/skills --skill define-loanlemur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: define
Source: https://github.com/LoanLemur/skills/tree/main/define
Command: npx skills add https://github.com/LoanLemur/skills --skill define-loanlemur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts vague feature requests into a structured, actionable GitHub issue that defines WHAT to build and WHY, enabling downstream teams to design and implement with shared clarity.

Core Features & Use Cases

  • Structured issue generation: captures problem statement, goals, constraints, and success criteria.
  • Phase-aligned planning: appends an implementation plan and decision log to the issue.
  • Guided scoping: prompts for scope assessment and asks clarifying questions before proceeding.

Quick Start

Provide a concise feature idea, and this skill outputs a ready-to-file GitHub issue outlining WHAT, WHY, and an initial plan.

Frequently Asked Questions about define

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

FAQPage Schema
How do I convert a vague feature idea into a structured GitHub issue?

To convert a vague feature idea into a structured GitHub issue, provide the concept to this skill. It outputs a ready-to-file outline capturing the problem statement, goals, constraints, and success criteria.

What is the best way to align stakeholders on new feature scope?

The best way to align stakeholders on new feature scope is using guided scoping. This process prompts for scope assessment and asks clarifying questions before proceeding to ensure cross-functional clarity on what to build and why.

How do I create an implementation plan for cross-functional product management proposals?

To create an implementation plan for cross-functional product management proposals, this skill generates a Phase 1-7 artifact plan appended directly to the issue, enabling structured downstream design and review workflows.

Can I use this to generate frontmatter metadata for downstream design workflows?

Yes, you can use this to generate frontmatter metadata for downstream design workflows. The output includes name, description, argument-hint, and user-invocable fields required for governance and review phases.

Does this work for feature requests that touch multiple files or actors?

Yes, this works specifically for feature requests that touch multiple files or actors. It applies to proposals describing new functionality or scope, enabling a structured cross-functional design workflow.