Your agent can do more. Find the skill that makes it happen.
Find your next superpower If you are an agent, refer to our llms.txt for full access.Establishes a spec-first workflow by writing PRODUCT.md before implementation and TECH.md when warranted. Keeps specifications updated throughout development and supports planning agent-driven implementation with specs in source control.
Verify that a specification is marked approved in any language, create and switch to a branch named after it, and implement it step by step. Pause along the way for diff review.
Write a Gherkin story file to docs/stories/ for a feature. The story IS the spec. No intermediate PROBLEM/SPEC/PLAN/TASKS artifacts.
Investigates legacy or undocumented systems to explain their behavior and map code dependencies. Generates API and architecture documentation from implementation and identifies undocumented business logic.
Dialogue-driven spec development through skeptical questioning and iterative refinement. Use when "spec this out", feature planning, architecture decisions, "is this worth it?" questions, RFC/design doc creation, work scoping. Invoke Librarian for unfamiliar tech/frameworks/APIs.
Checks implementations against whitepapers, protocol specifications, or design documents. Reports which requirements hold, which are contradicted or absent, and which code behaviors have no documented requirement.
Structures planning before implementation through explicit requirements, technical design, and task breakdowns. Suits work spanning multiple modules, unclear acceptance criteria, or substantial architectural decisions.
Specialized hardware interfaces and system reliability for Zephyr RTOS. Covers LVGL GUI development, Audio I2S/Codecs, Watchdog timers, and Fault Injection. Trigger when building human-machine interfaces (HMI), audio devices, or high-reliability mission-critical systems.
Bridges design and engineering by producing detailed specs, organized handoff packages, asset inventories, and cross-functional documentation. Part of the Intent design strategy system. Trigger when: writing design specs, preparing engineering handoffs, documenting for development, writing the spec material behind a design review (the deck itself goes to /present), writing test plans, building copy matrices, addressing edge cases, packaging designs "for engineering," or sayi…
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
Orchestrate the Codex Spec Kit sub-agent workflow with mandatory token observability.
Generate a custom checklist for the current feature based on user requirements.
Skills give your agent reusable instructions for a specific job. Pick one, read what it does, and bring it into your workflow.
A name only tells half the story. Search the full description and instructions to find the right fit.
Read the skill, visit its source, and see exactly what you’re adding to your agent.
Copy the install command from a skill page and run it in your project.
npx skillycli add owner/repo --skill name