elicit

Conduct structured four-phase interviews to capture actors, goals, and exceptions for documentation.

Updated May 6, 2026
One-click install
npx skills add https://github.com/SuSuSleep/scaffold --skill elicit-sususleep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elicit
Source: https://github.com/SuSuSleep/scaffold/tree/main/skills/elicit
Command: npx skills add https://github.com/SuSuSleep/scaffold --skill elicit-sususleep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill bridges the gap between raw technical implementation and meaningful product documentation by capturing the human context that code cannot express.

Core Features & Use Cases

  • Structured Interviewing: Guides the user through a 4-phase process to define actors, goals, flows, and exception handling.
  • Contextual Documentation: Automatically populates TBD placeholders in module use-case and user-story files based on user input.
  • Use Case: After an AI agent scans a new module, use this skill to interview the developer or product owner to define who uses the feature, why it exists, and how users experience errors.

Quick Start

Trigger the elicit skill to fill in the business context and TBD placeholders for the authentication module.

Frequently Asked Questions about elicit

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

FAQPage Schema
How do I add business context to technical documentation drafts?

To add business context to technical documentation, you can use a structured interview process to capture actors, goals, and exception handling, automatically populating TBD placeholders in user-story files with human-centric details.

What is the best way to generate user stories from raw technical modules?

Generating user stories from technical modules involves mapping code-generated drafts to actor and goal frameworks. A structured interview extracts the human context code cannot express, bridging raw implementation and product documentation.

How does a structured interview help fill in software documentation gaps?

A structured interview helps fill software documentation gaps by guiding users through phases to define actors, goals, flows, and exception handling, automatically populating TBD placeholders in module use-case files.

Can I use this to document exception handling for new software modules?

Yes, you can document exception handling for new software modules by conducting a structured interview. It captures how users experience errors and maps technical interfaces to user-facing stories.

Do I need existing code-generated drafts to map user-facing stories?

Yes, you need existing code-generated drafts to map user-facing stories. The process populates TBD placeholders in module use-case files by applying actor, goal, and exception framing to the existing technical drafts.