Loading...
Loading...
Found 3,124 Skills
Write an implementation spec when a task has decisions, invariants, or boundaries worth surfacing before coding.
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
Execute the implementation planning workflow and generate design artifacts using the plan template. Trigger phrase: "speckit plan".
Create a beautiful HTML explanation of a repo, spec, PR, architecture, or concept so a smart beginner can understand and retell it.
explain-diff: explain a code change, diff, branch, or PR as a rich self-contained HTML page. Flags: --target <branch>, --pr <n>, --staged, --unstaged, --output <path>.
Interactive feature development workflow from idea to implementation. Creates requirements (EARS format), design documents, and task lists. Triggers: "kiro", ".kiro/specs/", "feature spec", "需求文档", "设计文档", "实现计划".
Crypto news search, AI ratings, trading signals, and real-time updates via the OpenNews 6551 API. Supports keyword search, coin filtering, source filtering, AI score ranking, and WebSocket live feeds.
One-stop skill for the project architecture center — draft new architecture documents, refresh existing architecture documents, or conduct an architecture health check. Automatically determine the mode based on user input: `new` (draft)/ `update` (refresh to the latest code status)/ `check` (view only, generate issue list). The `check` mode has three sub-goals: consistency within a single feature design, alignment between design and code, and consistency among multiple documents under `easysdd/architecture/`. Single-target rule — only modify one document or check one target at a time. Trigger scenarios: User says "fill in an architecture doc", "draft an architecture document", "refresh the architecture directory", "write down the structure of this module", "conduct an architecture check", "is the design internally consistent?", "does the plan match the code?", "are there conflicts among several documents in the architecture folder?", or when it is found in the feature-design / feature-acceptance / implement phase that an architecture action needs to be performed first before proceeding.
For when you're asked to write a design doc or specification, especially after a brainstorm or feature design session.
Use when you need durable, repo-specific context (architecture, domain model, how a flow works, standards, gotchas, decisions) before engineering or reviewing, or when you have learned something worth recording. Reads and writes an in-repo Obsidian knowledge base (docs/<repo>-vault/), synced by git.
Story decision capture and mining — recording what was decided, what was rejected, and why, inline with the artifacts they relate to. Use whenever story direction is being chosen, brainstorm options are being narrowed, character or world choices are being made, or past decisions need to be recovered from session history.
Creates a structured lessons learned entry for organizational memory. Use after projects, incidents, or significant learnings to capture knowledge for future teams and initiatives.