Loading...
Loading...
Found 3,117 Skills
Wrap up completed work. Council validates the implementation, then extract learnings. Triggers: "post-mortem", "wrap up", "close epic", "what did we learn".
Generate comprehensive implementation tutorial documents with deep background, context, rationale, and step-by-step milestones. Use when the user wants to learn by building—creating detailed guides instead of making direct code changes. Triggers on requests like "create a tutorial for", "implementation guide", "teach me how to implement", or explicit /tutorial invocation.
Run a high-quality decision process and produce a Decision Process Pack (decision brief/pre-read, options + criteria matrix, RAPID/DACI roles, decision meeting plan, decision log entry, comms, review plan). Use for decision making, decision memo, decision log, one-way door vs two-way door, RAPID, DACI, RACI, exec alignment.
Design or refactor skills by separating deterministic and non-deterministic steps. Use when creating or improving skills, especially to move repeatable workflows into scripts/ and update SKILL.md to call them.
This skill should be used when content teaches patterns (skills, subagents, ADRs, PHRs, specifications) that have canonical sources elsewhere. Prevents format drift by ensuring content references and follows the authoritative format from canonical sources. Use before implementing lessons that teach platform patterns, or when reviewing content for format consistency.
Lint and fix Markdown files using markdownlint-cli2. Use when asked to: lint, fix, format, or clean up Markdown (.md) files; enforce Markdown best practices or style standards; resolve markdownlint errors or warnings. Triggers on requests mentioning markdownlint, markdown linting, or formatting Markdown to best standards.
Use this when users need help starting or continuing their writing (not diaries). Trigger scenarios include "don't know what to write", "help me brainstorm", "write a travelogue", "record TIL", "write something". For diary writing, please use the diary-assistant skill instead.
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.
Manage project context effectively. Use when onboarding, context switching, or maintaining project knowledge. Covers context capture and sharing.
Write feature specifications that capture requirements and acceptance criteria. Use when (1) writing a new feature spec, (2) documenting functional requirements, (3) defining acceptance criteria for a feature, (4) capturing design goals and constraints for planned work, or (5) structuring a product idea into a formal specification.
Collect improvement insights from UI/UX reviews, document research, or external references, convert confirmed items into development requirements. Use when users have optimization suggestions, research findings, or want to improve based on external references. Triggers on keywords like "insights", "improvements", "optimize", "review findings", "research", "reference", "optimization suggestions", "review results", "research".
[Planning] ⚡⚡⚡⚡ Research & create an implementation plan with 2 approaches