skill-elicitation

Extract tacit operator knowledge into reviewable workflow artifacts.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/rbtkhn/grace-mar --skill skill-elicitation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-elicitation
Source: https://github.com/rbtkhn/grace-mar/tree/main/.cursor/skills/skill-elicitation
Command: npx skills add https://github.com/rbtkhn/grace-mar --skill skill-elicitation

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This Skill helps operators extract tacit workflow knowledge that is difficult to document, turning personal operating patterns into explicit and reviewable WORK artifacts without treating them as permanent identity records.

## Core Features & Use Cases

  • Structured Knowledge Extraction: Guides bounded interviews across rhythms, decisions, dependencies, friction, and thresholds to capture operational context.
  • Review-First Workflow: Creates checkpoint summaries and requires confirmation before writing captured information into working files.
  • Use Case: An operator changing roles can use this Skill to document their actual working patterns and provide better context for downstream planning and execution workflows.

### Quick Start Use the skill-elicitation skill to run a bounded elicitation pass for capturing my workflow patterns into reviewable WORK artifacts.

Frequently Asked Questions about skill-elicitation

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

FAQPage Schema
How do I document tacit workflow knowledge from operators before a role transition?

To document tacit workflow knowledge for role transitions, run bounded interviews across rhythms, decisions, dependencies, friction, and thresholds to capture operational context into structured, reviewable artifacts.

What is the best way to capture operator knowledge without losing context?

The best way to capture operator knowledge without losing context is using review-first elicitation flows that separate working notes from canonical records and require operator approval before updates.

Can I use structured interviews to extract working patterns into reviewable artifacts?

Yes, you can use structured interviews to extract working patterns by guiding bounded elicitation passes that produce checkpoint summaries for operator confirmation before writing to working files.

How does an elicitation workflow separate working notes from canonical records?

An elicitation workflow separates working notes from canonical records by creating checkpoint summaries that require explicit operator confirmation before any captured information updates canonical workflow artifacts.

Does workflow documentation require operator approval before updating canonical files?

Yes, workflow documentation requires operator approval before updating canonical files, ensuring review-first flows preserve operator confirmation and separate working notes from permanent records.

When do I need to run a bounded elicitation pass for context capture?

You need to run a bounded elicitation pass for context capture during workflow documentation, operational interviews, role transitions, and context grounding for downstream planning or execution tasks.