skills.rest
xoai
xoaiCOMMUNITY
Explore all skills by this author →
𝕏@xoaiGitHub

quick-elicit

Guides a three-round questioning process to elicit feature specifications with codebase-scan context.

25|7|Updated Mar 16, 2026
Search Tags:#planning#specification#requirements#user stories#elicitation
One-click install
npx skills add https://github.com/xoai/sage --skill quick-elicit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quick-elicit
Source: https://github.com/xoai/sage/tree/main/core/capabilities/elicitation/quick-elicit
Command: npx skills add https://github.com/xoai/sage --skill quick-elicit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of gathering requirements for new features or changes, preventing vague specifications and ensuring clarity before development begins.

Core Features & Use Cases

  • Guided Questioning: Engages users through three focused rounds of questions to define intent, boundaries, and acceptance criteria.
  • Contextual Awareness: Leverages codebase-scan to tailor questions based on the existing project structure.
  • Use Case: When a user says "I want to add a new user profile page," this Skill will ask targeted questions to quickly define what the page should do, what it shouldn't do, and how to test it, resulting in a clear specification.

Quick Start

Use the quick-elicit skill to define the requirements for adding a new user profile page.

Frequently Asked Questions about quick-elicit

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

FAQPage Schema
How do I elicit detailed feature specifications before development begins?▼

You can elicit feature specifications through a structured three-round questioning process that defines intent, boundaries, and acceptance criteria, preventing vague requirements during software planning.

What is the best way to write user stories for an existing codebase?▼

Writing user stories for an existing codebase is streamlined by leveraging codebase scanning to infer existing context, tailoring targeted questions to produce clear specifications based on your project structure.

How do I define acceptance criteria and boundaries for a new feature?▼

Defining acceptance criteria and boundaries is achieved through focused questioning rounds that clarify exactly what a feature should do, what it should not do, and how it should be tested.

Do I need to scan my codebase to generate accurate requirements?▼

Scanning the codebase is required to infer existing context and tailor questions for efficient elicitation, ensuring the generated requirements align closely with your current project structure.

What are the limitations of automated requirements gathering?▼

Limitations of automated requirements gathering include relying on a fixed three-round questioning structure, meaning highly complex or ambiguous project intents may still require manual refinement after the elicitation process.

Related Skills

Explore More Product & Management Skills→
telum-aitelum-ai
2

project-import

Create a Speck project structure with a skeleton project.md file.

Official
Basic
atlassianatlassian
949

spec-to-backlog

Convert Confluence specification documents into structured Jira backlogs with Epics and linked tickets.

Official
Intermediate
BaraArdiwinataBaraArdiwinata

planning-and-task-breakdown

Decompose feature specifications into implementable tasks with dependency tracking and acceptance criteria.

Community
Advanced
Serg28Serg28

feature-forge

Facilitate requirements workshops and generate EARS-format specification documents.

Community
Intermediate