skills.rest
jokerman89
jokerman89COMMUNITY
Explore all skills by this author →
WebsiteGitHub

li-define

Generates requirements, acceptance criteria, and a concrete design before implementation.

Updated May 27, 2026
Search Tags:#workflow#design#planning#specification#requirements#acceptance criteria#github copilot
One-click install
npx skills add https://github.com/jokerman89/lintel --skill li-define-jokerman89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: li-define
Source: https://github.com/jokerman89/lintel/tree/main/.github/skills/li-define
Command: npx skills add https://github.com/jokerman89/lintel --skill li-define-jokerman89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into implementation without agreed requirements, leading to rework and misaligned expectations. This Skill turns a raw request into a defined specification with acceptance criteria and a concrete design before any code is written. ## Core Features & Use Cases - Requirements Definition: Converts a user request into structured requirements and acceptance criteria through the canonical Lintel define workflow. - Copilot Adapter Integration: Follows the Copilot adapter contract for tool mapping, authorization, and verification rules inside GitHub Copilot clients. - Use Case: A developer receives a vague feature request like "add a health endpoint" and uses this Skill to produce a specification with measurable acceptance criteria before asking the agent to implement it. ## Quick Start Ask your Copilot agent to define requirements and acceptance criteria for the feature you want to build before starting implementation.

Frequently Asked Questions about li-define

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

FAQPage Schema
How do I create acceptance criteria before implementing a feature?▼

Invoke the define workflow with your feature request, and it produces structured requirements, acceptance criteria, and a concrete design. The output is written to the working repository so the team can review it before implementation starts.

How does li-define work with GitHub Copilot?▼

It reads the Copilot adapter contract first, then executes the canonical define workflow using the adapter's tool mapping, authorization, and verification rules. This keeps behavior consistent across Copilot in VS Code, Copilot CLI, and cloud agents.

Can I use this workflow outside of GitHub Copilot?▼

The Skill itself is a Copilot adapter, but it delegates to a canonical define workflow in the repository. Other agent clients like Claude Code or Codex can follow the same canonical workflow through their own adapters.

When should I not use a define-before-build workflow?▼

Skip it for trivial changes like typo fixes or one-line configuration edits where writing requirements adds overhead without value. It is designed for requests where scope, design decisions, or acceptance criteria are genuinely ambiguous.

Related Skills

Explore More Software Engineering Skills→
amingclawdevamingclawdev
26

aming-claw-project-inbox

Capture raw user requirements and coordinate Capture and Confirmation modes for backlog promotion via governance endpoints.

Community
Intermediate
adhi-jpadhi-jp

vibe-planning

Convert explicit requirements into a formal implementation plan artifact.

Community
Advanced
docs-plusdocs-plus
88

grill-with-docs

Validates project plans against CONTEXT.md glossaries and ADRs to catch terminology mismatches.

Official
Intermediate
johan--johan--

implement

Implement features from GitHub Spec Kit specifications with acceptance criteria validation.

Community
Advanced