Menu
Promote a battle-tested user-level skill to the specflow shipped skills directory (specflow/skills/)
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.
Run the i18n validation script to check for missing, extra, or misformatted translation keys before publishing
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".
| name | promote-skill |
| description | Promote a battle-tested user-level skill to the specflow shipped skills directory (specflow/skills/) |
Promote a skill from ~/.agents/skills/<name>/ to specflow/skills/<name>/.
Usage: /promote-skill <name> — e.g., /promote-skill my-workflow
Verify source exists
Read ~/.agents/skills/<name>/SKILL.md. If it doesn't exist, stop and report.
Sanitization check Scan the skill content for lbruton-specific paths or personal preferences:
/Volumes/DATA/GitHub/ that should be relative or omittedlbruton username references
Report findings and ask for confirmation if anything looks personal before proceeding.Check for existing shipped copy
Check if specflow/skills/<name>/SKILL.md already exists.
If yes, show a diff of what would change.
Copy
mkdir -p /Volumes/DATA/GitHub/specflow/skills/<name>
cp ~/.agents/skills/<name>/SKILL.md /Volumes/DATA/GitHub/specflow/skills/<name>/SKILL.md
Verify diff
Run diff ~/.agents/skills/<name>/SKILL.md /Volumes/DATA/GitHub/specflow/skills/<name>/SKILL.md.
Only sanitization changes should appear. If other differences exist, flag them.
README check Grep the README.md for the skill name. If not found, note that the skills inventory section needs updating and show the user the relevant README section to update manually.
Commit and open a PR
cd /Volumes/DATA/GitHub/specflow
git add skills/<name>/
git commit -m "feat(skills): promote <name> to shipped skills"
git push -u origin <branch>
Confirm completion with the commit hash and PR URL.