Elicit
This walks you through building Allium specifications by asking the right questions at the right time. It helps you figure out scope boundaries first (what's in, what's out, what's a separate spec), then guides you to the right abstraction level through tests like "could this be implemented differently?" and "why does the stakeholder care?". The approach changes based on what you bring: if you're describing a process it starts with discovery, if you're naming entities it jumps to details, if you have existing code it points you to distillation. The real value is in teaching you to distinguish domain concerns from implementation details, which is harder than it sounds when you're in the middle of a conversation.
- skills.sh installs
- 2.7K
- GitHub stars
- 529
- last updated
- Aug 21, 2026
Install
$ npx -y skills add juxt/allium --skill elicit --agent claude-codeInstalls into .claude/skills of the current project.
Files
Elicitation
This skill guides you through building Allium specifications by conversation. The goal is to surface ambiguities and produce a specification that captures what the software does without prescribing implementation.
Scoping the specification
Before diving into details, establish what you are specifying. Not everything needs to be in one spec.
Questions to ask first
"What's the boundary of this specification?" A complete system? A single feature area? One service in a larger system? Be explicit about what is in and out of scope.
"Are there areas we should deliberately exclude?" Third-party integrations might be library specs. Legacy features might not be worth specifying. Some features might belong in separate specs.
"Is this a new system or does code already exist?" If code exists, you are doing distillation with elicitation. Existing code constrains what is realistic to specify.
Documenting scope decisions
Capture scope at the start of every spec:
-- allium: 3
-- interview-scheduling.allium
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageDetails
- Repository
- github.com/juxt/allium
- Categories
- DevOps & CI/CD, Sales & Marketing
- First seen
- May 16, 2026
More from juxt/allium
All 6Recommended
More DevOps & CI/CD
literature-searchlingzhi227/agent-research-skillsSearch academic literature using Semantic Scholar, arXiv, and OpenAlex APIs. Returns structured JSONL with title, authors, year, venue, abstract, citations, and2.7Kskills.sh installs
cloud-create-projectelastic/agent-skillsCreates Elastic Cloud Serverless projects (Elasticsearch, Observability, or Security) via the REST API, saves credentials to file, and bootstraps a scoped Elast2.7Kskills.sh installs
dt-obs-awsdynatrace/dynatrace-for-aiAWS cloud resource monitoring including EC2, RDS, Lambda, ECS/EKS, VPC networking, load balancers, S3, DynamoDB, SQS/SNS, and cost optimization. Use when analyz2.7Kskills.sh installs
checkjuliusbrussee/cavekitRead-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or buil2.7Kskills.sh installs
mojo-python-interopmodular/skillsAids in writing Mojo code that interoperates with Python using current syntax and conventions. Use this skill in addition to mojo-syntax when writing Mojo code 2.7Kskills.sh installs
domain-contextcustomware-ai/skillsProgressive Domain Crystallization (PDC) — a skill for building and maintaining a living domain knowledge base for any custom business application. Use this ski2.7Kskills.sh installs