Menu
Run the i18n validation script to check for missing, extra, or misformatted translation keys before publishing
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Spec-driven development orchestrator. Creates and executes spec-workflow specifications from an issue — Requirements → Design → Tasks → Implementation with dashboard approvals and subagent dispatch.
On-demand project health check — code quality (CGC), security (Codacy SRM), instruction file drift (CLAUDE.md vs Agents.md vs Gemini.md), issue landscape, index health. Triggers: "audit", "health check", "check project health", "scan codebase", "code health", "instruction drift", "check for drift".
Casual, freeform discovery mode (Phase 0 of the Spec Flow Lifecycle). Explore an idea without committing to code, issues, or specs. Dispatch subagents for research, surface past work from mem0, and build context until the idea is ready for an issue and formal spec. Triggers on "/chat", "/talk", "let's explore", "I have an idea", "what if we".
Structured brainstorm and research phase (Phase 1 of the Spec Flow Lifecycle). Takes an issue ID, dispatches research agents, runs codebase analysis, and produces a Discovery Brief with all open questions resolved. Bridges the gap between casual exploration (/chat) and formal spec creation (/spec). Triggers on "/discover", "/brainstorm", "research this issue", "explore this before we spec it".
Issue management — create, read, update, list. Backend is driven by `.specflow/config.json` `issue_backend` field: `plane` (Plane MCP, primary going forward) or `docvault` (legacy markdown — for projects not yet migrated). Triggers on: "create issue", "issue", "new issue", "new bug", "file a bug", "track this".
Migrate a user-level skill into the specflow plugin's skills directory. Use when porting a proven skill from ~/.claude/skills/ to the plugin for distribution. Covers generic vs project-specific classification, MCP prompt extraction, deprecation of user-level shims, and verification.
| name | validate-i18n |
| description | Run the i18n validation script to check for missing, extra, or misformatted translation keys before publishing |
Run the i18n validator for the specflow project:
cd /Volumes/DATA/GitHub/specflow && node scripts/validate-i18n.js
Report the full output. If clean, confirm "i18n validation passed — all translation keys are consistent."
If there are failures, list them clearly grouped by:
Suggest fixes for any issues found.