skills.rest
Bullish-Design
Bullish-DesignCOMMUNITY
Explore all skills by this author →
GitHub

elicit

Guide structured elicitation to convert conversations into Allium specifications.

1|Updated Mar 11, 2026
Search Tags:#scoping#specification#requirements#discovery#stakeholders#allium#elicit
One-click install
npx skills add https://github.com/Bullish-Design/remora-v2 --skill elicit-bullish-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: elicit
Source: https://github.com/Bullish-Design/remora-v2/tree/main/.agents/skills/allium/skills/elicit
Command: npx skills add https://github.com/Bullish-Design/remora-v2 --skill elicit-bullish-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill guides teams through structured elicitation to convert conversations and stakeholder input into a concrete Allium specification, reducing ambiguity and missed requirements.

Core Features & Use Cases

  • Structured interview flow: Scope definition, happy path, edge cases, and refinement to produce a complete spec.
  • Open-question capture and decision logging to surface ambiguities and decisions.
  • Library-spec boundary awareness to distinguish application vs library specs and ensure reusable patterns are documented.

Quick Start

Start an elicitation session by outlining scope with stakeholders and guiding the interview through scope, happy path, and edge cases to draft the initial Allium spec.

Frequently Asked Questions about elicit

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

FAQPage Schema
How do I turn stakeholder conversations into a specification?▼

To turn stakeholder conversations into a specification, use structured elicitation to guide teams through scope definition, happy path tracing, and edge-case handling. This process captures open questions and decisions to produce a concrete, shareable Allium spec artifact.

What is structured requirements elicitation for feature scoping?▼

Structured requirements elicitation for feature scoping is a phase-based workflow that extracts scope definitions from verbal descriptions or existing code. It surfaces ambiguities by logging open questions and decisions to draft a complete specification.

How do I capture edge cases and open questions during requirements discovery?▼

You can capture edge cases and open questions during requirements discovery by applying a structured interview flow. This workflow systematically traces the happy path, identifies boundary conditions, and logs unresolved ambiguities into a shareable spec artifact.

Does this work for defining both application and library specifications?▼

Yes, it supports defining both application and library specifications. The workflow enforces library-spec boundary awareness to distinguish between the two, ensuring reusable patterns are documented correctly within the final Allium specification.

What is the best way to document scope decisions from a discovery session?▼

The best way to document scope decisions from a discovery session is to use a guided elicitation workflow that enforces phase-based refinement. It records open questions and stakeholder decisions directly into a shareable Allium spec artifact.

Related Skills

Explore More Product & Management Skills→
twkevinzhangtwkevinzhang
7

business-analyst

Translate vague task descriptions into precise, testable specifications with acceptance criteria.

Community
Advanced
juxtjuxt
10

weed

Resolve divergences between Allium behavioral specification files and implementation code.

Official
Advanced
mahg-esmahg-es
3

unit-test

Generate unit tests for functions, methods, and classes using the project's test framework.

Official
Intermediate
xsw632xsw632
2

requirement-parser

Converts natural language hardware descriptions into Chime-compliant JSON specifications with validation and workspace setup.

Community
Intermediate