This skill should be used when the user asks to "generate dashboard", "refresh dashboard", "build command center", "update ALM views", "regenerate pipeline visualization", or "open dashboard". It generates both the single-file dashboard and the multi-page ALM Command Center with all views (pipeline, specs, quality, intelligence, workspace, governance, logs, backlog, search). Use this skill whenever the user mentions dashboard, command center, ALM, or pipeline visualization.

This skill should be used when the user asks to "capture input", "save to RAG memory", "index a file", "store reference material", "capture document for context", or "add to knowledge base". It captures session inputs as RAG memory files with frontmatter, abstract, key takeaways, and full content. Workspace-aware routing sends captures to the active workspace's rag/ folder. Use this skill whenever the user mentions capture, RAG, memory indexing, or knowledge base storage.

This skill should be used when the user asks to "browse RAG memory", "search captures", "list memory files", "find past inputs", "show knowledge base", or "review stored context". It browses and searches the RAG memory archive indexed in rag-index.json. Use this skill whenever the user mentions memory browsing, RAG search, captured files, or knowledge base exploration.

This skill should be used when the user asks to "run sentinel", "check project health", "scan for drift", "detect stale artifacts", "run perceive-decide-act cycle", or "audit pipeline state". It executes a full sentinel cycle (perceive-decide-act) with zero LLM cost to detect stale artifacts, missing files, health regression, and drift from constitution principles. Use this skill whenever the user mentions sentinel, health check, drift detection, or pipeline audit.

This skill should be used when the user asks to "check status", "show pipeline status", "view progress", "what phase am I on", "show feature stages", or "display pipeline overview". It runs the status script to display a visual pipeline table with phase dots, feature stages, and next step recommendations. Use this skill whenever the user mentions status, progress, pipeline overview, or current phase.

This skill should be used when the user asks to "show menu", "list all commands", "what commands are available", "show command palette", "help with SDD commands", or "what can SDD do". It displays the interactive command palette organized by category (pipeline, intelligence, utility, experience) with descriptions and aliases. Use this skill whenever the user mentions menu, command list, help, or available commands.

This skill should be used when the user asks to "sync upstream", "update from IIC/kit", "pull latest framework", "sync intent integrity chain", "update SDD engine", or "reapply brand overlay". It syncs the upstream IIC/kit repository and reapplies the MetodologIA brand layer. Use this skill whenever the user mentions sync, upstream, IIC/kit update, or brand reapplication.

This skill should be used when the user asks to "start tour", "onboard me to SDD", "show me around", "walk me through the pipeline", "how does SDD work", or "give me a guided introduction". It runs an 8-step interactive walkthrough of the SDD pipeline covering constitution, specs, plan, checklist, testify, tasks, analyze, implement, and ship. Use this skill for onboarding, orientation, or learning SDD.

This skill should be used when the user asks to "verify project", "run verification", "check integrity", "validate structure", "audit assertions", "verify brand compliance", or "run checks". It executes the 8-check verification suite covering structure, brand, tokens, assertions, and workspace integrity. Use this skill whenever the user mentions verify, validate, integrity check, or compliance audit.

This skill should be used when the user asks to "install hooks", "set up git hooks", "enable assertion integrity", "install pre-commit hooks", "configure commit validation", or "protect test hashes". It installs git pre-commit and post-commit hooks that enforce assertion integrity by validating .feature file SHA-256 hashes on every commit. Use this skill whenever the user mentions hooks, assertion integrity, or commit validation.

Generate production-ready SKILL.md and MOAT asset files from a skill design. Enforces MOAT quality dimensions (>=7 on all 6), 500-line body limit, progressive disclosure. Trigger: spec skill, generate skill spec, write SKILL.md, create skill specification, produce skill MOAT.

Create MOAT directory structures and populate asset files (references/, examples/, prompts/, scripts/, assets/) for plugin skills. Trigger: build MOAT assets, create skill assets, populate references, generate examples, build skill directories.

Design MOAT asset strategy per skill: which subdirectories needed, what content they contain, naming conventions. Trigger: plan MOAT, MOAT strategy, asset planning, reference planning, plan skill assets.

Performs a comprehensive security audit on a Claude Code plugin, detecting leaked secrets, unsafe paths, shell injection risks, sensitive files, and insecure scripts. Trigger: audit security, security scan, check for secrets, find vulnerabilities.

Audits all SKILL.md files in a plugin against a 6-criteria excellence rubric, producing per-skill scores, plugin averages, and actionable improvement recommendations. Trigger: audit content quality, score skills, check skill quality, content rubric.

Generate plugin architecture plan with agent roles, skill-movement mapping, hook strategy, and command routing. Trigger: plan architecture, design plugin structure, architect plugin, plugin architecture, plan plugin layout.

Validates frontmatter and body structure of all skills, agents, and commands in a plugin. Triggers: validate components, check frontmatter, component audit, skill validation.

Scaffold a complete plugin directory from architecture plans and specs. Creates all files, then validates structure. Trigger: build plugin, scaffold plugin, create plugin directory, assemble plugin, generate plugin files.

Generate production-ready agent .md and command .md files from designs. Enforces plugin subagent constraints and alias linkage. Trigger: spec agent, spec command, generate agent file, write command file, create agent specification.

Generate a structured plugin concept brief from a user idea. Trigger: ideate plugin, brainstorm plugin, plugin concept, new plugin idea, create plugin concept. Researches existing plugins for overlap, proposes movement structure and component counts.