configure-capabilities

Generate scope.yaml and decision-manifest.yaml from project profiles and domain catalogs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts a project profile and a frozen domain knowledge snapshot into a deterministic, auditable capability scope, ensuring that every inclusion, exclusion, and constraint decision is surfaced instead of silently omitted.

Core Features & Use Cases

  • Deterministic capability selection: Builds a scope.yaml with selected capabilities, rejected capabilities with reasons, and a complete constraint trace.
  • Cross-tree constraint auditing: Walks every cross-tree constraint (fired and not-applicable) and records how each affected scope-shaping decisions.
  • Within-domain coverage analysis: Surfaces non-blocking gaps for user review when the domain feature catalog does not fully cover the brief’s implied needs.
  • Optional capability checkpointing: Returns optional capabilities for a user selection checkpoint and merges prior user-approved selections when provided.
  • Decision and grounding traceability: Emits a decision-manifest.yaml and appends grounding questions to user-provided grounding-questions for durable review across runs.

Quick Start

Ask the product-keeper agent to run configure-capabilities using your project profile and the prepared product research folder to generate .garura/product/scope/scope.yaml and decision-manifest.yaml.

Frequently Asked Questions about configure-capabilities

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

FAQPage Schema
How do I generate a deterministic capability scope from a product brief?

To generate a deterministic capability scope, you apply project-profile rules to a frozen product research catalog, translating intent into selected and rejected capabilities while writing scope.yaml.

What is cross-tree constraint auditing in feature selection?

Cross-tree constraint auditing walks every constraint during capability selection, recording how each fired or not-applicable rule shapes the scope to prevent silent omissions in domain feature processing.

How do I handle non-blocking coverage gaps in domain taxonomy during scoping?

Perform within-domain coverage analysis to surface non-blocking gaps when the domain taxonomy lacks full coverage, returning optional capabilities as a checkpoint for user review.

Do I need a prior MVP recommendation to start capability selection?

Yes, capability selection requires a pre-existing MVP recommendation as input to translate it alongside cross-tree constraints and domain feature markdowns into selected and rejected capabilities.

Can I merge previously approved optional capabilities into a new scope.yaml?

Yes, the capability selection process merges prior user-approved optional capabilities when provided, returning remaining optional capabilities for a new checkpoint without overwriting prior grounding question answers.

What outputs does constraint auditing produce for feature scope decisions?

Constraint auditing produces a scope.yaml file with selected and rejected capabilities, a decision-manifest.yaml detailing the complete constraint trace, and appends grounding questions for durable review.