projetix

Generate CADRE notes and functional specifications from business briefs.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dduquenne/unanima-platform --skill projetix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: projetix
Source: https://github.com/dduquenne/unanima-platform/tree/main/.claude/skills/projetix
Command: npx skills add https://github.com/dduquenne/unanima-platform --skill projetix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Projetix automates the creation of structured project notes and functional specifications from client briefs, reducing ambiguity and speeding up proposal and development alignment.

Core Features & Use Cases

  • Note de cadrage creation: converts discovery input into a scoped, prioritized project frame (MoSCoW, actors, risks, value).
  • Functional specifications generation: produces Epic/Feature/User Story structure with acceptance criteria (BDD/Gherkin) and a Definition of Done.
  • Reuse and alignment: ensures vocabulary matches client language and ties deliverables to business value.
  • Use Case: When given a client brief, it outputs a CADRE document and the initial backlog of US with DoD, ready for review.

Quick Start

Provide the client brief and objectives, and Projetix will generate a structured CADRE note and a complete set of functional specifications.

Frequently Asked Questions about projetix

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

FAQPage Schema
How do I generate functional specifications from a business brief?

To generate functional specifications from a business brief, you provide the client objectives and Projetix outputs a structured CADRE document with an Epic, Feature, and User Story backlog. This includes BDD/Gherkin acceptance criteria and a Definition of Done.

What is a CADRE note and when do I need it for project scoping?

A CADRE note is a scoped, prioritized project frame used for project scoping when you need to define MoSCoW priorities, actors, risks, and business value. You need it to reduce ambiguity and align development proposals before writing functional specifications.

How do I write user stories with acceptance criteria and a Definition of Done?

To write user stories with acceptance criteria, the Skill enforces a structured template generating Epic/Feature/User Story hierarchies. It automatically applies BDD/Gherkin conventions for acceptance criteria and includes a standardized Definition of Done.

Can I use MoSCoW prioritization to define scope for client proposals?

Yes, you can use MoSCoW prioritization to define scope for client proposals. The Skill applies the MoSCoW method directly within the CADRE note generation to ensure deliverables are tied to business value and project scope is clearly prioritized.

Does this approach work for creating BDD Gherkin acceptance criteria from discovery notes?

Yes, this approach works for creating BDD Gherkin acceptance criteria from discovery notes. It takes discovery inputs and client vocabulary to generate functional specifications that enforce DoD and BDD conventions directly within the user story structure.

What is the best way to structure an initial backlog from a client brief?

The best way to structure an initial backlog from a client brief is to enforce a structured Epic, Feature, and User Story hierarchy. Projetix automates this by mapping client language directly into a complete, review-ready backlog with acceptance criteria.