garura:specify

Convert product ideas and project profiles into scoped intent epics with YAML constraints.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts a product idea plus a complete project profile into a fully scoped set of enriched intent epics and an aggregated quality profile, eliminating shallow or unvalidated specifications.

Core Features & Use Cases

  • Market-brained product specification: Produces a quantified market brief (TAM/SAM/SOM, competitive landscape, gaps, and risks) and uses it to drive scoped outcomes.
  • Capability selection with traced constraints: Selects 2–4 domains, configures capabilities using MVP narrowing, and records a complete cross-tree constraint_trace for auditability.
  • Intent epic generation with rigorous validation: Generates one intent epic per selected capability with quantified performance/security/accessibility/compliance constraints plus failure_conditions and expectations that downstream engineering can implement directly.

Quick Start

Run the specify play in Garura’s 5-stage SDLC by providing your product idea and a complete project profile, then Tether the market brief and checkpoint artifacts as prompted to produce market-brief.md, scope.yaml, and per-capability epic YAML files.

Frequently Asked Questions about garura:specify

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

FAQPage Schema
How do I turn a product idea into a scoped set of intent epics?▼

To turn a product idea into intent epics, provide a complete project profile to generate a quantified market brief, select 2-4 domains, configure capabilities using MVP narrowing, and generate one validated epic per capability.

What is an intent epic in product specification and scope planning?▼

An intent epic in product specification is a scoped outcome for a selected capability, containing quantified performance, security, accessibility, and compliance constraints plus failure conditions ready for direct engineering implementation.

How do I generate a market brief with TAM SAM SOM for enterprise delivery?▼

Generate a market brief with TAM SAM SOM by inputting your product idea and project profile, which produces a quantified brief including the competitive landscape, market gaps, and risks to drive scoped outcomes.

How to configure capabilities and domains using MVP narrowing for scope planning?▼

Configure capabilities and domains using MVP narrowing by selecting 2-4 domains, applying minimum viable product constraints to narrow each capability, and recording a complete cross-tree constraint trace for full auditability.

Does product specification require YAML frontmatter contracts and checkpoint gates?▼

Yes, rigorous product specification requires YAML frontmatter contracts, decision-manifest surfacing discipline, quantified constraint validation, and checkpoint-gated progression to satisfy structural safety requirements across all downstream artifacts.

When should I not use automated intent epic generation for scope planning?▼

Avoid automated intent epic generation when lacking a complete project profile, since shallow or unvalidated specifications are eliminated by requiring quantified market intelligence and human-gated checkpoints before producing scope.yaml and epic artifacts.