ghm-id-register
Validates and registers new SoT IDs with cross-reference integrity. Triggers when creating BR-XXX, UJ-XXX, API-XXX, or CFD-XXX entries. Outputs formatted SoT entry with validated cross-references.
context7-resolve-library-id
To find the Context7-compatible library ID for a package or product name, resolve the library ID before querying docs unless the user already provided an /org/project ID (max 3 calls).
context7-query-docs
To fetch up-to-date docs and code examples from Context7 for a known library, query by a resolved library ID after running resolve-library-id (max 3 calls).
doctor-triage
Perform breadth-first hypothesis surfacing and prioritization across all ownership zones, without commitment. This is not diagnosis and not investigation.
chrome-history
Query Chrome browsing history with natural language. Filter by date range, article type, keywords, and specific sites.
community-docs
Community superstitions - unverified observations from pattern development. Use when encountering undocumented edge cases or framework quirks not in official docs. Verified knowledge should be upstreamed to labs docs.
onboard
Creates C3 architecture documentation from scratch using staged Socratic discovery. Use when the user asks to "adopt C3", "onboard me to architecture", "scaffold C3 docs", "init C3", "set up architecture docs", or starts C3 documentation for a new project. Implements 3-stage workflow: Inventory → Details → Finalize.
completing-layer-documentation
Use after verifying-layer-documentation to fix all gaps found. Reads gaps.md and adds missing documentation.
writing-skills
Use when creating or updating SKILL.md documentation - Explains how and why to create a skill.
latex-overleaf
Comprehensive LaTeX documentation from Overleaf Learn tutorials
writing-specs
Use when creating feature specifications after brainstorming - generates lean spec documents that reference constitutions heavily, link to external docs instead of embedding examples, and focus on WHAT not HOW (implementation plans handled separately)
skill-selector
Self-driven skill selection system that uses internal curiosity asking (self-questioning) to analyze user requests, infer context from available information, and automatically recommend the most appropriate skills. Use when (1) User requests are ambiguous or unclear, (2) Multiple skills could potentially match a request, (3) User needs help discovering available skills, (4) Understanding user context is needed before recommending skills, or (5) User asks "what skills are available" or "which skill should I use".
cynefin-classifier
Classify problems into Cynefin Framework domains (Clear, Complicated, Complex, Chaotic, Confusion) and recommend appropriate response strategies. Use when unsure how to approach a problem, facing analysis paralysis, or needing to choose between expert analysis and experimentation.
briefing-note-expert
Expert in generating executive briefing notes (1-2 pages, decision-focused) for infrastructure acquisition projects including issue framing, background context, financial analysis, recommendation development, risk assessment, and action planning. Use when preparing board submissions, executive decision memos, or approval requests for property acquisitions. Key terms include briefing note, executive summary, decision memo, board approval, acquisition recommendation, risk assessment, action items
technical-design-doc
Generates clear technical design documents with architecture, trade-offs, and rollout plans.
tech-specification
The master skill for generating technical specifications. Identifies project technology and delegates deep analysis to specialized sub-skills.
create-plan
Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
feature-analyzer
Comprehensive feature artifact analysis for loading and understanding complete feature context. Use when needing to: (1) Load all feature documentation before implementation, (2) Build mental model of feature requirements and architecture, (3) Prepare context for downstream operations like checklist generation or task execution, (4) Analyze feature completeness and artifact availability. Triggers on: analyze feature, load feature context, prepare feature, check feature prerequisites, understand feature scope.
frontend-master
Master skill for frontend development with Next.js + React + Tailwind stack. Decision framework for choosing components, animations, assets, and tools. Routes to specialized skills for implementation details. Use as entry point for any frontend task.
refine-issue
Refining issues with technical context and structured details. Use when expanding a brief bug, feature, or refactor description into a detailed issue suitable for developers and AI agents.
