skills.rest
AIS-Commercial-Business-Unit
AIS-Commercial-Business-UnitOFFICIAL
Explore all skills by this author →
GitHub

ais.presales.synthesize

Synthesize client requirements from project context files into a structured "What We Heard" document.

Updated Jul 1, 2026
Search Tags:#requirements analysis#proposal generation#document synthesis#client engagement#pre-sales
One-click install
npx skills add https://github.com/AIS-Commercial-Business-Unit/CBU_Specify --skill ais-presales-synthesize
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ais.presales.synthesize
Source: https://github.com/AIS-Commercial-Business-Unit/CBU_Specify/tree/main/.cursor/skills/ais.presales.synthesize
Command: npx skills add https://github.com/AIS-Commercial-Business-Unit/CBU_Specify --skill ais-presales-synthesize

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of manually synthesizing client requirements from various sources into a coherent document, which is essential for proposal and SOW creation in pre-sales engagements.

Core Features & Use Cases

  • Context Ingestion: Reads and processes files from .project-context/ to understand client needs.
  • Synthesis: Organizes client requirements into a structured "What We Heard" document.
  • Use Case: For a pre-sales engagement, use this Skill to analyze client documents and produce a comprehensive "What We Heard" document that outlines the client's needs and desired outcomes.

Quick Start

Run the ais.presales.synthesize skill to analyze the project context and generate a "What We Heard" document.

Frequently Asked Questions about ais.presales.synthesize

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

FAQPage Schema
How do I synthesize client requirements from multiple documents into one file?▼

To synthesize client requirements, this skill reads files from the `.project-context/` directory and organizes them into a structured "What We Heard" document. It consolidates various client documents into a single coherent output for pre-sales analysis.

What is a "What We Heard" document in pre-sales client engagement?▼

A "What We Heard" document is a structured synthesis of client needs and desired outcomes extracted from project context files. It outlines client requirements to serve as the foundational analysis for proposal and SOW creation during pre-sales.

How do I generate a requirements analysis document from project context files?▼

Generate a requirements analysis document by placing client files in the `.project-context/` directory and running this skill. It processes the ingested context and outputs a comprehensive pre-sales requirements synthesis automatically.

Does this requirements synthesis skill work without external dependencies?▼

Yes, this requirements synthesis skill works without external dependencies. It operates independently using internal scripts and references to process project context files and generate the structured pre-sales document.

Can I use document synthesis for pre-sales proposal generation?▼

Yes, you can use document synthesis for pre-sales proposal generation. This skill analyzes client documents to produce a structured "What We Heard" file, which is specifically designed to streamline proposal and SOW creation.

Related Skills

Explore More Product & Management Skills→
arielybarakarielybarak

speckit-checklist

Generate custom checklists for requirements validation from user specifications.

Community
Advanced
larus-perituslarus-peritus

Requirements Engineering

Transform ideas into testable EARS-formatted requirements with validation templates.

Community
Advanced
venturecraneventurecrane

proposal-drafter

Generate Markdown proposal drafts from meeting transcripts and service offerings.

Official
Advanced
bbolek-apbbolek-ap

requirements-reviewer

Generate strategic client questions to identify gaps in requirements documents.

Community
Intermediate