gannonh

mintlify

Build and maintain documentation sites with Mintlify. Use when creating docs pages, configuring navigation, adding components, or setting up API references.

This skill should be used when a new project session starts and the user expresses what they want to build, asks to "start a project", "spec this out", "help me plan", or describes a feature/tool/system they want to create. Guides structured intent capture through goal, constraints, architecture, acceptance criteria, tasks, and non-goals.

Code & Development Solid

debug-symphony

Investigate stuck runs and execution failures by tracing Symphony, Pi runner, and Codex logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.

okf

Create, read, and maintain Open Knowledge Format documentation bundles in repositories. Use this skill when the user asks for /okf, OKF, Open Knowledge Format, docs-as-knowledge, reading project context from docs, reorganizing docs into an agent-readable bundle, updating docs/specs/ADRs after a session or PR, or adding AGENTS.md instructions for agents to consume and maintain the docs bundle. Supports /okf read, /okf init, and /okf update workflows.

plan-build-verify-github

Use this skill for multi-step, spec-driven, or acceptance-gated implementation work in a GitHub repository where specs live as GitHub Issues. Routes work through Plan, Build, and Verify phases, manages the roadmap through issue labels and sub-issues, and triages and grooms the backlog. Also handles migration from file-based specs to GitHub Issues.

kata-complete-milestone

Use when the user wants to finish, close, ship, archive, or mark the active Kata milestone complete.

kata-execute-issue

Use when the user wants to execute a standalone Kata issue, one-off issue plan, backlog issue, or isolated implementation plan created by kata-plan-issue. This skill selects or retrieves an open issue from the backend, confirms the issue with the user, then executes its approved plan with fresh subagents and two-stage review per task.

kata-execute-phase

Use when the user wants Kata to execute planned phase work or advance tasks in the active milestone.

kata-health

Use when the user asks whether Kata is configured correctly, healthy, connected, or ready to run.

kata-new-milestone

Use when the user wants to create the next milestone, release goal, or scoped delivery target for an existing Kata project.

kata-new-project

Use when the user wants to start, define, import, or initialize a Kata project.

kata-plan-issue

Use when the user wants to plan a one-off Kata issue, standalone issue, backlog item, bugfix, enhancement, or slice-sized unit of work outside the milestone/slice/task workflow. This skill turns an isolated request into a single issue containing both a design section and an implementation plan section. Use this instead of kata-new-milestone or kata-plan-phase when the work should be planned and executed in isolation rather than as part of an active milestone.

kata-plan-phase

Use when the user asks to plan a phase, slice upcoming work, or turn a milestone goal into executable Kata tasks.

kata-progress

Use when the user asks for Kata project status, milestone progress, task progress, or execution state.

kata-setup

Use when the user asks to install Kata, set up Kata CLI, connect Kata to an agent harness, or check initial Kata configuration.

kata-update-project

Use when the user wants to update an in-flight Kata project, refresh project artifacts, revise the current milestone, adjust requirements or roadmap context, or pause work to record ad hoc project direction changes. This skill interactively updates durable project and active milestone artifacts without creating new execution scope.