garura:define

Convert a raw feature idea or FEAT-ID into a scoped feature entry and validated intent epic.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill garura-define
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: garura:define
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/plays/define
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill garura-define

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts a raw feature idea into a fully scoped, traceable product feature entry and a validated intent epic, ready to advance the build planning workflow deterministically.

Core Features & Use Cases

  • Feature scoping from intent: Turns a free-text feature description or a FEAT-ID into a scoped feature row anchored to an existing GitHub issue.
  • Validation-gated epic creation: Generates or extends the capability-scoped intent epic and validates it before proceeding.
  • Structured HITL checkpoints: Surfaces catalog/placement and epic decisions to the user with Tether/Vanish/Orbit control, ensuring user review for critical decisions.
  • Evidence + memory hygiene: Writes catalog-match, constraint-fit, grounding, decision history, and delivery records into STM with clear separation from product LTM.

Quick Start

Run /define with a feature description or a FEAT-ID and follow the Tether/Vanish/Orbit prompts until the workflow ends with a scope ready for /prepare.

Frequently Asked Questions about garura:define

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

FAQPage Schema
How do I scope a raw feature idea into a validated intent epic for deterministic planning?

Feature scoping transforms a free-text idea or FEAT-ID into a scoped feature row anchored to a GitHub issue, classifies catalog buckets, checks constraints, and validates the intent epic before deterministic planning.

What is GitHub issue anchoring in the context of feature scoping?

GitHub issue anchoring links a raw feature idea to an existing GitHub issue, ensuring the generated intent epic and product feature entry remain traceable throughout the product-configuration workflow.

How do I include human-in-the-loop checkpoints during intent epic creation?

Human-in-the-loop checkpoints are integrated at placement and epic gates, surfacing catalog and epic decisions to the user via Tether/Vanish/Orbit controls to ensure critical choices are reviewed before proceeding.

Does feature scoping require YAML frontmatter metadata for validation?

Yes, YAML frontmatter metadata is required, along with config-resolved pathing and strict template-backed user surfaces, to successfully pass validation via validate-intent-epics before finishing.

Can I ground a feature entry in existing knowledge before generating an intent epic?

Yes, the workflow optionally grounds feature scoping in existing knowledge, writing catalog-match, constraint-fit, grounding, and decision history records into STM with clear separation from product LTM.

What happens if validate-intent-epics fails during the feature scoping workflow?

The workflow does not finish if validate-intent-epics fails, requiring the user to resolve validation errors in the scoped feature entry or intent epic before advancing to deterministic planning.