analyste-besoin

Transform ambiguous client requests into a structured cahier-des-charges.md document.

Updated Mar 3, 2026

Search Tags:#templates #specification #requirements #analysis #stakeholder-interviews #cahier-des-charges

Ready to run

npx skills add https://github.com/BENYEKHLEF-Anouar/SoliQuiz --skill analyste-besoin-benyekhlef-anouar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyste-besoin
Source: https://github.com/BENYEKHLEF-Anouar/SoliQuiz/tree/main/Maquettage/.agent/skills/analyste-besoin
Command: npx skills add https://github.com/BENYEKHLEF-Anouar/SoliQuiz --skill analyste-besoin-benyekhlef-anouar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts ambiguous or incomplete client requests into a clear, structured cahier des charges so stakeholders and developers share the same scope and expectations.

Core Features & Use Cases

Demand Analysis: Determine whether a full requirements document is needed for new pages, projects, or major refactors versus minor modifications.
Document Generation: Use the provided analysis capability and the cahier-des-charges template to create or update a requirements file (1.analyse-besoin/cahier-des-charges.md).
Governance & Constraints: Enforce non-technical framing (no architecture decisions), require developer validation before finalization, and propose updates when a complete refactor is requested.
Use Case: A trainer requests a new learning module; the skill extracts objectives, target persona, required content, and deadlines, then produces a concise cahier des charges for review.

Quick Start

Ask analyste-besoin to analyze the client conversation and generate or update a cahier des charges using the template while avoiding technical architecture details.

Frequently Asked Questions about analyste-besoin

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

FAQPage Schema

How do I turn vague client requests into a structured requirements document?▼

To turn vague client requests into a structured requirements document, you analyze stakeholder conversations to extract objectives, personas, and functional needs, then populate a cahier-des-charges template. This ensures stakeholders and developers share the same scope and expectations.

What is a cahier des charges and when do I need one for a new project?▼

A cahier des charges is a structured requirements document defining project scope and expectations. You need one for new pages, new projects, or major refactors to align stakeholders and developers, whereas minor modifications typically do not require a full document.

How to extract functional needs and personas from stakeholder interviews?▼

To extract functional needs and personas from stakeholder interviews, apply a structured requirement analysis to the client conversation. Identify the target audience, required content, and deadlines, then map these elements directly into the specification template.

Does the requirements analysis process include technical architecture decisions?▼

No, the requirements analysis process explicitly avoids technical architecture decisions to maintain a non-technical framing. It focuses solely on product discovery and UX needs, requiring developer validation before the specification is finalized.

Can I use this specification approach for minor page modifications?▼

You can use this specification approach for minor page modifications, but it first analyzes the demand to determine if a full requirements document is actually needed. It proposes updating the existing file only when a complete refactor is requested.