structured-elicitation

Interview users across five layers and generate agent configuration artifacts.

4|1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/m2ai-portfolio/m2ai-skills-pack --skill structured-elicitation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: structured-elicitation
Source: https://github.com/m2ai-portfolio/m2ai-skills-pack/tree/main/skills/structured-elicitation
Command: npx skills add https://github.com/m2ai-portfolio/m2ai-skills-pack --skill structured-elicitation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides a structured interview to capture operating rhythms, recurring decisions, dependencies, institutional knowledge, and friction, then generates agent-config artifacts for downstream consumption.

Core Features & Use Cases

  • Five-layer elicitation interviews with checkpoints to verify captured data at each stage.
  • Artifact generation of SOUL.md, USER.md, HEARTBEAT.md, operating-model.json, and schedule-recommendations.json.
  • Enables rapid onboarding of new agents or client teams by translating tacit work patterns into machine-readable configurations.

Quick Start

Initiate a five-layer elicitation interview with a user and review the generated artifacts.

Frequently Asked Questions about structured-elicitation

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

FAQPage Schema
How do I extract expert knowledge to build an agent configuration?

To extract expert knowledge for an agent configuration, conduct a structured user interview across five layers to capture operating rhythms, recurring decisions, dependencies, institutional knowledge, and friction, then generate agent-ready artifacts for downstream consumption.

What is structured elicitation for agent onboarding?

Structured elicitation for agent onboarding is a five-layer interview process with checkpoints that translates tacit work patterns into machine-readable configurations, enabling rapid onboarding of new agents or client teams by capturing operating rhythms and institutional knowledge.

How do I create an operating model from user interviews?

You can create an operating model from user interviews by guiding users through a structured five-layer elicitation to verify captured data at each checkpoint, then producing an operating-model.json file that defines recurring decisions and dependencies.

What artifacts are generated when extracting agent configurations?

Extracting agent configurations generates multiple machine-readable artifacts including SOUL.md, USER.md, HEARTBEAT.md, operating-model.json, and schedule-recommendations.json to define agent personas, operating rhythms, and recurring decisions.

Can I refine an existing agent persona using elicitation interviews?

Yes, you can refine an existing agent configuration by conducting a structured elicitation interview to capture updated operating rhythms, dependencies, and institutional knowledge, then regenerating agent-ready artifacts to align the persona with current workflows.

What is the best way to document institutional knowledge for downstream agents?

The best way to document institutional knowledge for downstream agents is to use a five-layer interview with verification checkpoints, ensuring tacit work patterns and dependencies are accurately translated into machine-readable artifacts like USER.md.