skills.rest
scottopell
scottopellCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

elicit

Guide stakeholder conversations to draft Allium specification artifacts.

1|Updated May 22, 2013
Search Tags:#documentation#specification#requirements#elicitation#stakeholders#allium
One-click install
npx skills add https://github.com/scottopell/dotfiles --skill elicit-scottopell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: elicit
Source: https://github.com/scottopell/dotfiles/tree/main/home-dir-configs/claude/skills/allium/skills/elicit
Command: npx skills add https://github.com/scottopell/dotfiles --skill elicit-scottopell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Elicit helps teams define clear Allium specifications by guiding structured conversations that surface ambiguities and align stakeholders.

Core Features & Use Cases

  • Guided interviews to capture scope and boundary decisions.
  • Documentation of decisions and open questions in a consistent format for review.
  • Distillation of stakeholder input into a testable Allium spec artifact.

Quick Start

Initiate a guided elicitation with a stakeholder to draft an Allium specification for a new feature.

Frequently Asked Questions about elicit

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

FAQPage Schema
How do I elicit requirements from stakeholders to create a formal specification?▼

You elicit requirements by initiating guided conversations that surface ambiguities and capture scope boundaries. This structured interviewing process documents stakeholder decisions and distills their input into a testable formal specification artifact.

What is the best way to document open questions and decisions during requirements gathering?▼

The best way to document open questions is through a phase-driven workflow that captures stakeholder input in a consistent format. This approach aligns understanding and produces ready-for-review artifacts detailing decisions and unresolved queries.

How do I define scope boundaries for a new feature specification?▼

You define scope boundaries by conducting guided interviews with stakeholders to capture boundary decisions. This structured elicitation process surfaces ambiguities early and distills agreed scope definitions into a formal specification.

Can I use guided conversation to align stakeholder understanding before writing a spec?▼

Yes, you can use guided conversation to align stakeholder understanding before writing a spec. This elicitation process surfaces hidden ambiguities, documents decisions, and ensures all stakeholders share a unified understanding of the requirements.

Does generating an Allium specification require predefined requirements documentation?▼

Generating an Allium specification does not require predefined requirements documentation. The process builds the specification through guided elicitation, actively interviewing stakeholders to distill input and capture decisions directly into the spec artifact.

Related Skills

Explore More Software Engineering Skills→
hb9397hb9397

design-doc

Generate structured design documents and PRDs from raw project inputs.

Community
Advanced
Bullish-DesignBullish-Design
1

elicit

Guide structured elicitation to convert conversations into Allium specifications.

Community
Advanced
skeeper75skeeper75

moai-docs-generation

Generate technical documentation from code using Sphinx, MkDocs, TypeDoc, and Nextra.

Community
Advanced
ashtonianashtonian
2

requirements

Guide stakeholder sessions to document software requirements and draft specifications.

Community
Advanced