skills.rest
matteotitta
matteotittaCOMMUNITY
Explore all skills by this author →
Website𝕏@matteo_tittaGitHub

consultation

Transform ambiguous project requests into structured specifications via adversarial review.

29|12|Updated Mar 30, 2026
Search Tags:#planning#scoping#elicitation#consultation#gtm#spec-writing
One-click install
npx skills add https://github.com/matteotitta/genesys-skills --skill consultation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: consultation
Source: https://github.com/matteotitta/genesys-skills/tree/main/skills/primitives/clients/consultation
Command: npx skills add https://github.com/matteotitta/genesys-skills --skill consultation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the friction of turning ambiguous client or internal requests into actionable, high-quality project specifications, preventing scope creep and misalignment before execution begins.

Core Features & Use Cases

  • Interactive Elicitation: Uses a structured questioning loop to map knowns and unknowns, ensuring no critical details are missed.
  • Adversarial Review: Integrates automated premortem checks to identify potential failure modes in the proposed plan.
  • Standardized Handoff: Produces a clean, delimited prompt that allows execution sessions to start immediately without re-litigating decisions.

Quick Start

Invoke the consultation skill by typing /consultation followed by your vague project request to begin the scoping process.

Frequently Asked Questions about consultation

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

FAQPage Schema
How do I write project specifications from vague client requests?▼

Project specifications from vague requests are written by running an interactive elicitation loop that maps knowns and unknowns, ensuring ambiguous project asks become structured, actionable specs.

What is premortem analysis in project scoping?▼

Premortem analysis in project scoping is an adversarial review process that identifies potential failure modes in a proposed plan, ensuring high-fidelity project handoff documentation and preventing scope creep.

How do I prevent scope creep during B2B GTM planning?▼

Prevent scope creep during B2B GTM planning by mapping knowns and unknowns through a four-quadrant board, transforming ambiguous requests into structured specifications before execution begins.

Can I use interactive elicitation to map project unknowns?▼

Interactive elicitation maps project unknowns through a structured questioning loop, routing the gathered plans through adversarial premortem checks to guarantee no critical details are missed.

What is the best way to turn ambiguous asks into handoff documentation?▼

The best way to turn ambiguous asks into handoff documentation is using an interactive elicitation loop that produces a clean, delimited prompt for execution sessions to start immediately.

Does this project scoping approach support standardized prompt handoff?▼

This project scoping approach supports standardized prompt handoff by producing a clean, delimited prompt that allows execution sessions to start immediately without re-litigating prior decisions.

Related Skills

Explore More Marketing & Sales Skills→
apexradiusapexradius

client

Manage client project lifecycles from intake through handoff.

Official
Advanced
TheCraigHewittTheCraigHewitt
7.3k

analytics-tracking

Design and implement GA4 and GTM analytics tracking with event taxonomy and privacy compliance.

Community
Intermediate
jsagirjsagir
2

map-unknowns

Map known, unknown, and unknowable project elements using the Knowns and Unknowns Matrix Framework.

Community
Intermediate
srobinsonsrobinson

create-spec

Creates a structured SPEC.md template through interactive one-question-at-a-time elicitation.

Community
Intermediate