How do I install the Bmad Validation Metier skill?

Run npx skillmds@latest add aibot88/bmad-validation-metier in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bmad Validation Metier safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bmad Validation Metier?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bmad Validation Metier free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bmad Validation Metier?

aibot88 (@aibot88) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bmad Validation Metier by aibot88 — Agent Skill

Name: Bmad Validation Metier
Rating: 4.2 (5 reviews)
Author: aibot88

Bmad Validation Metier

Production business validation gate. Executes each Validation Metier item against a real environment (staging/production), collecting tangible proof (API responses, DB queries, screenshots, logs). Binary verdict: ALL pass = Done, ANY fail = stays in current status. Use when 'validation metier', 'validate ticket', 'tester en staging', 'valider le ticket', 'VM' is mentioned.

aibot88 Updated Sep 9, 2026 3 repo stars

File contents

Validation Metier

Overview

Production business validation gate.

Conventions

Bare paths (e.g. steps/step-01-init.md) resolve from the skill root.
{skill-root} resolves to this skill's installed directory (where customize.toml lives).
{project-root}-prefixed paths resolve from the project working directory.
{skill-name} resolves to the skill directory's basename.

On Activation

Step 1: Resolve the Workflow Block

Run: python3 ~/.claude/skills/bmad-shared/scripts/resolve_customization.py --skill {skill-root} --key workflow

If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:

{skill-root}/customize.toml — defaults
{project-root}/_bmad/custom/{skill-name}.toml — team overrides
{project-root}/_bmad/custom/{skill-name}.user.toml — personal overrides

Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.

Step 2: Execute Prepend Steps

Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.

Step 3: Load Persistent Facts

Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run. Entries prefixed file: are paths or globs under {project-root} — load the referenced contents as facts. All other entries are facts verbatim.

Step 4: Load Project Workflow Context

Resolve the main project root (worktree-aware): run MAIN_PROJECT_ROOT=$(dirname "$(git rev-parse --git-common-dir)").

Load {MAIN_PROJECT_ROOT}/.claude/workflow-context.md and resolve from its YAML frontmatter:

Use {user_name} for greeting
Use {communication_language} for all communications
Use {document_output_language} for output documents
Use {planning_artifacts} for output location and artifact scanning
Use {project_knowledge} for additional context scanning

If workflow-context.md is missing, ask the user for their name and preferred language, then continue.

Step 5: Greet the User

Greet {user_name}, speaking in {communication_language}. Be warm but efficient.

Step 6: Execute Append Steps

Execute each entry in {workflow.activation_steps_append} in order.

Activation complete. Read FULLY and follow ./workflow.md — load the file with the Read tool, do not summarise from memory, do not skip sections.

---name: bmad-validation-metierdescription: Production business validation gate. Executes each Validation Metier item against a real environment (staging/production), collecting tangible proof (API responses, DB queries, screenshots, logs). Binary verdict: ALL pass = Done, ANY fail = stays in current status. Use when 'validation metier', 'validate ticket', 'tester en staging', 'valider le ticket', 'VM' is mentioned.--- # Validation Metier ## Overview Production business validation gate. ## Conventions - Bare paths (e.g. `steps/step-01-init.md`) resolve from the skill root. - `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives). - `{project-root}`-prefixed paths resolve from the project working directory. - `{skill-name}` resolves to the skill directory's basename. ## On Activation ### Step 1: Resolve the Workflow Block Run: `python3 ~/.claude/skills/bmad-shared/scripts/resolve_customization.py --skill {skill-root} --key workflow` **If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver: 1. `{skill-root}/customize.toml` — defaults 2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides 3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append. ### Step 2: Execute Prepend Steps Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding. ### Step 3: Load Persistent Facts Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim. ### Step 4: Load Project Workflow Context Resolve the main project root (worktree-aware): run `MAIN_PROJECT_ROOT=$(dirname "$(git rev-parse --git-common-dir)")`. Load `{MAIN_PROJECT_ROOT}/.claude/workflow-context.md` and resolve from its YAML frontmatter: - Use `{user_name}` for greeting - Use `{communication_language}` for all communications - Use `{document_output_language}` for output documents - Use `{planning_artifacts}` for output location and artifact scanning - Use `{project_knowledge}` for additional context scanning If `workflow-context.md` is missing, ask the user for their name and preferred language, then continue. ### Step 5: Greet the User Greet `{user_name}`, speaking in `{communication_language}`. Be warm but efficient. ### Step 6: Execute Append Steps Execute each entry in `{workflow.activation_steps_append}` in order. --- **Activation complete.** Read FULLY and follow `./workflow.md` — load the file with the Read tool, do not summarise from memory, do not skip sections.

Frequently asked questions