Loading...
Loading...
Found 87 Skills
Use when you have a spec or requirements for a multi-step task, before writing implementation code. Helps break down complex features into bite-sized, verifiable tasks.
Navigate the SLDD (Spec Loops Driven Development) process and choose the correct skill for the current stage. Use when starting a new feature or when unsure which step comes next.
Use when executing implementation plans. Dispatches independent subagents for individual tasks with code review checkpoints between iterations for rapid, controlled development.
Holistic, system-aware planning before implementing non-trivial tasks. Use when the task involves new features, architectural decisions, multi-file changes, unclear requirements, or multiple valid approaches. Triggers on "/plan", "plan this", "design an approach", "let's plan first".
PRD/Requirement Document Anti-Omission Assistant. When a user provides a requirement document (PRD, functional specification, product document, etc.) and requests to generate front-end pages, implement functions, or carry out development, this Skill must be used first to convert the requirement document into a structured Checklist, then implement code module by module to prevent function omissions. Trigger scenarios: The user sends a .md/.docx/.pdf requirement document and asks you to "generate pages", "implement functions", "write code", "develop this system"; the user says "develop according to this PRD", "generate based on the requirement document", "implement this document"; the user provides a requirement description of more than 200 lines. Even if the user does not mention the checklist, this process should be automatically triggered if the input is a long requirement document (>200 lines) and the goal is to generate code.
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
Enforces strict Spec-Driven Development. Prevents direct coding and ensures spec → generate → review loops.
Use when planning or designing features and need to understand current codebase state, find existing patterns, or verify assumptions about what exists; when design makes assumptions about file locations, structure, or existing code that need verification - prevents hallucination by grounding plans in reality
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
Disciplined plan execution for implementation tasks. Use when executing a saved implementation plan, following step-by-step instructions from a plan document.
Use this when you have a written implementation plan and execute it in separate sessions with review checkpoints
Interactive onboarding workflow that interviews users to understand their coding goals and generates PR-ready implementation plans. Use when starting a new development task to ensure clear requirements and structured execution.