Guide discovery sessions to distill requirements into an Allium specification.
npx skills add https://github.com/ravenoak/oh-my-stigmergy --skill elicit-ravenoak
Please help me install this Agent Skill. Skill: elicit Source: https://github.com/ravenoak/oh-my-stigmergy/tree/main/.agents/skills/elicit Command: npx skills add https://github.com/ravenoak/oh-my-stigmergy --skill elicit-ravenoak
This skill guides you through structured discovery sessions to build Allium specifications by conversation, enabling teams to surface ambiguities and shape a specification from user input.
Describe your system at a high level, then walk me through the main flow to identify actors, entities, and outcomes.
High-intent search queries and answers about installing and using this skill.
Requirements elicitation for a formal specification involves guiding discovery sessions to capture actors, entities, and boundaries. This skill structures that process by distilling user input into a walking skeleton and surface definitions to drive alignment.
Scope definition and edge-case elicitation are handled by framing happy-path flows and checking assumptions against user input. This approach surfaces alternative paths and gaps, documenting them as unresolved questions for stakeholders.
Process discovery outputs like transition graphs and actor roles are captured by formalizing client workshop conversations. You describe the system at a high level, then walk through the main flow to identify exposed surfaces and outcomes.
Structured discovery can frame happy paths and surface ambiguities in an incomplete specification. It provides open questions and assumption checking to highlight unresolved issues, ensuring a complete spec is defined before hand-off.
Requirements elicitation does not require a complete spec to start; it is designed for scenarios where a specification is not yet defined. You can build a formal Allium spec from scratch by starting with a high-level system description.
Structured process discovery should not be used when a complete and formal Allium specification is already defined. It is specifically built for early discovery sessions and client workshops where scope, actors, and boundaries remain ambiguous.
kvcopCapture raw ideas into structured draft notes with TL;DR and source tracking.
scottopellCompare .allium specifications with implementation code to detect divergences.
g-bastianelliGuide users through creating and validating detailed project specifications.
hiddink-aiAnalyze natural language feature requests against project codebases and generate JSON issue specifications.
